Clarity
Release
This release is all about tightening it up. A redundant state transition check was removed (#1738), a few networking items were clarified (#1708, #1730, #1736, #1744), and some gossip conditions were made a bit more strict (#1694, #1706, #1710).
A nice side effect of the tightened gossip conditions is a 32x reduction in the size of a few caches while simultaneously increasing the DoS security. Thanks @paulhauner for pointing those out!
With our new commitment to backwards compatibility within semi-major versions (thanks @q9f!), v0.11.2
is fully backwards compatible with v0.11.1
, so keep testing those testnets 💻 .
PR showing full diff can be found here: #1743
Phase 0
Beacon chain
- Remove redundant check in
is_valid_indexed_attestation
[non-substantive] (#1738) - Clarify that state transitions with
uint64
under- and over-flows are invalid (#1739)
Fork choice
Stable!
Validator
Stable!
Networking
- Tighten restriction on "seen" attestation (#1694)
- Notes on peer discovery/ENRs prior to genesis (#1708, #1730)
- Clarify attestation gossip condition and make "seen" cache per-epoch instead of per-slot (#1706)
- Aggregate gossip condition "seen" cache per-epoch instead of per-slot (#1710)
- Clarify block range request description (#1736)
- Add missing note about "valid" attestation in gossip conditions (#1744)
- Include fork digest in example gossip topics (#1754)
Deposit contract
Stable!
Simple Serialize
Stable!
BLS
Stable, but draft 7 of hash-to-curve is expected to be released very soon and make it into a v0.12
release in the spec repo.
Phase 1 spec (warning: not stable)
Continued work on refining Phase 1 specs
Warning The Custody Game challenge-response is currently missing, but will be reintroduced soon when the core Phase 1 shard chain design stabilizes. Client teams looking to prototype Phase 1 should first focus on shard data mechanics, while stubbing out custody game logic.
Light client spec (warning: not stable)
Light client sync spec is under redesign in the context of the phase 1 redesign. The current light client spec can be used for general educational purposes to understand the approach we are considering, but will see heavy redesign after phase 1 stabilizes.
Testing, Repo, etc
- Update remerkleable and config loading (#1709)