A community for the latest discussions about the cutting edge of crypto design, it's culture and significant crypto news. Decentralize everything. Check out our [Community Guidelines](https://relevant.community/crypto/post/6122269e61d1cd005a877277/62427d3ed587ad005b647828)
53475 Members
We'll be adding more communities soon!
© 2020 Relevant Protocols Inc.
A community for the latest discussions about the cutting edge of crypto design, it's culture and significant crypto news. Decentralize everything. Check out our [Community Guidelines](https://relevant.community/crypto/post/6122269e61d1cd005a877277/62427d3ed587ad005b647828)
53475 Members
We'll be adding more communities soon!
© 2020 Relevant Protocols Inc.
Relevant
Hot
New
Spam
Relevant
Hot
New
Spam
0
116
0
116
"A hard fork that split Ethereum’s chain in two was activated on purpose, calling into question Ethereum’s client coordination."
"A hard fork that split Ethereum’s chain in two was activated on purpose, calling into question Ethereum’s client coordination."
>"A hard fork that split Ethereum’s chain in two was activated on purpose, calling into question Ethereum’s client coordination."
>"A hard fork that split Ethereum’s chain in two was activated on purpose, calling into question Ethereum’s client coordination."
The split resulted from a code change that was surreptitiously inserted into a previous Geth update; some Ethereum node operators ignored the update, which ironically was meant to prevent the very split that occurred.
The split resulted from a code change that was surreptitiously inserted into a previous Geth update; some Ethereum node operators ignored the update, which ironically was meant to prevent the very split that occurred.
>"A hard fork that split Ethereum’s chain in two was activated on purpose, calling into question Ethereum’s client coordination."
>"A hard fork that split Ethereum’s chain in two was activated on purpose, calling into question Ethereum’s client coordination."
Some low-ranking comments may have been hidden.
Some low-ranking comments may have been hidden.