3675: Bring back extraData (#3982)

This commit is contained in:
Mikhail Kalinin 2021-09-17 18:25:50 +06:00 committed by GitHub
parent b381064c19
commit e0a90ecc09
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -74,7 +74,6 @@ Beginning with `TRANSITION_BLOCK`, a number of previously dynamic block fields a
|-|-|-|
| **`ommersHash`** | `0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347` | `= Keccak256(RLP([]))` |
| **`difficulty`** | `0` | |
| **`extraData`** | `b''` | `RLP(b'') = 0x80` |
| **`mixHash`** | `0x0000000000000000000000000000000000000000000000000000000000000000` | |
| **`nonce`** | `0x0000000000000000` | |
| **`ommers`** | `[]` | `RLP([]) = 0xc0` |
@ -167,10 +166,6 @@ This change introduces an additional validity rule that enforces the replacement
After deprecating the proof-of-work the notion of difficulty no longer exists and replacing the block header **`difficulty`** field with `0` constant is semantically sound.
### Deprecating `extraData`
The **`extraData`** field is deprecated in favour of the corresponding **`graffiti`** field of the beacon block.
### Changing block validity rules
The rule set enforcing the PoW seal validity is replaced with the corresponding PoS rules along with the consensus upgrade as the rationale behind this change.