Pages:
Author

Topic: Stop fuckin' around, fork the son-of-a-bitch already. - page 3. (Read 9367 times)

legendary
Activity: 4424
Merit: 4794
The most interesting thing about the above-quoted list is that nobody wants to play the obvious zinger in response. Have a little fun. Please.

if your talking about why i switched from talking about hard drive to bandwidth, obviously hard drives are cheap so the other 'cost' is internet speed
if your talking about my reasoning to talk about UPLOAD instead of download.. there is a technical reason for this
if your talking about why i am mentioning uploading live video. as oppose to a tweet there is an obvious reason for this too

the reason i used live streaming is because its a real life scenario people can understand of large data moving..
(upload 10minutes of SD(0.5mbIT/sec) quality video=~37mbyte of data)

months ago lauda attempted to debunk WATCHING videos as that was only download bandwidth to which i replied months ago with UPLOAD stats of livestream recording at that time. and today was reminding him of the facts that the internet as a whole is not a problem for 2-4mb blocks upload and by default definitely no issues for download

though the internet is proven to be fast for hundred of MILLIONS of people as shown by all the countries doing livestreaming to prove its not a dream. the community accept some places can get over 100mb/s, but as a safe level the majority feel 2-4 is acceptable.. even core believe 4mb is acceptable now.
im not going to get into the debate of someone else advocating 20mb, as that is just poking laudas bear and not something the community as a whole could consider right now(though technically possible).

i personally have only been advocating for 2mb this year knowing rationally that in the near future technology progresses to allow for more (even if the technology is already available now. its best to stay in the safe zone)

in short 4mb is internet safe, 2mb is even safer so data speed debate of 2mb should be considered resolved as it was before late 2015 (even in cores 4mb eyes, 2mb is safe)

which is why i laugh hard when lauda was saying 2mb was bad.. yet his friends are saying 4mb is acceptable, and lauda has now backtracked to say 4mb is acceptable "because its core". but 2mb is still bad.

even if its a 2mb base 4mb weight linear validation rules.. lauda will still not be happy and will always try to debate some crap to keep core as the overlords, rather than all implementations coming to a joint agreement making all implementations all on the same level playing field coming to a joint consensus, which the community thought we reached before last christmas. and then tried to get core back inline in spring. and then again in summer..
hero member
Activity: 493
Merit: 518
a 2tb hard drive is only 800,00 kuna (im guessing your still in croatia) (£90 : $120 for those not wishing to convert kuna to western currencies)
No, I am not and have never been in Croatia.



hmm.. lets pick a country .
ok africa..http://www.africawebtv.com/
ok korea..http://www.afreecatv.com/
ok russia..http://www.vichatter.com/

i could go on..


The most interesting thing about the above-quoted list is that nobody wants to play the obvious zinger in response. Have a little fun. Please.
hero member
Activity: 697
Merit: 520
1) Security risk of a DOS due to quadratic validation problem.

Today's DOS attack on Ethereum is relevant here:

http://www.ethnews.com/ethereum-network-under-a-dos-attack


I suppose we can keep musing about how irrational it would be for such blocks to mined... but, food for thought.
legendary
Activity: 2674
Merit: 3000
Terminated.
If you are not against blocksize increase, then why do you keep arguing against it?
Because it's the wrong position to have and it has many cons which should not be ignored. 2 MB is inherently dangerous, hence the additional limitations as added by Gavin's BIP for Classic. Segwit aims to solve this, in addition to increasing the capacity with usage (which should result in around 170-180% increase). After Segwit, we should look into acceptable block size increases. In addition to all of this, deploying a HF just for the sake of a block size increase is horribly inefficient. There are certainly some changes/optimizations that require a HF and those should be deployed along side the block size increase.

I'm not taking things out of context, although I do remember someone doing just that a few posts ago.
Yes, you have. It's still better than the franky1's "You all want Monero to succeed" fantasy.
legendary
Activity: 1106
Merit: 1005
So even though those statements weren't direct quotes (I never implied they were quotes), I can proof that they align with your statements. Therefore you are contradicting yourself, and falsely accusing me of lying.
Taking things out of context in other to strengthen your position is what one would usually define a lying manipulator as.

If you are not against blocksize increase, then why do you keep arguing against it?

I'm not taking things out of context, although I do remember someone doing just that a few posts ago.

Quote
No, that's not what Bitcoin "is doing right now". Bitcoin can't do anything on its own as Bitcoin isn't an entity that can decide for itself. In addition to that, the analogy is false since the limit in currently a safeguard from the DOS risk at 2 MB or higher.

