> You are wrong, 

Like that time an inflation bug was introduced into bitcoin core v0.14 and not discovered until v0.16.2?

> You are wrong

Yet you have no response to these facts

> Ethereum could do with a fellow like you

That's rich coming from a shitcoiner such as yourself

> We do need more opcodes for expressability

You really are a contentious fellow Justin. You are wrong, of course, as usual, and your ignorance just comes across as combative. 
Ethereum could do with a fellow like you, this matches their general philosophy.

ZezzebbulTheMysterious

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.

bitdevs

Thinking about building a new Bitcoin node client in nodejs

anon

> 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.