Skip to content

v1.2.0

Latest
Latest
Compare
Choose a tag to compare
@github-actions github-actions released this 09 Dec 15:01
· 123 commits to main since this release
v1.2.0
d60eb93
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

v1.2.0 - 2024-12-09

Obol Logo

This is a non-urgent, feature pre-release. This release introduces improved charon exit command - now it is possible to sign exits for all validators in a cluster with a single command. It also greatly improves the UX, number of tests and overall stability of the charon alpha test commands. Feedback is welcome and appreciated.

Feature

Charon test command

  • Add cluster lock and definition files to test peers #3368
  • Beacon node simulation #3361
  • General UX #3370, #3390
  • Create real blocks with MEV test #3378
  • Version check on beacon tests #3379
  • Rename test performance to test infra #3380
  • Output file improvements #3384
  • Custom number of validators for beacon node simulation #3385
  • Change data-dir flag to private-key-file flag for test peers #3393

Charon exits

  • Initial refactor #3248
  • Add --all flag #3272
  • Broadcast all exits #3288
  • Fetch all exits #3291
  • Enable exit all #3296
  • Add custom testnet flags (to enable kurtosis testing) #3317
  • Improve logging and error handling #3347
  • Increase default Obol API timeout #3353

Test

Misc

  • Log leader index #3334
  • Add third Charon relay #3227
  • Fix promrated network overview stats #3234
  • Harden threshold parameter checks #3242, #3297
  • Dependabot to bump only patch versions for our BLS library #3352
  • Optimize Dockerfile #3281, #3389
  • Create automate PR for release #3310
  • Use minor versions in pipelines #3321
  • Fix trigger-dispatch for release #3351, #3381
  • Launchpad link broken #3231
  • Docs typos #3236, #3367, #3369

Compatibility Matrix

This release of Charon is backwards compatible with Charon v1.0, v1.1.

The below matrix details a combination of beacon node (consensus layer) + validator clients and their corresponding versions the DV Labs 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
Validator 👉 Consensus 👇 Teku v24.10.3 Lighthouse v5.3.0 Lodestar v1.23.0 Nimbus v24.10.0 Prysm v5.1.2 Remarks
Teku v24.10.3 ✅ 🟡 ✅ ✅ 🟠 Teku beacon node needs the --validators-graffiti-client-append-format=DISABLED flag in order to produce blocks properly. Teku validator client is only failing aggregation duties 50% of the time, which are not directly penalised but impact network density at high scale.
Lighthouse v5.3.0 ✅ 🟡 ✅ ✅ ✅ Lighthouse validator client is only failing aggregation duties, which are not directly penalised but impact network density at high scale.
Lodestar v1.23.0 ✅ 🟡 ✅ ✅ 🟠
Nimbus v24.10.0 ✅ 🟡 ✅ ✅ 🟠
Prysm v5.1.2 ✅ 🟡 ✅ ✅ ✅ Prysm validator client is failing aggregation duties 50% of the time, which are not directly penalised but impact network density at high scale. In some combinations rare failures of attestation and proposal duties were observed (0-2% per epoch).

Full Changelog: v1.1.2..v1.2.0-rc3

What's Changed

Assets 3
Loading