So is the analogy, with the side effect that it is limiting users. Which bitcoin is doing right now too. (and you know full well what I mean by that, don't derail the conversation by arguing semantics)
legendary
Activity: 2674
Merit: 3000
Terminated.
Here you are disagreeing with limiting the transaction size. (limiting it to 1MB is implied, just to be sure you understand, the current limit is 1MB because the blocksize is 1MB and therefore a transaction larger than 1MB doesn't fit).
What was meant is that I'm against additional imposed limitations in order to favor a HF. I'm undecided about TX size as there haven't been that many discussions about it.

-snip-
and here you are disagreeing with increasing the block size.
Listing cons of something != disagreeing with it. There is likely going to be some headroom with Segwit, where an additional increase of 1-2 MB may be okay. I'm still waiting for Luke-Jr's proposal.

So even though those statements weren't direct quotes (I never implied they were quotes), I can proof that they align with your statements. Therefore you are contradicting yourself, and falsely accusing me of lying.
Taking things out of context in other to strengthen your position is what one would usually define a lying manipulator as.

And yet, that's exactly what bitcoin is doing right now.
No, that's not what Bitcoin "is doing right now". Bitcoin can't do anything on its own as Bitcoin isn't an entity that can decide for itself. In addition to that, the analogy is false since the limit in currently a safeguard from the DOS risk at 2 MB or higher.

Not enough time for what? Verifying with an abacus?
I'll even risk by saying that enthusiast grade hardware will not be able to validate a sigop expensive 20 MB block in time. Someone would need to test this out to confirm though.
legendary
Activity: 1106
Merit: 1005
1) You could limit the transaction size while still increasing the blocksize.
It's not a matter of 'could' or 'could not', but rather a matter of "should" or "should not". I disagree with those limitations.


Here you are disagreeing with limiting the transaction size. (limiting it to 1MB is implied, just to be sure you understand, the current limit is 1MB because the blocksize is 1MB and therefore a transaction larger than 1MB doesn't fit).

Other than a mindless fearr of a hard fork, give me 1 solid reason based on logic against a block size increase.
1) Security risk of a DOS due to quadratic validation problem.
2) No hard fork experience.
3) High risk of damaging merchants and businesses that do not manage to update in time (if the activation parameters are improper such as with Bitcoin Classic).
4) Higher storage cost.
5) Higher bandwidth cost.

Even if we disregard the 4 latter, the primary issue is still the security risk.

and here you are disagreeing with increasing the block size.

So even though those statements weren't direct quotes (I never implied they were quotes), I can proof that they align with your statements. Therefore you are contradicting yourself, and falsely accusing me of lying.

Quote
Until somebody "turns on" the spam again, and suddenly everyone is stuck with massive bloat.

you can't just block honest transactions because you're afraid of spam. You're doing more harm than good that way.

That's like only allowing 100 users at a time to connect to google.com because otherwise google.com might be DDOSed. So whenever there's 100 users on google, google.com blocks all requests until one of the users is done.    

If google.com would do that, how long do you think google.com remains the most popular search engine?

Not very long.

And yet, that's exactly what bitcoin is doing right now.

Quote
No, that's not even nearly enough time, especially not without Segwit.

Not enough time for what? Verifying with an abacus?

Could you get equipment from this century at least?
Quote
Ad hominem nonsense due to losing ground.

fun fact, 100% of the troll I have spoken to have used the following arguments when they run out of actual arguments:
Quote
*You are using ad hominem
* You are using strawman arguments

Does not matter if I am actually using ad hominem or strawman arguments.
legendary
Activity: 1106
Merit: 1005


anyway
although 20mb is diverting off the current proposals by a factor of 5-10x.. and entering the cosmic theory of doomsday dreams, lets ask you..
are you saying to this other guy that 0.3mb internet speeds is something the world is averaging.
is this 0.3mb speed something you yourself are suffering with..



There's actually some proposals for 20MB blocks and they're widely accepted. source: https://en.bitcoin.it/wiki/Block_size_limit_controversy#Entities_positions

In favor: Magnr, Ethereum (If bitcoin is used as currency), armory, bitcoinreminder, bithours, bitpay, bittiraha.fi, blockchain.info, blocktrail, breadwallet, BTC guild, BX.in.th, coinbase, coinify, adam back, kryptoradio, okcoin, 3rd key solutions, xapo, F2pool (in favor of 5MB, 20MB is too soon for them).

Opposed: bitcoinpaygate, bitrated, greenaddress, mpex, paymium.

