Live data from Hacker News

Ethereum Fork Fails on OpenEthereum

github.com

21–30 of 108 posts

Re: Ethereum Fork Fails on OpenEthereum

#21
Fireblocks (massive institutional settlement platform for crypto-to-crypto and crypto-to-fiat transactions (like bank-size transactions) is on openethereum too -- all the settlements are completely backed up right now and tether is going really bid

Re: Ethereum Fork Fails on OpenEthereum

#22
post #19

Earlier quoted context omitted.

Theoretically there’s a protocol standard, and every client implementation is equal. Functionally, whatever Geth does is the actual standard because a supermajority of nodes run Geth.

This is not true, and I can say that because I work on Geth. We take great care to ensure that all clients behave according to the specification, and Geth has had similar faults in the past.

Surely it doesn't matter what the specification says? If the majority of the hashpower is using an implementation which deviates from the spec, then the blockchain will follow that code and not the 'correct' version. By the time the devs have fixed the bugs, it will be too late and too costly to roll back the chain and reverse all the subsequent transactions.

Re: Ethereum Fork Fails on OpenEthereum

#23
post #16
post #13

Earlier quoted context omitted.

The fix is in https://github.com/openethereum/openethereum/pull/364 Actually, it's this commit of the PR: https://github.com/openethereum/openethereum/pull/364/commit...

386 files changed? This has to include more than just the fix, right?

[deleted]

Re: Ethereum Fork Fails on OpenEthereum

#24
post #16
post #13

Earlier quoted context omitted.

The fix is in https://github.com/openethereum/openethereum/pull/364 Actually, it's this commit of the PR: https://github.com/openethereum/openethereum/pull/364/commit...

386 files changed? This has to include more than just the fix, right?

Looks like they've extracted it to a separate hotfix PR here:

https://github.com/openethereum/openethereum/pull/366

Re: Ethereum Fork Fails on OpenEthereum

#25

Earlier quoted context omitted.

No. It’s “just” a client issue, and OpenEthereum is “only” used by ~11% of the nodes. I believe the former name is Parity, which had a major bug related to frozen coins some years ago. See https://mobile.twitter.com/etherscan/status/1382662485832994...

Theoretically there’s a protocol standard, and every client implementation is equal. Functionally, whatever Geth does is the actual standard because a supermajority of nodes run Geth.

https://etherscan.io/nodetracker only shows 55% on geth; I wouldn't call that a super majority.

EDIT: Actually, that page shows 15% on openethereum so we must be looking at different sources. Where did you get 11% on openethereum?

Re: Ethereum Fork Fails on OpenEthereum

#28
Satoshi wrote in 2010: "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." https://bitcointalk.org/index.php?topic=195.msg1611#msg1611

In ETH land, the wise guidance of Satoshi is regularly ignored.

Re: Ethereum Fork Fails on OpenEthereum

#30

Satoshi wrote in 2010: "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." https://bitcoint…

So much for a protocol eh ...
Post reply on HN