Compare
Four documents, the same five questions.
No throughput league table and no yield. The cells are what this library is willing to say about the text.
| Question | Fork identifier for chain compatibility checks |
|---|---|
| What the text proposes | EIP 2124, Fork identifier for chain compatibility checks. Currently nodes in the Ethereum network try to find each other by establishing random connections to remote machines "looking" like an Ethereum node (public networks, private networks, test networks, etc), hoping that they found a useful peer (same genesis, same forks). |
| Who may write | Péter Szilágyi , Felix Lange |
| What is settled | Currently nodes in the Ethereum network try to find each other by establishing random connections to remote machines "looking" like an Ethereum node (public networks, private networks, test networks, etc), hoping that they found a useful peer (same genesis, same forks). |
| Load-bearing assumption | A peer protocol is not a consensus rule. A peer can disconnect. A block is still valid or not on its own. |
| What this library says afterwards | Status in the source: Final. A reading of the public specification, not a copy of it and not a certification. |
| Rights | Official external source only |