The only entity actually providing a reason for opposition is greenaddress, who provided "it's only a temporary solution" as a reason. So they recognize the problem, but they don't agree with the solution because they think it won't fix the problem long-term.


Btw, only 6 out of 144 countries have an average upload speed of < 0.9 Mb/s, only 2 of them have an average download speed of < 0.9Mb/s (burkina faso [0.84 Mb/s] and niger [0.6 Mb/s])

0 out of 144 countries have an average download speed of < 0.3 Mb/s and 2 out of 144 have an average upload speed of < 0.3 (burkina faso [0.29 Mb/s] and niger [0.2 Mb/s])

total population of those two countries is roughly 34 million (both countries are about 17 million)

Those might struggle a little bit, but even they could probably run 20MB blocks (especially if we include xthin blocks)



Although I think it's together with xthin blocks to make the network propagation more efficient by a factor of at least 5 times. So effectively they would be like 4MB blocks but allowing 20MB worth of transactions (and i can only imagine what SegWit/LN could improve on this).

Scaling is possible, it's only some people holding it back, for no particular reason.
legendary
Activity: 2674
Merit: 3000
Terminated.
Statement 1:
I don't want blocks larger than 1MB

Statement 2:
I might want transactions larger than 1MB

These are not compatible with each other (not to mention, they're ridiculous, even in their own, but together they're even worse).
I have made neither one of these statements. Now you're just an outright liar and manipulator (say hi to Veritas for me).

-snip-
Ad hominem nonsense due to losing ground.

You're only showing that talking with you is a massive waste of anyone's time.
You're the one wasting time with wrongful information trying to mislead people into supporting something that is both inherently controversial and dangerous.

Still, in practice even a cheap 500GB drive would last for at least half a year, and most likely longer because it's unlikely blocks of 20MB would be filled every time at least for the next few years.
Until somebody "turns on" the spam again, and suddenly everyone is stuck with massive bloat.

And xthin blocks would solve that issue too, but Core doesn't support xthin (of course, because core doesn't support improvement).
Xthin is half-baked level improvement, just like pretty much any other BU development has been.

10 minutes should be enough for the slower nodes to keep up with plenty of headroom.
No, that's not even nearly enough time, especially not without Segwit.
legendary
Activity: 1106
Merit: 1005
So you agree there's no normal use case for 1MB or larger transactions, so why do you oppose limiting transactions to 1MB while increasing blocksize?
I don't agree with that. I haven't thought about it, and I'm pretty sure that there may very well be a normal use case for some business.
You do realize that in order to have transactions bigger than 1MB you would need blocks bigger than 1MB right?   
i hope you have at least that level of intelligence.

Considering your contradiction posts on this subject though, I am starting to doubt that. (either that, or you are forgetting your own statements in less than a few hours after posting them).

Statement 1:
I don't want blocks larger than 1MB

Statement 2:
I might want transactions larger than 1MB

These are not compatible with each other (not to mention, they're ridiculous, even in their own, but together they're even worse).

Are you mad because I can destroy your entire argument in 2 minutes of typing?
1) I don't get "mad" when someone rationally shows supreme arguments. 2) You did no such thing.
If you don't understand me, than that's not my problem, but yours.   
I have proven this to be factually correct, and it remains true until you prove proof that your disagreement is backed by logical reasoning and facts.  
You have done no such thing. You're starting to resemble Veritas.
See above comment
And you can teach me?
I may or may not be able to, not that it would matter.
I doubt it.
First of all, technology has become much cheaper in the past 6 years (on average at least). And besides, who really has a hard drive measured in gigabytes anymore?    
Strawman argument.
I'm sure this is in no way a strawman argument.
It's a pure example of strawman fallacy. I never argued that "technology didn't become cheaper" did I? Don't attempt to use fallacies again, else we end up with nonsense as "Strawman nodes".  Roll Eyes
It's pretty clear you have no idea what a strawman argument is, and are accusing me of using them while your whole premise is based on one.   
You're only showing that talking with you is a massive waste of anyone's time.

Yes, they're being sold and yes I plan to buy a 1/2 TB drive.
That's still plenty to run 20MB blocksize for several years, even if you falsely assume every single block is full. (and it's still a drive measured in terabytes)
20 MB per block x 6 blocks per hour x 24 hours a day x 365 days a year = ~1051 GB per year. Please explain how a 1/2 TB drive (aka 500 GB drive) would run for "several years".
well, this is the first time you actually have a point, I didn't bother calculating that, so I turned out to be wrong in that statement.

