pull down to refresh

Don't -- This adds very little except fork risk that puts your users money at risk. This applies to Knots too -- Don't touch it. Its a menace.
Bitcoin Core is Bitcoin.

"I don't believe a second, compatible implementation of Bitcoin will ever be a good idea. So much of the design depends on all nodes getting exactly identical results in lockstep that a second implementation would be a menace to the network. The MIT license is compatible with all other licenses and commercial uses, so there is no need to rewrite it from a licensing standpoint." -- Satoshi, 2010

There is very little reason to do this (beyond your education in the protocol), and many reasons not to.

this +100

reply

I agree with your comment... I'm a bit more conservative.

reply
145 sats \ 5 replies \ @justin_shocknet 6 Jul -420 sats
Bitcoin Core is Bitcoin.

Retarded comment of the day award.

a second, compatible implementation of Bitcoin will ever be a good idea .. a menace to the network

Literally every new version of Core is a second compatible implementation, relative to older versions pre-existing on the network.

If Core pushes a bad update, it effects much of the network in a uniquely dangerous way. A diverse network of many implementations don't carry this risk as damage is isolated to the users of that implementation and not the network as a whole.

The same systems that keep continuity from one Core version to the next applies equally to new implementations, test vectors. A solved problem.

BTCD has been reliable for years and powers most of the Lightning Network.

Afaik Libbitcoin consensus has too been stable for years.

Since every new Core version is the only potential menace to the network at large, it's far better there be more implementations, causing more frequent issues, as a trade-off for limiting the damage by some future Core version going wrong.