I just read about Bitcoin Core and Bitcoin-XT, and I want to know what is the difference between Bitcoin Core and Bitcoin-XT?
And which is better Bitcoin Core or Bitcoin-XT?
Bitcoin Stack Exchange is a question and answer site for Bitcoin crypto-currency enthusiasts. It only takes a minute to sign up.Sign up to join this community
The two pieces of software, Bitcoin Core and Bitcoin-XT, are very similar. Bitcoin-XT is actually just a fork of Bitcoin Core with some features added that Bitcoin Core developers didn't deem appropriate, such as a larger block size (BIP 101) and relaying of double spends.
Bitcoin Core is more up-to-date with all of the work that the community doing. Additionally, Bitcoin-XT now has a different consensus protocol regarding the maximum size of blocks. There has been much debate within the bitcoin community about if/how/when to increase the artificially imposed block size limit (of 1 MB), and one attempt to resolve this debate is being done through Bitcoin-XT.
The Bitcoin-XT README.md has these notes on how it is different than Bitcoin Core:
Support for larger blocks. XT has support for BIP 101 by Gavin Andresen, which schedules an increase from the one megabyte limit Bitcoin is now hitting.
Relaying of double spends. Bitcoin Core will simply drop unconfirmed transactions that double spend other unconfirmed transactions, forcing merchants who want to know about them to connect to thousands of nodes in the hope of spotting them. This is unreliable, wastes resources and isn't feasible on mobile devices. Bitcoin XT incorporates work by Tom Harding and Gavin Andresen that relays the first observed double spend of a transaction. Additionally, it will highlight it in red in the user interface. Other wallets also have the opportunity to use the new information to alert the user that there is a fraud attempt against them.
Support for querying the UTXO set given an outpoint. This is useful for apps that use partial transactions, such as the Lighthouse crowdfunding app. The feature allows a client to check that a partial SIGHASH_ANYONECANPAY transaction is correctly signed and by querying multiple nodes, build up some confidence that the output is not already spent.
DNS seed changes: bitseed.xf2.org is removed as it no longer works, and seeds from Addy Yeow and Mike Hearn are (re)added to increase seed diversity and redundancy.
So, if you support these changes and/or the possible future changes on the consensus-block-size-limit, run Bitcoin-XT. The releases are available here: https://github.com/bitcoinxt/bitcoinxt/releases
Core. Bram Cohen has a good writeup on medium
The upcoming ‘crisis’ which is being used as a justification for a hard fork is something which it’s easy to convince people who aren’t very familiar with the technology will be a disaster. There’s a hard limit on the rate which transactions can happen, about five per second, and the transaction rate in bitcoin has been approaching that over time. We’re going to hit a wall! The sky is falling!
So what happens when that limit is reached?
Transaction fees go up.
Literally, that’s all that happens. That’s the big ‘crisis’. What’s being claimed is: Transaction fees might go above two cents! The sky is falling! I am not exaggerating.
Raising the block size limit is the idea of Gavin Andresen, former Bitcoin lead developer, who initially went around to core developers and players in the Bitcoin ecosystem trying to convince them that it should be done. The core developers had reactions ranging from neutral to vitriolically against it. Rather than accept this strongly negative reaction as a sign that his idea is a bad one, or attempting to work on some kind of compromise proposal, Gavin’s now blaming the arguing on a lack of benevolent dictator or clear voting process. There are several obvious problems with this. In projects which have a real Benevolent Dictator For Life, that person was the one who created the project. Gavin didn’t invent Bitcoin. He isn’t even a Bitcoin developer any more. He resigned his position as lead developer a year ago, and has been largely inactive since. Using a voting process, or even a system of rough consensus among core developers would cause his proposal to be quickly rejected. It’s only the exertion of outside political force which has forced it to be taken seriously.