v1.2.0

v1.2.0 - 2024-12-09

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

• Fix flaky tests #3309, #3316, #3332
• Disable intrange linter #3282
• Fix linter #3307 (partially)

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

• add third relay in p2p-relays (#3227)
• build(deps): Bump github.com/attestantio/go-eth2-client from 0.21.9 to 0.21.10 (#3214)
• testutil/promrated: fixing promrated network overview stats (#3234)
• docs: launchpad link is broken (#3231)
• build(deps): Bump golang.org/x/sync from 0.7.0 to 0.8.0 (#3217)
• build(deps): Bump github.com/docker/docker from 27.1.0+incompatible to 27.1.1+incompatible (#3232)
• build(deps): Bump golang.org/x/time from 0.5.0 to 0.6.0 (#3216)
• build(deps): Bump golang.org/x/crypto from 0.25.0 to 0.26.0 (#3219)
• *: bump linter to v1.60.3 (#3247)
• build(deps): Bump sigp/lighthouse from v5.2.1 to v5.3.0 in /testutil/compose/static/lighthouse (#3223)
• build(deps): Bump chainsafe/lodestar from v1.20.2 to v1.21.0 in /testutil/compose/static/lodestar (#3225)
• cmd: refactor exits (#3248)
• build(deps): Bump github.com/pelletier/go-toml/v2 from 2.2.2 to 2.2.3 (#3254)
• build(deps): Bump github.com/showwin/speedtest-go from 1.7.8 to 1.7.9 (#3255)
• *: bump golang to 1.23.1 (#3261)
• build(deps): Bump github.com/herumi/bls-eth-go-binary from 1.35.0 to 1.36.1 (#3256)
• cmd: hardening threshold parameter checks (#3242)
• build(deps): Bump github.com/prometheus/client_golang from 1.19.1 to 1.20.3 (#3258)
• workflows: bump govulncheck to v1.1.3 (#3262)
• build(deps): Bump golang.org/x/crypto from 0.26.0 to 0.27.0 (#3265)
• build(deps): Bump go.opentelemetry.io/otel/trace from 1.28.0 to 1.29.0 (#3252)
• build(deps): Bump go.opentelemetry.io/otel/exporters/stdout/stdouttrace from 1.28.0 to 1.29.0 (#3263)
• build(deps): Bump github.com/ferranbt/fastssz from 0.1.3 to 0.1.4 (#3264)
• build(deps): Bump golang.org/x/tools from 0.23.0 to 0.25.0 (#3270)
• build(deps): Bump go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp from 0.53.0 to 0.54.0 (#3271)
• build(deps): Bump go.opentelemetry.io/otel from 1.29.0 to 1.30.0 (#3274)
• build(deps): Bump go.opentelemetry.io/otel/exporters/stdout/stdouttrace from 1.29.0 to 1.30.0 (#3275)
• *: add --all for exit sign command (#3272)
• docs: fix typos (#3236)
• [build(deps): Bump go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp from 0.54.0 to 0.55.0 (#3284)](https://github.co...

v1.2.0-rc3

v1.2.0-rc3 - 2024-12-05

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

• Fix flaky tests #3309, #3316, #3332
• Disable intrange linter #3282
• Fix linter #3307 (partially)

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

• add third relay in p2p-relays (#3227)
• build(deps): Bump github.com/attestantio/go-eth2-client from 0.21.9 to 0.21.10 (#3214)
• testutil/promrated: fixing promrated network overview stats (#3234)
• docs: launchpad link is broken (#3231)
• build(deps): Bump golang.org/x/sync from 0.7.0 to 0.8.0 (#3217)
• build(deps): Bump github.com/docker/docker from 27.1.0+incompatible to 27.1.1+incompatible (#3232)
• build(deps): Bump golang.org/x/time from 0.5.0 to 0.6.0 (#3216)
• build(deps): Bump golang.org/x/crypto from 0.25.0 to 0.26.0 (#3219)
• *: bump linter to v1.60.3 (#3247)
• build(deps): Bump sigp/lighthouse from v5.2.1 to v5.3.0 in /testutil/compose/static/lighthouse (#3223)
• build(deps): Bump chainsafe/lodestar from v1.20.2 to v1.21.0 in /testutil/compose/static/lodestar (#3225)
• cmd: refactor exits (#3248)
• build(deps): Bump github.com/pelletier/go-toml/v2 from 2.2.2 to 2.2.3 (#3254)
• build(deps): Bump github.com/showwin/speedtest-go from 1.7.8 to 1.7.9 (#3255)
• *: bump golang to 1.23.1 (#3261)
• build(deps): Bump github.com/herumi/bls-eth-go-binary from 1.35.0 to 1.36.1 (#3256)
• cmd: hardening threshold parameter checks (#3242)
• build(deps): Bump github.com/prometheus/client_golang from 1.19.1 to 1.20.3 (#3258)
• workflows: bump govulncheck to v1.1.3 (#3262)
• build(deps): Bump golang.org/x/crypto from 0.26.0 to 0.27.0 (#3265)
• build(deps): Bump go.opentelemetry.io/otel/trace from 1.28.0 to 1.29.0 (#3252)
• build(deps): Bump go.opentelemetry.io/otel/exporters/stdout/stdouttrace from 1.28.0 to 1.29.0 (#3263)
• build(deps): Bump github.com/ferranbt/fastssz from 0.1.3 to 0.1.4 (#3264)
• build(deps): Bump golang.org/x/tools from 0.23.0 to 0.25.0 (#3270)
• build(deps): Bump go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp from 0.53.0 to 0.54.0 (#3271)
• build(deps): Bump go.opentelemetry.io/otel from 1.29.0 to 1.30.0 (#3274)
• build(deps): Bump go.opentelemetry.io/otel/exporters/stdout/stdouttrace from 1.29.0 to 1.30.0 (#3275)
• *: add --all for exit sign command (#3272)
• docs: fix typos (#3236)
• [build(deps): Bump go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp from 0.54.0 to 0.55.0 (#3284)](https://githu...

v1.2.0-rc2

v1.2.0-rc2 - 2024-11-26

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

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

• Fix flaky tests #3309, #3316, #3332
• Disable intrange linter #3282
• Fix linter #3307 (partially)

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-rc2

What's Changed

• add third relay in p2p-relays (#3227)
• build(deps): Bump github.com/attestantio/go-eth2-client from 0.21.9 to 0.21.10 (#3214)
• testutil/promrated: fixing promrated network overview stats (#3234)
• docs: launchpad link is broken (#3231)
• build(deps): Bump golang.org/x/sync from 0.7.0 to 0.8.0 (#3217)
• build(deps): Bump github.com/docker/docker from 27.1.0+incompatible to 27.1.1+incompatible (#3232)
• build(deps): Bump golang.org/x/time from 0.5.0 to 0.6.0 (#3216)
• build(deps): Bump golang.org/x/crypto from 0.25.0 to 0.26.0 (#3219)
• *: bump linter to v1.60.3 (#3247)
• build(deps): Bump sigp/lighthouse from v5.2.1 to v5.3.0 in /testutil/compose/static/lighthouse (#3223)
• build(deps): Bump chainsafe/lodestar from v1.20.2 to v1.21.0 in /testutil/compose/static/lodestar (#3225)
• cmd: refactor exits (#3248)
• build(deps): Bump github.com/pelletier/go-toml/v2 from 2.2.2 to 2.2.3 (#3254)
• build(deps): Bump github.com/showwin/speedtest-go from 1.7.8 to 1.7.9 (#3255)
• *: bump golang to 1.23.1 (#3261)
• build(deps): Bump github.com/herumi/bls-eth-go-binary from 1.35.0 to 1.36.1 (#3256)
• cmd: hardening threshold parameter checks (#3242)
• build(deps): Bump github.com/prometheus/client_golang from 1.19.1 to 1.20.3 (#3258)
• workflows: bump govulncheck to v1.1.3 (#3262)
• build(deps): Bump golang.org/x/crypto from 0.26.0 to 0.27.0 (#3265)
• build(deps): Bump go.opentelemetry.io/otel/trace from 1.28.0 to 1.29.0 (#3252)
• build(deps): Bump go.opentelemetry.io/otel/exporters/stdout/stdouttrace from 1.28.0 to 1.29.0 (#3263)
• build(deps): Bump github.com/ferranbt/fastssz from 0.1.3 to 0.1.4 (#3264)
• build(deps): Bump golang.org/x/tools from 0.23.0 to 0.25.0 (#3270)
• build(deps): Bump go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp from 0.53.0 to 0.54.0 (#3271)
• build(deps): Bump go.opentelemetry.io/otel from 1.29.0 to 1.30.0 (#3274)
• build(deps): Bump go.opentelemetry.io/otel/exporters/stdout/stdouttrace from 1.29.0 to 1.30.0 (#3275)
• *: add --all for exit sign command (#3272)
• docs: fix typos (#3236)
• build(deps): Bump go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp from 0.54.0 to 0.55.0 (#3284)
• [build(deps): Bump github.com/prometheus/client_golang from 1.20.3 to 1.20.4 (#3289)...

v1.2.0-rc1

v1.2.0-rc1 - 2024-11-20

This is a non-urgent, feature release. This release introduces improved charon exit command - now it is possible to easily exit all validators from a cluster with a single command. It also greatly improves the UX, number of tests and overall stability of the charon test command, moving it out of alpha state. 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
• 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

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

• Fix flaky tests #3309, #3316, #3332
• Disable intrange linter #3282
• Fix linter #3307 (partially)

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
• 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 + 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
Lighthouse v5.3.0
Lodestar v1.23.0
Nimbus v24.10.0
Prysm v5.1.2

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

What's Changed

• add third relay in p2p-relays (#3227)
• build(deps): Bump github.com/attestantio/go-eth2-client from 0.21.9 to 0.21.10 (#3214)
• testutil/promrated: fixing promrated network overview stats (#3234)
• docs: launchpad link is broken (#3231)
• build(deps): Bump golang.org/x/sync from 0.7.0 to 0.8.0 (#3217)
• build(deps): Bump github.com/docker/docker from 27.1.0+incompatible to 27.1.1+incompatible (#3232)
• build(deps): Bump golang.org/x/time from 0.5.0 to 0.6.0 (#3216)
• build(deps): Bump golang.org/x/crypto from 0.25.0 to 0.26.0 (#3219)
• *: bump linter to v1.60.3 (#3247)
• build(deps): Bump sigp/lighthouse from v5.2.1 to v5.3.0 in /testutil/compose/static/lighthouse (#3223)
• build(deps): Bump chainsafe/lodestar from v1.20.2 to v1.21.0 in /testutil/compose/static/lodestar (#3225)
• cmd: refactor exits (#3248)
• build(deps): Bump github.com/pelletier/go-toml/v2 from 2.2.2 to 2.2.3 (#3254)
• build(deps): Bump github.com/showwin/speedtest-go from 1.7.8 to 1.7.9 (#3255)
• *: bump golang to 1.23.1 (#3261)
• build(deps): Bump github.com/herumi/bls-eth-go-binary from 1.35.0 to 1.36.1 (#3256)
• cmd: hardening threshold parameter checks (#3242)
• build(deps): Bump github.com/prometheus/client_golang from 1.19.1 to 1.20.3 (#3258)
• workflows: bump govulncheck to v1.1.3 (#3262)
• build(deps): Bump golang.org/x/crypto from 0.26.0 to 0.27.0 (#3265)
• build(deps): Bump go.opentelemetry.io/otel/trace from 1.28.0 to 1.29.0 (#3252)
• build(deps): Bump go.opentelemetry.io/otel/exporters/stdout/stdouttrace from 1.28.0 to 1.29.0 (#3263)
• build(deps): Bump github.com/ferranbt/fastssz from 0.1.3 to 0.1.4 (#3264)
• build(deps): Bump golang.org/x/tools from 0.23.0 to 0.25.0 (#3270)
• build(deps): Bump go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp from 0.53.0 to 0.54.0 (#3271)
• build(deps): Bump go.opentelemetry.io/otel from 1.29.0 to 1.30.0 (#3274)
• build(deps): Bump go.opentelemetry.io/otel/exporters/stdout/stdouttrace from 1.29.0 to 1.30.0 (#3275)
• *: add --all for exit sign command (#3272)
• docs: fix typos (#3236)
• build(deps): Bump go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp from 0.54.0 to 0.55.0 (#3284)
• build(deps): Bump github.com/prometheus/client_golang from 1.20.3 to 1.20.4 (#3289)
• *: disable intrange linter (#3282)
• cmd: broadcast all exits (#3288)
• cmd: fetch all exits (#3291)
• build(deps): Bump chainsafe/lodestar from v1.21.0 to v1.22.0 in /testutil/compose/static/lodestar (#3293)
• build(deps): Bump attestant/vouch from 1.8.2 to 1.9.0 in /testutil/compose/static/vouch (#3294)
• [dkg: fixed TestSyncFlow...

v1.1.2

v1.1.2 - 2024-10-28

This is a non-urgent, patch release, which introduces a fix for DKG key creation issues.

Due to an upstream dependency issue, DKG running on AVX-enabled CPUs might fail due to misgenerated private keys.

Details the bug can be found here.

Full Changelog: v1.1.1...v1.1.2

Bugfixes

• *: update bls-eth-go-binary #3349

Compatibility Matrix

This release of Charon is backwards compatible with Charon v1.0.0 - v1.1.1. DKGs need to be completed with clients on the same minor release.

Due to the above mentioned issue, it is recommended to run DKGs with Charon v1.1.2 onwards.

The below matrix details a combination of beacon node + 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

Consensus 👇 Validator 👉	Teku v24.8.0	Lighthouse v5.3.01	Lodestar v1.20.2	Nimbus v24.7.0	Prysm 5.1.0	Remarks
Teku v24.8.0	🟡	🟡	✅	✅	🟠	Teku bn needs the --validators-graffiti-client-append-format=DISABLED flag in order to produce blocks properly. Teku vc are 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 vc are only failing aggregation duties, which are not directly penalised but impact network density at high scale.
Nimbus v24.7.0	🟡	🟡	✅	✅	✅	Nimbus beacon nodes requires that you add the following flag to charon run: charon run --feature-set-enable=json_requests
Prysm v5.1.0	🟡	🟡	✅	✅	✅
Lodestar v1.20.2	🟡	🟡	✅	✅	🔴

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

v1.1.2-rc1

v1.1.2-rc1 - 2024-10-23

This is a non-urgent, patch release, which introduces a fix for DKG key creation issues.

Due to an upstream dependency issue, DKG running on AVX-enabled CPUs might fail due to misgenerated private keys.

Details the bug can be found here.

Full Changelog: v1.1.1...v1.1.2-rc1

Bugfixes

• *: update bls-eth-go-binary #3349

Compatibility Matrix

This release of Charon is backwards compatible with Charon v1.0.0 - v1.1.1. DKGs need to be completed with clients on the same minor release.

Due to the above mentioned issue, it is recommended to run DKGs with Charon v1.1.2 onwards.

The below matrix details a combination of beacon node + 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

Consensus 👇 Validator 👉	Teku v24.8.0	Lighthouse v5.3.01	Lodestar v1.20.2	Nimbus v24.7.0	Prysm 5.1.0	Remarks
Teku v24.8.0	🟡	🟡	✅	✅	🟠	Teku bn needs the --validators-graffiti-client-append-format=DISABLED flag in order to produce blocks properly. Teku vc are 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 vc are only failing aggregation duties, which are not directly penalised but impact network density at high scale.
Nimbus v24.7.0	🟡	🟡	✅	✅	✅	Nimbus beacon nodes requires that you add the following flag to charon run: charon run --feature-set-enable=json_requests
Prysm v5.1.0	🟡	🟡	✅	✅	✅
Lodestar v1.20.2	🟡	🟡	✅	✅	🔴

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

v1.1.1

v1.1.1 - 2024-09-26

This is a non-urgent, patch release, which introduces a fix for Gnosis/Chiado chains, as well as a few minor fixes for the CI pipeline.

Full Changelog: v1.1.0...v1.1.1

Features

• core/validatorapi: workaround for Gnosis proposals
• *: enable gnosis hotfix automatically

Bugfixes

• *: fix flaky testpeers test #3267
• cmd: increase testpeers tests timeouts #3268
• cmd: fix test peers out of range #3280
• testutil: update docker-compose command to docker compose

Compatibility Matrix

This release of Charon is backwards compatible with Charon v1.0.0 - v1.1.0. DKGs need to be completed with clients on the same minor release.

The below matrix details a combination of beacon node + 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

Consensus 👇 Validator 👉	Teku v24.8.0	Lighthouse v5.3.01	Lodestar v1.20.2	Nimbus v24.7.0	Prysm 5.1.0	Remarks
Teku v24.8.0	🟡	🟡	✅	✅	🟠	Teku bn needs the --validators-graffiti-client-append-format=DISABLED flag in order to produce blocks properly. Teku vc are 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 vc are only failing aggregation duties, which are not directly penalised but impact network density at high scale.
Nimbus v24.7.0	🟡	🟡	✅	✅	✅	Nimbus beacon nodes requires that you add the following flag to charon run: charon run --feature-set-enable=json_requests
Prysm v5.1.0	🟡	🟡	✅	✅	✅
Lodestar v1.20.2	🟡	🟡	✅	✅	🔴

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

v1.1.1-rc1

v1.1.1-rc1 - 2024-09-17

This is a non-urgent, patch release, which introduces a fix for Gnosis/Chiado chains, as well as a few minor fixes for the CI pipeline.

Full Changelog: v1.1.0...v1.1.1-rc1

Features

• core/validatorapi: workaround for Gnosis proposals
• *: enable gnosis hotfix automatically

Bugfixes

• *: fix flaky testpeers test #3267
• cmd: increase testpeers tests timeouts #3268
• cmd: fix test peers out of range #3280
• testutil: update docker-compose command to docker compose

Compatibility Matrix

This release of Charon is backwards compatible with Charon v1.0.0 - v1.1.0. DKGs need to be completed with clients on the same minor release.

The below matrix details a combination of beacon node + 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

Consensus 👇 Validator 👉	Teku v24.8.0	Lighthouse v5.3.01	Lodestar v1.20.2	Nimbus v24.7.0	Prysm 5.1.0	Remarks
Teku v24.8.0	🟡	🟡	✅	✅	🟠	Teku bn needs the --validators-graffiti-client-append-format=DISABLED flag in order to produce blocks properly. Teku vc are 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 vc are only failing aggregation duties, which are not directly penalised but impact network density at high scale.
Nimbus v24.7.0	🟡	🟡	✅	✅	✅	Nimbus beacon nodes requires that you add the following flag to charon run: charon run --feature-set-enable=json_requests
Prysm v5.1.0	🟡	🟡	✅	✅	✅
Lodestar v1.20.2	🟡	🟡	✅	✅	🔴

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

v1.1.0

v1.1.0 - 2024-08-26

This is a non-urgent, feature release. This release introduces improved monitoring capabilities of validator clients and process configuration, along with a test framework, developed to understand the health of your node, its consensus client, its peers, and its MEV relays, before the activation of a validator. More details can be found on our docs site, feedback is welcome and appreciated.

This release also introduces overridable timeouts for beacon nodes, if needed for extremely large clusters.

Feature

• Charon test command
  • Test peers - add direct connection test, ping relays (#3073, #3177)
  • Test validator client (#3085)
  • Test MEV relay (#3176)
  • Test performance (#3197, #3203)
• Detect validator services (#3169)
• Add --publish-timeout flag for charon exit command (#3098, #3127)
• Enforce JSON for Nimbus BN to properly handle SubmitProposal (#3110)
• Add Prometheus gauges for requests made by VC (#3112)
• Replace --beacon-node-url flag for exits with --beacon-node-endpoints to allow multiple beacon nodes (#3106)
• Allow exiting with validator index (#3106, #3146)
• Cache deeper on /validators endpoint to BN (#3114, #3123)
• Add --timeout flag for charon dkg command (#3130)
• Add custom beacon node timeout flags to charon run command --beacon-node-timeout and --beacon-node-submit-timeout (#3164)

Bugfix:

• Add --fetched-exit-path to the existing flags for charon exit command (#3099)
• Initialise fork version for lazy interface, fixing VC exits (#3131)
• Blinded and unblinded blocks casting (#3144, #3149)

Test:

• Charon test command unit tests (#3082, #3079)
• Fix compose test lighthouse image (#3111)

Misc:

• Bump version.go (#3078)
• Bump go versions (#3092, #3118, #3163)
• Update license (#3100, #3140, #3151)
• Composite CI build step for setting up go (#3119)
• Log warn about not using https only if protocol is http (#3124)
• Add Capella Fork Hash to networks struct (#3138)
• Recover on failed beacon node duty submission (#3150)
• Deprecate VersionedSignedBlindedProposal (#3155)
• Explicitly return 404 to v2 produce block endpoints (#3167)
• Fix typos in docs (#3165)

Compatibility Matrix

This release of Charon is backwards compatible with Charon v1.0.0 and v1.0.1.

The below matrix details a combination of beacon node + 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

Consensus 👇 Validator 👉	Teku v24.8.0	Lighthouse v5.3.01	Lodestar v1.20.2	Nimbus v24.7.0	Prysm PR	Remarks
Teku v24.8.0	🟡	🟡	✅	✅	🟠	Teku bn needs the --validators-graffiti-client-append-format=DISABLED flag in order to produce blocks properly. Teku vc are 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 vc are only failing aggregation duties, which are not directly penalised but impact network density at high scale.
Nimbus v24.7.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.20.2	🟡	🟡	✅	✅	🔴

Full Changelog: v1.0.1..v1.1.0

What's Changed

• app/peerinfo: version v1.1-dev (#3078)

• cmd: increase timeout of timeout test (#3079)

• *: bumped go-eth2-client to 0.21.4 (#3084)

• cmd: remove nil context check on test command (#3086)

• cmd: add available tests per test category in help (#3087)

• *: bump go to version 1.22 (#3092)

• app/obolapi: specify HTTP requests timeout (#3098)

• cmd: specify exit fetch path (#3099)

• *: update license for the next release candidate (#3100)

• app/eth2wrap: deep validator cache (#3114)

• *: bump go version to 1.22.4 (#3118)

• workflows: composite GitHub actions (#3119)

• core/validatorapi: return requested validators (#3123)

• *: not https warning to show only on http (#3124)

• cmd: bind publish timeout on exit (#3127)

• dkg: add customizable timeout (#3130)

• eth2wrap: initialize fork version on lazy (#3131)

• cmd: new thresholds for test command (#3132)

• cmd: add separate consts for testvalidator (#3133)

• *: capella fork to networks (#3138)

• *: update license (#3140)

• core/validatorapi: convert blinded to full proposal (#3144)

• core/tracker: track blinded proposals (#3149)

• core/tracker: harden inclusion proposal checks (#3150)

• *: update license (#3151)

• core: deprecate VersionedSignedBlindedProposal (#3155)

• cmd: beacon node API timeouts (#3164)

• docs: fix typos (#3165)

• *: update project status (#3166)

• *: bumped go-eth2-client to 0.21.7 (#3168)

• app/stacksnipe: detect validator services (#3169)

• cmd: charon test peers ping charon relays (#3177)

• docs: fix spelling issues (#3180)

• cmd: add load test for beacon node (#3182)

• *: pin lighthouse version in compose tests (#3188)

• app: fix for loop linting (#3194)

• cmd: performance test command (#3197)

• *: flag refactors (#3198)

• app/version: v1.1 from dev to rc (#3211)

• cmd: add file to homedir for fio in main-v1.1 (#3213)

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

v1.0.1

v1.0.1 - 2024-07-15

This release updates go-eth2-client in order to support Lodestar Beacon Node v1.20, which now defaults to SSZ encoding.

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.6.1	Lighthouse v5.2.11	Lodestar v1.20.0	Nimbus v24.5.1	Prysm PR	Remarks
Teku v24.6.1	✅	🟡	✅	✅	✅	Teku bn needs the --validators-graffiti-client-append-format=DISABLED flag in order to produce blocks properly.
Lighthouse v5.2.1	✅	🟡	✅	✅	🟠	Lighthouse vc are only failing aggregation duties, which are not directly penalised but impact network density at high scale.
Nimbus v24.5.1	🔴	🟡	✅	✅	✅	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.20.0	✅	🟡	✅	✅	✅

Full Changelog: v1.0.0..v1.0.1

What's Changed

• *: update go-eth2-client to v0.21.7 (#3173)

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