Progress without progress
Release
Patch to critical state transition bug found by @daejunpark during formal verification work under @runtimeverification. Thank you!
There was an untested path that allowed for the proposal of multiple (unbounded!) blocks on the same slot in the same chain. This was not the intention and, because it was untested and unclear, was implemented differently across clients. This has been patched in all affected clients currently on public testnets.
PR showing full diff can be found here: #1818
Phase 0
Beacon chain
- Disallow multiple block proposals for same slot within a single chain [#1818]
Fork choice
Stable!
Validator
Stable!
Networking
Stable!
Deposit contract
Stable!
Simple Serialize
Stable!
BLS
Stable!
Phase 1 spec (warning: not stable)
Stable!
Light client spec (warning: not stable)
Stable!
Testing, Repo, etc
- Refactor some testing to be tighter about the application of blocks upon states at the
block.slot
[#1818]