go-ethereum VS parity-ethereum

Read the q&as on GitHub. Total shambles. No plan, few commits. bizarre replies. Coinbase eventually had to submit a Pull Request as all support channels closed/unanswered. Read it and weep. Last post 15hrs ago, the soap-opera continues. https://github.com/ethereumpow/go-ethereum/pull/17

That is what they have claimed for a while now. Their geth fork has yet to actually implement this chain ID, and they actually don't plan to do so until after the merge has occurred. So there will be some initial chaos as the miners sort things out, but presumably at some point the team will provide the proper code to carry out the fork and enough people will run it to establish a stable network. Presumably. I'll believe it when I see it.

This is the Repo where you can see if the chain ID has been updated: https://github.com/ethereumpow/go-ethereum/blob/master/params/config.go

This was pointed out to them multiple times on their Github repository (https://github.com/ethereumpow/go-ethereum/pulls) and a poll was taken to chose a more appropriate ChainID ( https://www.rcv123.org/results/rr6xjagxbmoR8CSKUSobW6/qtGJMHK7pBeugsJ1KFpv3S) which settled on 1111, but has been ignored.

The fun bit is in the pull requests: https://github.com/ethereumpow/go-ethereum/pulls

The library killer's confession contains the bugged contract address, and some post-mortem links.

Not really. If one of the clients interpreted a part of the spec in a different way, event if they are right, they would have change it to follow an officially approved code because that's the consensus.

There are examples like https://github.com/openethereum/parity-ethereum/blob/55c90d4...

$150 Million of ETH gets locked up in Parity multisig contracts after a user "accidentally" kills a referenced library.

Case in point. Here's the line of code that introduced a bug in a contract that was ultimately worth $32M:

https://github.com/openethereum/parity-ethereum/blame/4c3217...

https://blog.openzeppelin.com/on-the-parity-wallet-multisig-...

If you look at the associated pull request, it added over 2K lines of code, and removed almost 1K, spread across 20 different files. 5 files have changed so much, GitHub doesn't even show their diff by default.

It was reviewed by one person in a single day.

for those that don't know, Gavin Wood was responsible for writing the Parity Multi-Sig wallet contract on Ethereum, which was famously killed by mistake due to a bug that was discovered by a developer who was playing around with the contract. This caused 513,743 ETH to be permanently frozen ($1,842,796,141 USD as of today).