Still, in practice even a cheap 500GB drive would last for at least half a year, and most likely longer because it's unlikely blocks of 20MB would be filled every time at least for the next few years.

It's quite easy, you just divide the blocksize by the average time it takes to find a block.
20 MB / 10 minutes = 2 MB per 1 minute. 2 divided by 60 = 0.03 MB/s. Let me tell you why your thinking is flawed (not that you're going to admit this). If a node is downloading at this speed, it will never catch up. Why is that? By the time that it downloads a 20 MB block, it is likely that another one will be created. The node would still be validating the previous block in addition to having the next one. I do wonder how long it takes to validate a 20 MB block on decent hardware though.

Except that you snipped out the part where I actually admitted this before you even brought it up as an argument, along with saying that this isn't an issue because it's several orders of magnitude lower than even slow internet speeds. So even if you account for this, it's not a problem.     

Not only do you show an inability to reasoning on any level of intelligence, you also are also purposely misrepresenting my quotes. I'm not beyond admitting when I'm wrong, I am wrong sometimes, but that does not invalidate my arguments. Fact is, every single person is wrong sometimes, but that does not make everything they say wrong.

And xthin blocks would solve that issue too, but Core doesn't support xthin (of course, because core doesn't support improvement).


And what is the primary bottleneck then? I'm sure memory won't be a problem with blocksizes smaller than a few gigabyte.
Validation time.

Well, it's a good thing Satoshi was smart enough to keep block times at 10 minutes then, unlike many altcoins who have blocktimes of mere seconds.     
10 minutes should be enough for the slower nodes to keep up with plenty of headroom. (this is also why I oppose of altcoins with very fast blocktimes).

legendary
Activity: 4424
Merit: 4794
a 2tb hard drive is only 800,00 kuna (im guessing your still in croatia) (£90 : $120 for those not wishing to convert kuna to western currencies)
No, I am not and have never been in Croatia.

well i just thought that with all of your cries about internet speeds and stuff there was no way that you could live in america..
also things like talking croatian and being a mod of the croation category..

anyway
although 20mb is diverting off the current proposals by a factor of 5-10x.. and entering the cosmic theory of doomsday dreams, lets ask you..
are you saying to this other guy that 0.3mb internet speeds is something the world is averaging.
is this 0.3mb speed something you yourself are suffering with..

have you also complained to skype for offering video services to millions of happy people because in your eyes them millions of people must be unhappy.
have you also complained to twitch, youtube, and other video upload services that do live streaming?

in short is 0.3mb a real world problem where video uploading and livestream is a problem (uses more data then all current bitcoin proposals)

hmm.. lets pick a country .
ok africa..http://www.africawebtv.com/
ok korea..http://www.afreecatv.com/
ok russia..http://www.vichatter.com/

i could go on..
seems all countries around the world can livestream.

the funny thing is that you are more distraught about including 3rd world countries than excluding them.
this is because internet speeds are not excluding 3rd world countries, but the thing you have shown many times, is that your desire for higher fee's will price 3rd world countries out of using bitcoin.
i then laugh that you pretend you want higher fee's to reduce spam. yet you want to remove features like sigops, which will allow spammy transactions to increase. (funny that)
legendary
Activity: 2674
Merit: 3000
Terminated.
The whole reason huge transactions are unsafe is because of quadratic scaling, which won't work if you split up the equation across two transactions that scale linearly with each other.    
I wasn't talking about that when I mentioned the potential of unknown attack vectors.  

So you agree there's no normal use case for 1MB or larger transactions, so why do you oppose limiting transactions to 1MB while increasing blocksize?
I don't agree with that. I haven't thought about it, and I'm pretty sure that there may very well be a normal use case for some business.

Are you mad because I can destroy your entire argument in 2 minutes of typing?
1) I don't get "mad" when someone rationally shows supreme arguments. 2) You did no such thing.

I have proven this to be factually correct, and it remains true until you prove proof that your disagreement is backed by logical reasoning and facts.  
You have done no such thing. You're starting to resemble Veritas.

And you can teach me?
I may or may not be able to, not that it would matter.

First of all, technology has become much cheaper in the past 6 years (on average at least). And besides, who really has a hard drive measured in gigabytes anymore?    
Strawman argument.
I'm sure this is in no way a strawman argument.
It's a pure example of strawman fallacy. I never argued that "technology didn't become cheaper" did I? Don't attempt to use fallacies again, else we end up with nonsense as "Strawman nodes".  Roll Eyes

