@dlight sorry man I pretty much totally disagree with you here
@Adam
I'm extremely surprised that LTB would be supporting this obvious attempt at a "coup d'etat" against the Bitcoin system. To put control over the system in the hands of one guy is nuts.
That's not really what is happening here. There are already several implementations of bitcoin which are run by different teams of developers (and perhaps some lone wolfs). These are the systems that run the back end of everything you can do in the bitcoin world. Such as BTCD, libbitcoin, Bits of Proof, BitcoinJ, picocoin, BitCore, Electrum Server, Ufasoft Coin, NBitcoin, caesure, Toshi, and of course Bitcoin Core, BitcoinXT and other variants of Bitcoin Core. Although IIRC only Bitcoin Core (the "reference client") and it's variants have 100% full mining functionality, but that is a separate issue already being worked on (via consensus libraries anybody can use)
Also IIRC Gavin actually has full administrative access to the Bitcoin Core repository and could just kick out all the other people with commit access if he wanted to, so really that project has been "controlled" by one guy the entire time. Correct me if I'm wrong, he might have handed the reigns over to another dev (forget the name at the moment)... but either way that's just how projects on GIthub work. One person is the owner of the project, and they can accept or reject changes from people or allow others to accept changes on their behalf (commit access). That doesn't mean though that they can magically force everyone to download and use any code they feel like. And because it's open source, any attempt at doing something fishy quickly becomes obvious.
@Cryptonaut's statement "For the record, at LTB we will be switching all our nodes over to Bitcoin XT to ensure we stay on the proper chain when the fork is triggered early next year."
is clearly stating that the LTB network is taking sides - the opposite of neutrality.
Yeah, I knew when I wrote that that I would get some shit for it. I reworded it a little to clarify a bit more. We actually haven't switched our nodes to XT yet because we need to get a patch called "addrindex" adapted to it, which is a requirement for using Counterparty (also I'v been travelling a fair amount this month). Also as @adam has mentioned, it's less about XT specifically and more about making sure we are always on the chain with majority hashrate and if a fork occurs we will receive little or no interruptions. Because we are not miners, our choice of backend client doesn't really matter to the network.
The whole point of a distributed system like Bitcoin is that it should be a set of rules that are extremely hard for anyone to alter.
I don't really see how this whole process so far has been "easy", and it's far from over. Don't forget that this debate has actually been going on for years, and look at how intense it has gotten in the past few months with still no final resolution. You can write entire books out of the arguments back and forth that have been made...
The idea that one guy (using the Gavin's name recognition) can fork the network is outrageous and pretty much defeats the whole purpose of crypto-currency.
Yes Gavin is well known and well respected (for most people anyways) in this space, and yes him and Hearn were the ones to pull the fork-the-project card.. but they still have to convince everyone else to implement the same protocol changes and/or use the BitcoinXT client instead. Nobody is in favour of XT or BIP101 because Gavin is Gavin or Mike is Mike... it's because the numerous arguments they have laid out just so happen to make sense. I couldn't care less if it was Gavin Andresen or an anonymous user named CheeseBurg3rs69. Plus, the Bitcoin Core project could just patch over the BIP101 implementation at any time and effectively stop the exodus to the BitcoinXT project in it's tracks.
While it probably doesn't hurt anything to increase the block-size to 8MB - the further increases up to 8GB are extremely questionable - opening the network to attack in the future.
8GB won't be for 20 years. In 1995, a 10GB harddrive cost something like $2000, 64MB of ram for $150 and internet access was available at a speedy 56Kb/s over dial-up. Today, you can get 1,000GB harddrives for like $30, 4,000MB sticks of ram for $25 and some of the top internet speeds available in the world clock up to 1,000Mb/s for both uploads and downloads. That means already with todays fastest connections, you would be able to download full 8GB blocks in around 8 seconds. Thats 1,000 times larger than what the initial 8MB limit will be over the next couple years. Computer technology may or may not improve at the same rate that it has been over the next 20 years, but it's hard to believe that 8GB will be anything to worry about by that time. By then, we will be measuring consumer disk space in petabytes or maybe even exabytes
Plus there are numerous other changes to the XT code which are not even being discussed. Why should all of Mike Hearn's pet projects suddenly become adopted with no discussion? Not to mention all of his future pet projects.
Well for one XT is just one project, so I don't see how people using XT all of a sudden means mass adoption for his other projects like Lighthouse and BitcoinJ. But sure, let's talk briefly about the additional changes in BitcoinXT (there aren't many)
You can see a list of patches over on the website here: https://bitcoinxt.software/patches.html
- "Bigger blocks"
So as many have said - increasing the blocksize is just a stopgap measure until far more scalable solutions - like payment channels are introduced. Solutions which could handle the many orders of magnitude increases that will be required for Bitcoin to become widely adopted globally.
Yes and no. It's a step along the way and definitely not the final solution, but we also can't sit around and wait for someone to find the "perfect answer" to scalability, when we already know how to easily bump up the current network a few notches. Payment channels also have their own problems, such as the fact that they require funds to be locked up for periods of time (if you can only open and close one channel per year.. well I sure hope you have a whole years worth of income handy), are semi-centralized, take fees away from miners (the ones securing the network), and of course they don't even really exist yet anyways, it's all just on paper.
We need to remember that these increases tend to happen all at once - not gradually. The network needs to be able to very rapidly explode in size without choking. Just altering the blocksize doesn't achieve this.
Sure. BIP101 with 8MB doubling every 2 years gives us some solid predictability of the network limits so that we can plan accordingly.
But allowing a coup just to make this temporary fix - is crazy. As the person claiming to be Satoshi said - it will give Bitcoin the appearance of a failed experiment - since it will give dictatorial control to a single person - one who has vowed to do whatever he wants regardless of what the community thinks.
As explained above, no single person actually has control here.. there are no dictators in Bitcoin. Multiple competing implementations are healthy for the network and allow progress to be made instead of everyone getting caught up in a deadlock because no one wants to make a decision or someone is being too stubborn. Here is an interesting article that came out today from Meni Rosenfeld about forks.