github ObolNetwork/charon v1.0.0-rc5

latest releases: v1.0.0-rc7, v1.0.0-rc6
pre-release14 days ago

v1.0.0-rc5 - 2024-06-12

Obol Logo

Warning

This is the fifth release candidate for our first major Charon release! Unless you want to test this rc, you should wait until a full v1.0.0 is published and announced.

As detailed by our version compatibility, being a major release, Charon v1.0.0-rc5 is not fully-backwards compatible with v0.x.x releases. Block proposals are not compatible between the versions, so once your cluster begins the upgrade, please upgrade all nodes promptly to ensure readiness for a proposal opportunity should one occur.

Breaking changes

  • Full support for beacon spec produceBlockV3 endpoint has been implemented: DutyProposer supports now both blinded and unblinded blocks, while DutyBuilderProposer has been deprecated.
    • This means you should remove the extra validator configuration added during previous versions of charon, consult the prior release to see what flags to remove to default to the lastest version of block proposals.

Compatibility Matrix

This matrix details the combination of beacon node + validator clients and their corresponding versions the Obol team have tested with this charon release. More validator and consensus client will be added to this list as they are supported in our automated testing framework.

Legend

  • ✅: All duties succeed in testing
  • 🟡: All duties succeed in testing, except non-penalised aggregation duties
  • 🟠: Duties may fail for this combination
  • 🔴: One or more duties fails consistently
Consensus 👇 Validator 👉 Teku v24.4.0 Lighthouse v5.2.01 Lodestar v1.19.0 Nimbus v24.3.0 Prysm PR Remarks
Teku v24.4.0 🟡 Teku bn needs the --validators-graffiti-client-append-format=DISABLED flag in order to produce blocks properly.
Lighthouse v5.1.3 🟡 🟠 Lighthouse vc are only failing aggregation duties, which are not directly penalised but impact network density at high scale.
Nimbus v24.3.0 🔴 🟡 Nimbus beacon nodes requires that you add the following flag to charon run: charon run --feature-set-enable=json_requests
Prysm v5.0.3 🟡 Prysm validator needs a particular pull request merged and released for aggregation duties to succeed.
Lodestar v1.18.1 🟡

What's Changed

New Contributors

Full Changelog: v0.19.2...v1.0.0-rc5

Footnotes

  1. sync committee and aggregator duties are not yet supported in a DV setup by Lighthouse, all other duties work as expected. ↩

Don't miss a new charon release

NewReleases is sending notifications on new releases.