Yes, they're being sold and yes I plan to buy a 1/2 TB drive.
That's still plenty to run 20MB blocksize for several years, even if you falsely assume every single block is full. (and it's still a drive measured in terabytes)
20 MB per block x 6 blocks per hour x 24 hours a day x 365 days a year = ~1051 GB per year. Please explain how a 1/2 TB drive (aka 500 GB drive) would run for "several years".

It's quite easy, you just divide the blocksize by the average time it takes to find a block.
20 MB / 10 minutes = 2 MB per 1 minute. 2 divided by 60 = 0.03 MB/s. Let me tell you why your thinking is flawed (not that you're going to admit this). If a node is downloading at this speed, it will never catch up. Why is that? By the time that it downloads a 20 MB block, it is likely that another one will be created. The node would still be validating the previous block in addition to having the next one. I do wonder how long it takes to validate a 20 MB block on decent hardware though.

And what is the primary bottleneck then? I'm sure memory won't be a problem with blocksizes smaller than a few gigabyte.
Validation time.

a 2tb hard drive is only 800,00 kuna (im guessing your still in croatia) (£90 : $120 for those not wishing to convert kuna to western currencies)
No, I am not and have never been in Croatia.
legendary
Activity: 4424
Merit: 4794
Yes, they're being sold and yes I plan to buy a 1/2 TB drive.

500gb hard drive. well your the one that chooses to not think about the future, only you will be the one crying
cant blame bitcoin or anyone else if your hard drive fills up in 2.5 years+ (core 4mb weight)

a 2tb hard drive is only 800,00 kuna (im guessing your still in croatia) (£90 : $120 for those not wishing to convert kuna to western currencies)
not sure why you are even choosing 500gb

i feel like your actually trying to shoot yourself in the foot just to have a reason to cry in 2 years, even though 2tb is not a "data centre" cost and will last you for atleast 10 years (core 4mb weight)
legendary
Activity: 1106
Merit: 1005
If you limit the transaction size to 1MB, nothing changes from having a 1MB blocksize without a transaction size limit.
There may or may not be attack vectors that could work with 2x 1 MB transactions. Just because it seems safe, that doesn't mean that it will be.
The whole reason huge transactions are unsafe is because of quadratic scaling, which won't work if you split up the equation across two transactions that scale linearly with each other.       

       
Who would ever need to fill an entire block with 1 transaction?  
I'm not talking about normal usage when it comes to security problems.
So you agree there's no normal use case for 1MB or larger transactions, so why do you oppose limiting transactions to 1MB while increasing blocksize? That gets rid of your man argument (security) while also allowing more transaction throughput, and therefore more users.   

Are you mad because I can destroy your entire argument in 2 minutes of typing?

You are just disagreeing for the sake of disagreeing at this point.  
Said every person when losing their ground.

Sorry but I just destroyed your argument, and you have no ground to disagree on, except the right to disagree, but you have no actual logical reason to disagree.     
I have proven this to be factually correct, and it remains true until you prove proof that your disagreement is backed by logical reasoning and facts. 

   
That doesn't mean you can't look at other coins as an example.
It's one thing to fork something small and centralized, and another to fork Bitcoin.
TIL ETH is centralized. Yeah they have their differences, but centralization is not one of them.

Bitcoin would become the myspace of crypto
Stop being "spoon fed" (as franky1 would put it) by Ver & co.
I don't even know Ver, but from the few interviews I have heard from him he seems like a reasonable and nice guy, although I don't always agree with all he sais.

It does. You can't just say this every time someone disproves your statements.
It does not, as can be seen with your lack of experience in regards to large scale infrastructure.

And you can teach me?

First of all, technology has become much cheaper in the past 6 years (on average at least). And besides, who really has a hard drive measured in gigabytes anymore?    
Strawman argument.

I'm sure this is in no way a strawman argument.

If anything, your conjecture is based on a strawman argument, because you are defending imaginary nodes (strawman) that would be blocked out of being a node because they can't run an imaginary node on on imaginary system with a hard drive that belongs in the 90s and internet that is basically quite literally smoke signals.   

Any computer made after 2000 and even the most basic internet connection has no problem at all running a 20MB node. And with no problem at all I mean that it is barely noticeable that you are even running a node while at the same time actually using your computer for other tasks.

If anyone is having strawman arguments it's you, because you're using strawman nodes to back up your defense. I am talking about actual technology and actual nodes, that are not aaffected by larger block size in the slightest.

If you can find actual persons that actually will be affected by a larger blocksize, be my guest, I'd like to hear their testimonies.

And since no one is going to buy a hard drive of less than 1TB anyway (are they even sold anymore?) your argument is mood.      
Yes, they're being sold and yes I plan to buy a 1/2 TB drive.
That's still plenty to run 20MB blocksize for several years, even if you falsely assume every single block is full. (and it's still a drive measured in terabytes)

