status-im/EIPs
2
0
Fork 0
mirror of https://github.com/status-im/EIPs.git synced 2025-02-22 11:48:19 +00:00
Code Issues Projects Releases Wiki Activity

Clarify validation conditions in EIP 3675 "The Merge" (#3723)

Browse Source 
* whitespace

* clarify semantics of POS validity events

* Update EIPS/eip-3675.md

Co-authored-by: Mikhail Kalinin <noblesse.knight@gmail.com>

Co-authored-by: Mikhail Kalinin <noblesse.knight@gmail.com>
This commit is contained in:
Alex Stokes 2021-08-16 09:28:39 -07:00 committed by GitHub
parent b0dd434036
commit 99822ee034
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
EIPS/eip-3675.md
View File

@ -81,8 +81,8 @@ Beginning with `TRANSITION_BLOCK`, the block validity conditions **MUST** be alt
* Remove all validation rules that are evaluated over the list of ommers and each member of this list.
* Add verification of the fields noted in [block structure](#block-structure) as their specified constant value.
* Add verification of block validity with respect to the PoS consensus rules, i.e. assert that there **MUST** be a corresponding event for the block to consider it valid. Such events are limited to the following:
* A `POS_CONSENSUS_VALIDATED` event considering the block or any of its descendants as valid.
* A `POS_CHAINHEAD_SET` event, including the `POS_BLOCK_FINALIZED` form of this event, designating the block or any of its descendants as the head of the canonical chain.
* A `POS_CONSENSUS_VALIDATED` event considering the block or any of its ancestors as valid.
* A `POS_CHAINHEAD_SET` event, including the `POS_BLOCK_FINALIZED` form of this event, designating the block as the head of the canonical chain.
*Note*: If one of the new rules fails then the block **MUST** be invalidated.