Skip to content

Stargazer

Pre-release
Pre-release
Compare
Choose a tag to compare
@djrtwo djrtwo released this 17 Mar 03:16
· 3623 commits to master since this release
v1.1.0-alpha.1
3ce090f
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Release

v1.1.0-alpha.1 is the first pre-release for the upcoming Altair upgrade.

Although all core features are in place, we expect some iteration as client teams begin to implement.

PR showing full diff can be found here: #2230

Phase 0

Beacon chain

Stable with respect to features!

Note: process_final_updates was removed and replaced with sub-functions mapping to the different components of prior functionality. This non-substantive change facilitates cleaner spec writing in subsequent phases.

Networking

Stable other than one minor gossip validation added -- require gossip blocks to have a higher slot than their parent (#2196).

Weak subjectivity

Updated with extended weak subjectivity period calculations and sample values.

Altair

Beacon chain

All features for Altair upgrade in place. Features include:

  • Sync committees to support light clients
  • Incentive accounting reform to reduce spec complexity
  • Modified attestation rewards to increase incentive compatibility
  • Per validator inactivity leak
  • Penalty parameter updates toward maximally punitive parameters

Note: No major additions nor subtractions to this feature-set are expected unless unless unexpected security or engineering issues are uncovered. That said, minor adjustments based on engineering feedback should be expected.

Fork

Provides a function for upgrading the Phase 0 BeaconState to an Altair BeaconState.

ALTAIR_FORK_SLOT TBD.

Validator

Core Altair features in place, including:

  • Including sync committee aggregates in beacon blocks
  • Handling new validator sync committee assignments

Networking

Core Altair features in place, including:

  • Upgraded beacon_block gossip topic for new Altair type
  • Added gossip topics and validations for sync committee messages
  • Upgrade path for Req/Resp domain to handle cross-fork types

Note: Some of the particulars of the sync aggregation protocol might still be refined before the main release of v1.1.0 specs.

Sync protocol

Describes a minimal version of the light client sync protocol that leverages the new Altair sync committees.

This protocol is illustrative of how to build light clients using this new feature, but this should not be considered exhaustive with respect to viable designs.

Phase 1 (sharding)

Sharding spec is considered unstable and should only be used for educational purposes. Expect deep changes.

Testing, Repo, etc

  • Add Altair test vectors along with new fork function unit tests (#2220)
  • Compress tests with snappy, remove YAML duplicates (#2097)
  • Bump py_ecc to v5.2.0 (#2223)
  • Disable phase 1 tests from CI and generators
Assets 2