Even worse with network. Does anyone seriously have a bandwidth so low that 266kb/s is a problem? (that would be 20MB blocks).
You obviously aren't factoring in the primary bottleneck, but let's go with this. How did you derive this number, i.e. by calculating what?

It's quite easy, you just divide the blocksize by the average time it takes to find a block. Obviously, you would need internet faster than that to be actually useful as a node, but on average your internet would use that amount of data. When a new block is found, it would for a few seconds use more bandwidth, followed by a couple of minutes of almost no activity at all. The point is though that 266kb/s is ridicilously small, and everyone has internet orders of magnitudes faster than that, so even for the most basic internet user, the network usage would not even be noticable.

And what is the primary bottleneck then? I'm sure memory won't be a problem with blocksizes smaller than a few gigabyte.

legendary
Activity: 2674
Merit: 3000
Terminated.
If you limit the transaction size to 1MB, nothing changes from having a 1MB blocksize without a transaction size limit.
There may or may not be attack vectors that could work with 2x 1 MB transactions. Just because it seems safe, that doesn't mean that it will be.

Who would ever need to fill an entire block with 1 transaction?  
I'm not talking about normal usage when it comes to security problems.

You are just disagreeing for the sake of disagreeing at this point.  
Said every person when losing their ground.

   
That doesn't mean you can't look at other coins as an example.
It's one thing to fork something small and centralized, and another to fork Bitcoin.

Bitcoin would become the myspace of crypto
Stop being "spoon fed" (as franky1 would put it) by Ver & co.


It does. You can't just say this every time someone disproves your statements.
It does not, as can be seen with your lack of experience in regards to large scale infrastructure.

First of all, technology has become much cheaper in the past 6 years (on average at least). And besides, who really has a hard drive measured in gigabytes anymore?    
Strawman argument.

And since no one is going to buy a hard drive of less than 1TB anyway (are they even sold anymore?) your argument is mood.      
Yes, they're being sold and yes I plan to buy a 1/2 TB drive.

Even worse with network. Does anyone seriously have a bandwidth so low that 266kb/s is a problem? (that would be 20MB blocks).
You obviously aren't factoring in the primary bottleneck, but let's go with this. How did you derive this number, i.e. by calculating what?
legendary
Activity: 1106
Merit: 1005
1) You could limit the transaction size while still increasing the blocksize.
It's not a matter of 'could' or 'could not', but rather a matter of "should" or "should not". I disagree with those limitations.

If you limit the transaction size to 1MB, nothing changes from having a 1MB blocksize without a transaction size limit.

Who would ever need to fill an entire block with 1 transaction?  

You are just disagreeing for the sake of disagreeing at this point.      
2) ETH did fine.
We're talking about Bitcoin, not a mutable shitcoin.
That doesn't mean you can't look at other coins as an example. The main use of altcoins is to be a testbed for bitcoin, so that bitcoin can learn from their successes and mistakes. To prevent havng to make the same mistakes, while still benefiting from their successful projects.    
If bitcoin can keep up with the successful implementations of altcoins, while avoiding their mistakes, there will never be a reason for any altcoin to overtake bitcoin.    
However, if we stick our head in the sand and ignore altcoins altogether, some altcoin will eventualy shove bitcoin aside as old-fashioned and out-of-date. (Bitcoin would become the myspace of crypto)
3) Few shops actually directly accept bitcoin without an intermediary. Those intermediaries should be bitcoin-savvy enough to prevent damage to the merchants. Those merchants that do accept bitcoin directly probably know enough about it as well.
This argument has no relevance to what I said. You don't know how long it takes for those "intermediaries" to upgrade and test their custom implementations (hint: 28 days is ridiculous).
It does. You can't just say this every time someone disproves your statements.
4 & 5) The increased costs is only marginal.
A minimum of 2x increase is "marginal"?
First of all, technology has become much cheaper in the past 6 years (on average at least). And besides, who really has a hard drive measured in gigabytes anymore?    
Do you have any idea how long it takes for a TB to fill up on blocks of just a few MB? FYI a TB is a million MB.
Even a year worth of blocks only takes up a fraction of a home computer. Not a server, a regular home computer (even a laptop). If we increase the blocksize, it would only take up a larger fraction, but still it doesn't even fill an entire disk. So it would not actually cost anyone anything, unless their hard disk is already full. But even if someone's hard disk was full, he'd soon need a new drive anyway, because even without bigger blocks he'd run out of space soon.    
And since no one is going to buy a hard drive of less than 1TB anyway (are they even sold anymore?) your argument is mood.      

Even worse with network. Does anyone seriously have a bandwidth so low that 266kb/s is a problem? (that would be 20MB blocks).



rol)

 i laugh at your mindset
'big blockers want 2mb'  ........ (core wants 4mb)
'big blockers have a secondary barrier of 16mb'     (core has 32mb)

easy maths question.
2 and 16.... or 4 and 32. which is perceived as the real big blockers?

You're forgetting the part where they claim we want bitcoin to be a "get rich quick scamcoin"  

Because obviously the only reason we want bigger blocks is because a bigger block would magically cause the bitcoin price to become 20 times higher, which also is a bad thing.

what actual costs..
1 MB of data per full block -> 2 MB of data per full block. This equals to 2x increase.

oh i forgot you dont have a real node running on a home computer. you have an online AWS node with only probably 100gb storage
My node is not on any online service. Stop spreading lies.

try splashing out $300 and run a real node for once and be part of the decentralized network. that $300 will last you over 10 years
$300 won't last you 10 years.

Core's official roadmap claims to have Segwit and LN active in April/July 2016 respecitively
Both are false. Core did deliver Segwit in April, but there was no mention of activation by that time. "LN active" is a pure lie. There are other groups that are developing Lightning.

In my opinion, people make way too big a deal about an increase from 1MB to even 2MB, while 2MB blocks don't even hurt anyone (heck, even 20MB blocks wouldn't hurt anyone).        
Statements like this one make people ignorant fools by default.

You don't pay for data directly, most people already own a computer, and they use nowhere near 100% capacity on their internet nor on their hard drive.

Increasing the maximum block size doesn't change this (unless you increase it to terabytes, but  am not asking for terabytes)    

Besides, not every block will be full anyway. Every block is full now, but the whole point about bigger blocks is that not every block should be full in the first place (there needs to be some headroom).    

I don't know about you, but we haven't paid per MB of internet usage since the 90s. Or were you using your mobile phone as a node with cloud storage? Because in that case, you're doing it wrong.

By the way, a $300 computer can last you 10 years easily, you're not using it for gaming, you're using it as a node.

Also, where is segwit then? And if t's already deployed like you said, then why are they promising to deploy it in 2017 now? It's already active right?
legendary
Activity: 1778
Merit: 1043
#Free market



Interesting, freedom of choice Smiley no one will force you to run a software... never.
legendary
Activity: 2674
Merit: 3000
Terminated.
what actual costs..
1 MB of data per full block -> 2 MB of data per full block. This equals to 2x increase.

oh i forgot you dont have a real node running on a home computer. you have an online AWS node with only probably 100gb storage
My node is not on any online service. Stop spreading lies.

try splashing out $300 and run a real node for once and be part of the decentralized network. that $300 will last you over 10 years
$300 won't last you 10 years.

Core's official roadmap claims to have Segwit and LN active in April/July 2016 respecitively
Both are false. Core did deliver Segwit in April, but there was no mention of activation by that time. "LN active" is a pure lie. There are other groups that are developing Lightning.

In my opinion, people make way too big a deal about an increase from 1MB to even 2MB, while 2MB blocks don't even hurt anyone (heck, even 20MB blocks wouldn't hurt anyone).         
Statements like this one make people ignorant fools by default.
legendary
Activity: 1106
Merit: 1005
I don't think it is "mindless fear" to point to Ethereum's failed hard fork and point out that it permanently split the network. This caused significant losses for custodians---Coinbase lost ETC and still hasn't repaid their customers. BTC-E was replay attacked and lost all of their customers' ETC; they won't be repaying it. The results would have been disastrous if Kraken and Poloniex didn't have the foresight to ignore the Ethereum Foundation's advice to ignore ETC and not repay their customers their money. Replay attacks were commonplace, and many users lost money in trying to spend on only one chain or the other.
Seems like mindless fear to me, the replay attack has been fixed on all of the proposed Bitcoin forks, it is rather trivial to fix actually. The ethereum foundation purposely decided not to fix this particular issue, I thought that was a mistake. Splitting Bitcoin as a minority would not cause such problems at all, custodians also need to be more responsible in such a situation and take it into account. Some of those custodians simply just did not believe ETC would survive, now we know better.
That's not true. If Classic merges an update to change transaction format (not just add a new transaction format), it will be true for Classic. XT and Unlimited offer no replay protection. This is actually not just a technical issue---many that believe that a clean hard fork (one network) is possible don't want explicit replay protection because it promotes the idea that multiple blockchains will emerge. This was partially why Ethereum did not include replay protection in their fork; they simply assumed the original chain would die. The very idea of including replay protection in a fork is to make both networks viable (i.e. to enforce a network split). In the past, Gavin became quite upset at the suggestion that a hard fork could split the network---I'm curious about his thoughts on this.
I suppose that is why I now support splitting the chain, the alternative chain would simply have alternative clients that support it, solving the replay attack on both networks. I think that you are correct in thinking that a non controversial hard fork is no longer possible unless it is done through Core, who seem unlikely to increase the blocksize limit anytime soon. Therefore the only solution for people like myself who prefer that Bitcoin stays true to the original vision of Satoshi, is splitting the chain, after all Satoshi was a big blockist as well. Wink


Part of the problem in Ethereum is the heavily centralized development under the Ethereum Foundation, which has no public review/consensus mechanism. Vitalik said "let's fork" so mining pool admins ignored their miners, client developers forked their clients by default (no user choice whatsoever) and the fork came from the top-down. This makes user consent very difficult to gauge. Even in this context, Ethereum could not successfully hard fork.
Ethereum presently has the same consensus mechanism as Bitcoin, users can choose to use Ethereum Classic instead, this is what gives people the freedom of choice, that is part of the consensus mechanism of Bitcoin as well and soon this will happen to the Bitcoin network as well.

The effects of splitting the Bitcoin network and increasing the supply of "bitcoins" across multiple blockchains could be far worse for Bitcoin's value proposition than a network split in Ethereum.
Splitting the network does not worsen Bitcoins value proposition, since the share of total Bitcoins remains the same across all chains for investors, which means it does not create any type of monetary inflation, it protects the value of investors. Furthermore because it is already relatively easy to do this with a small minority it should already be a part of Bitcoins value proposition, if you are not taking this feature into account you are not truly evaluating the value of Bitcoin, for me it actually improves the value proposition of Bitcoin since I perceive this feature as being a crucial part of the governance mechanism.
Within a particular network, there has not been inflation, but you need to consider public perception and a confused userbase deciding among multiple networks, each with a supply of 21 million BTC. Again, I wonder if you could point to the protocol documentation or description from the whitepaper that suggests that breaking the consensus rules are "a crucial part of the governance mechanism"? Like I said, go ahead and fork....just don't be surprised when no one refers to your fork as Bitcoin.
Exactly, a confused user base does not change the fact that investors are still protected under such a mechanism. Not everything is in the whitepaper, but the consequences and reality of the rules that exists are within the code and the world for all to see. Because this is possible, it should be considered as part of the design of Bitcoin itself and considered inevitable from happening, especially considering the nature of human behavior.

If find it sad and surprising that so many people seem to be in favor of core, as opposed to classic/unlimited. I wouldn't be surprised if they just went with the 'default' option not actually even knowing that by downloading the 'default' wallet they actually vote in support of core.    

Core's official roadmap claims to have Segwit and LN active in April/July 2016 respecitively, but it's already september and neither of them are active now. Mainwhile blocks are mostly full and no solution is offered by core.    

By the time segwit and LN go online (if ever) it's too little too late. Mainwhile, bitcoin is losing marketshare rapidly, and due to the network effect, this could have permanent disastrous results for bitcoin.    

In my opinion, people make way too big a deal about an increase from 1MB to even 2MB, while 2MB blocks don't even hurt anyone (heck, even 20MB blocks wouldn't hurt anyone).        
legendary
Activity: 4424
Merit: 4794

4 & 5) The increased costs is only marginal.
A minimum of 2x increase is "marginal"?


what actual costs..

a 2tb hard drive does not cost more if its storing 52gb or 104gb.. and in 20 years-40 years when its full that hard drive cost is marginal
wait. lets put it into cores 4mb preference
10 years usage

most people change their computers every 5 years anyway

You can't know this. Example: I have to upgrade my node soon due to inadequate amount of storage on it.

oh i forgot you dont have a real node running on a home computer. you have an online AWS node with only probably 100gb storage

try splashing out $300 and run a real node for once and be part of the decentralized network. that $300 will last you over 10 years
($30 a year, $2.50 a month) much cheaper then amazons $15 a month
Pages:
Jump to: