Skip to content

Releases: ObolNetwork/charon

v1.7.0-rc2

29 Sep 16:56
459bc20

Choose a tag to compare

v1.7.0-rc2 Pre-release
Pre-release

v1.7.0-rc2 - 2025-09-29

Obol Logo

This is Charon's first Fulu-ready pre-release version. Feedback is welcome and appreciated, please use github issues or discord if you have trouble with this release.

Apart from Fulu readiness, there are two major features in this release, both under a feature flag:

Attestation source and target vote consensus. If feature flag chain_split_halt is enabled, Charon nodes will verify if the target and source votes (FFG) of the attestation they have fetched matches the one proposed from the leader. If not, Charon will not sign the attestation. If no consensus is reached between the nodes, a new leader is chosen. This is a security feature to ensure that in case of a fork in one of the beacon nodes used by the cluster, the rest do not blindly accept. However, head votes (LMD GHOST) are not checked in order not to block attestation signing when beacon node responds slower or receives block later.

Fetch only attestation data with committee index 0. In Electra the spec for fetching attestation data was changed, hardcoding the committee_index in the request to 0. However, most validator clients continued asking for the specific committee index, while the beacon nodes disregarded this field and returned the data. On Charon we were forced to do both in order to accommodate both versions. Now most VCs updated their codebase, in this issue we link the version at which the VC implemented the code that allows this feature flag to be turned on. If you enable this feature flag you will reduce the amount of requests Charon sends to the beacon node for attestation data. For big clusters that might be as high as 63 requests less per slot. In big clusters with slower beacon nodes turning on this feature flag improve attestation success rate as well.

Read the rest of the release notes for more:

Full Changelog: v1.6.1..v1.7.0-rc2

Feature

  • Attestation source and target vote consensus - chain split halt #3876 (#3946)
  • Fetcher fetch only attestation data with committee index 0 #3980 (#3989)
  • Track SSE events block_gossip and block #3877 (#3938)
  • Add publishing new cluster definition to Obol API with only --operator-enrs #3993
  • Allow beacon node basic auth in URL #3926

Misc

  • Turned on feature flag metric #3979 (#3994)
  • Add self identification to logs #3919 (#3939)
  • Allow pushing metrics to OTLP insecurely #3983

Compatibility Matrix

This release of Charon is backwards compatible with Charon v1.0.*, v1.1.*, v1.2.0, v1.3.*, v1.4.*, v1.5.*, v1.6.* Though only v1.3.* and newer are Pectra-ready and none of the previous are Fulu-ready.

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 v25.9.3 Lighthouse v8.0.0-rc.0 Lodestar v1.35.0-rc.0 Nimbus v25.9.1 Prysm v6.1.0 Vouch 1.12.0-beta.3
Teku v25.9.3 🟡
Lighthouse v8.0.0-rc.0 🟡
Lodestar v1.35.0-rc.0 🟡
Nimbus v25.9.1 🟡
Prysm v6.1.0 🟠 🟡
Grandine v2.0.0.rc0 🟡

What's Changed

v1.7.0-rc1

26 Sep 15:25
888c655

Choose a tag to compare

v1.7.0-rc1 Pre-release
Pre-release

v1.7.0-rc1 - 2025-09-26

Obol Logo

This is Charon's first Fulu-ready pre-release version. Feedback is welcome and appreciated, please use github issues or discord if you have trouble with this release.

Apart from Fulu readiness, there are two major features in this release, both under a feature flag:

Attestation source and target vote consensus. If feature flag chain_split_halt is enabled, Charon nodes will verify if the target and source votes (FFG) of the attestation they have fetched matches the one proposed from the leader. If not, Charon will not sign the attestation. If no consensus is reached between the nodes, a new leader is chosen. This is a security feature to ensure that in case of a fork in one of the beacon nodes used by the cluster, the rest do not blindly accept. However, head votes (LMD GHOST) are not checked in order not to block attestation signing when beacon node responds slower or receives block later.

Fetch only attestation data with committee index 0. In Electra the spec for fetching attestation data was changed, hardcoding the committee_index in the request to 0. However, most validator clients continued asking for the specific committee index, while the beacon nodes disregarded this field and returned the data. On Charon we were forced to do both in order to accommodate both versions. Now most VCs updated their codebase, in this issue we link the version at which the VC implemented the code that allows this feature flag to be turned on. If you enable this feature flag you will reduce the amount of requests Charon sends to the beacon node for attestation data. For big clusters that might be as high as 63 requests less per slot. In big clusters with slower beacon nodes turning on this feature flag improve attestation success rate as well.

Read the rest of the release notes for more:

Full Changelog: v1.6.1..v1.7.0-rc1

Feature

  • Attestation source and target vote consensus - chain split halt #3876 (#3946)
  • Fetcher fetch only attestation data with committee index 0 #3980 (#3989)
  • Track SSE events block_gossip and block #3877 (#3938)
  • Add publishing new cluster definition to Obol API with only --operator-enrs #3993
  • Allow beacon node basic auth in URL #3926

Misc

  • Turned on feature flag metric #3979 (#3994)
  • Add self identification to logs #3919 (#3939)
  • Allow pushing metrics to OTLP insecurely #3983

Compatibility Matrix

This release of Charon is backwards compatible with Charon v1.0.*, v1.1.*, v1.2.0, v1.3.*, v1.4.*, v1.5.*, v1.6.* Though only v1.3.* and newer are Pectra-ready and none of the previous are Fulu-ready.

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 v25.9.3 Lighthouse v8.0.0-rc.0 Lodestar v1.35.0-rc.0 Nimbus v25.9.1 Prysm v6.1.0 Vouch 1.12.0-beta.3
Teku v25.9.3 🟠 🟡
Lighthouse v8.0.0-rc.0 🟡
Lodestar v1.35.0-rc.0 🟡
Nimbus v25.9.1 🟡
Prysm v6.1.0 🟠 🟠 🟡
Grandine v2.0.0.rc0 🟠

What's Changed

v1.6.1

15 Sep 09:44
82e31db

Choose a tag to compare

v1.6.1 - 2025-09-15

Obol Logo

This is Charon's v1.6.1 release. Feedback is welcome and appreciated, please use github issues or discord if you have trouble with this release.

A dutydb bug fix, which impacted only big clusters with slow beacon nodes.

Read the rest of the release notes for more:

Full Changelog: v1.6.0..v1.6.1

Bug

  • Check only source and target for commidx 0 (#3974)

Compatibility Matrix

This release of Charon is backwards compatible with Charon v1.0.*, v1.1.*, v1.2.0, v1.3.*, v1.4.*, v1.5.*, v1.6.* Though only v1.3.* and newer are Pectra-ready.

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 v25.7.1 Lighthouse v7.1.0 Lodestar v1.33.0 Nimbus v25.7.1 Prysm v6.0.4 Vouch v1.10.3
Teku v25.7.1 🟡 🟡
Lighthouse v7.1.0 🟡 🟡
Lodestar v1.33.0 🟡 🟡
Nimbus v25.7.1 🟡 🟡
Prysm v6.0.4 🟡 🟡
Grandine v1.1.2 🟡 🟡

What's Changed

v1.6.0

27 Aug 13:07
5f953a6

Choose a tag to compare

v1.6.0 - 2025-08-27

Obol Logo

This is Charon's v1.6.0 release. Feedback is welcome and appreciated, please use github issues or discord if you have trouble with this release.

Read the rest of the release notes for more:

Full Changelog: v1.5.2..v1.6.0

Notable features

This release ships with opt-in support for the QUIC transport protocol. QUIC aims to improve performance in large, distant clusters. This may become a default feature in future versions once proven stable and well-incorporated across our stack.

To enable this feature, make the following additions:

  • Add https://4.relay.obol.dev/ to your obol relay list, e.g. CHARON_P2P_RELAYS:-https://0.relay.obol.tech,https://2.relay.obol.dev,https://1.relay.obol.tech,https://4.relay.obol.dev/
  • Add CHARON_FEATURESET_ENABLE=quic as an env variable
  • Add CHARON_P2P_QUIC_ADDRESS=0.0.0.0:3610 as an env variable
  • Allow UDP traffic on your port 3610. If you're using our docker-compose examples, your ports section should be like
    ports:
      - ${CHARON_PORT_P2P_TCP:-3610}:3610/tcp       # P2P TCP libp2p
      - ${CHARON_PORT_P2P_QUIC:-3610}:3610/udp       # P2P QUIC libp2p
    

This release also introduces new ways of modifying existing cluster which are still in alpha version and are not recommended for Mainnet usage:

  • addvalidator command which adds N validators to an existing cluster. This requires a new deposit for newly added validators.
  • node_merge.sh script which helps combining validator keys and configuration for single pair of nodes by merging two nodes' folders.
  • cluster_merge.sh script which helps expand an existing cluster with new validators by merging two existing clusters, given the same operators set and cluster configuration.

Feature

  • Launchpad link per network (#3886)
  • charon --split-existing-keys support multiple formats (#3872)
  • cluster-lock merge script (#3847)
  • Support deleting partial exits (#3838)
  • Add add-validators command (#3857)
  • Replace go-eth2-client with in-house solution (#3862)
  • Put QUIC behind a feature flag (#3814)
  • Add zipped flag to DKG (#3903)
  • Add hostname verification (#3901)

Bug

  • Invalid UUIDs are generated (#3887)
  • Memory leak under attestation_inclusion feature flag (#3867)
  • Increased duty timeout margin (#3800)
  • Set content type in alpha test (#3808)
  • Fixed vapi monitoring code (#3812)
  • Fix attestation committee index (#3820)
  • Remove fulu from fork schedule (#3822)
  • Add missing encoding types (#3853)
  • Fix flaky test (#3888)

Refactor

  • Added sse_head_delay buckets (#3795)
  • Changed reorg gauge to historgram (#3796)
  • Changed sse-head-delay buckets (#3816)
  • Replace HasPrefix+TrimPrefix with CutPrefix (#3824)
  • Use maps.Copy for cleaner map handling (#3856)
  • Improve fallback beacon node logic and metric (#3870)
  • Batch duplicate logs (#3835)
  • combine default input should align with create cluster default output. (#3815)

Compatibility Matrix

This release of Charon is backwards compatible with Charon v1.0.*, v1.1.*, v1.2.0, v1.3.*, v1.4.*, v1.5.* Though only v1.3.* and newer are Pectra-ready.

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 v25.7.1 Lighthouse v7.1.0 Lodestar v1.33.0 Nimbus v25.7.1 Prysm v6.0.4 Vouch v1.10.3
Teku v25.7.1 🟡 🟡
Lighthouse v7.1.0 🟡 🟡
Lodestar v1.33.0 🟡 🟡
Nimbus v25.7.1 🟡 🟡
Prysm v6.0.4 🟡 🟡
Grandine v1.1.2 🟡 🟡

What's Changed

v1.6.0-rc5

26 Aug 16:46
fe47c03

Choose a tag to compare

v1.6.0-rc5 Pre-release
Pre-release

v1.6.0-rc5 - 2025-08-26

Obol Logo

This is a release candidate for Charon's v1.6.0 release. Feedback is welcome and appreciated, please use github issues or discord if you have trouble with this release.

Read the rest of the release notes for more:

Full Changelog: v1.5.2..v1.6.0-rc5

Notable features

This release ships with opt-in support for the QUIC transport protocol. QUIC aims to improve performance in large, distant clusters. This may become a default feature in future versions once proven stable and well-incorporated across our stack.

To enable this feature, make the following additions:

  • Add https://4.relay.obol.dev/ to your obol relay list, e.g. CHARON_P2P_RELAYS:-https://0.relay.obol.tech,https://2.relay.obol.dev,https://1.relay.obol.tech,https://4.relay.obol.dev/
  • Add CHARON_FEATURESET_ENABLE=quic as an env variable
  • Add CHARON_P2P_QUIC_ADDRESS=0.0.0.0:3610 as an env variable
  • Allow UDP traffic on your port 3610. If you're using our docker-compose examples, your ports section should be like
    ports:
      - ${CHARON_PORT_P2P_TCP:-3610}:3610/tcp       # P2P TCP libp2p
      - ${CHARON_PORT_P2P_QUIC:-3610}:3610/udp       # P2P QUIC libp2p
    

This release also introduces new ways of modifying existing cluster which are still in alpha version and are not recommended for Mainnet usage:

  • addvalidator command which adds N validators to an existing cluster. This requires a new deposit for newly added validators.
  • node_merge.sh script which helps combining validator keys and configuration for single pair of nodes by merging two nodes' folders.
  • cluster_merge.sh script which helps expand an existing cluster with new validators by merging two existing clusters, given the same operators set and cluster configuration.

Feature

  • Launchpad link per network (#3886)
  • charon --split-existing-keys support multiple formats (#3872)
  • cluster-lock merge script (#3847)
  • Support deleting partial exits (#3838)
  • Add add-validators command (#3857)
  • Replace go-eth2-client with in-house solution (#3862)
  • Put QUIC behind a feature flag (#3814)
  • Add zipped flag to DKG (#3903)
  • Add hostname verification (#3901)

Bug

  • Invalid UUIDs are generated (#3887)
  • Memory leak under attestation_inclusion feature flag (#3867)
  • Increased duty timeout margin (#3800)
  • Set content type in alpha test (#3808)
  • Fixed vapi monitoring code (#3812)
  • Fix attestation committee index (#3820)
  • Remove fulu from fork schedule (#3822)
  • Add missing encoding types (#3853)
  • Fix flaky test (#3888)

Refactor

  • Added sse_head_delay buckets (#3795)
  • Changed reorg gauge to historgram (#3796)
  • Changed sse-head-delay buckets (#3816)
  • Replace HasPrefix+TrimPrefix with CutPrefix (#3824)
  • Use maps.Copy for cleaner map handling (#3856)
  • Improve fallback beacon node logic and metric (#3870)
  • Batch duplicate logs (#3835)
  • combine default input should align with create cluster default output. (#3815)

Compatibility Matrix

This release of Charon is backwards compatible with Charon v1.0.*, v1.1.*, v1.2.0, v1.3.*, v1.4.*, v1.5.* Though only v1.3.* and newer are Pectra-ready.

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 v25.7.1 Lighthouse v7.1.0 Lodestar v1.33.0 Nimbus v25.7.1 Prysm v6.0.4 Vouch v1.10.3
Teku v25.7.1 🟡 🟡
Lighthouse v7.1.0 🟡 🟡
Lodestar v1.33.0 🟡 🟡
Nimbus v25.7.1 🟡 🟡
Prysm v6.0.4 🟡 🟡
Grandine v1.1.2 🟡 🟡

What's Changed

v1.6.0-rc4

26 Aug 08:49
32ce96b

Choose a tag to compare

v1.6.0-rc4 Pre-release
Pre-release

v1.6.0-rc4 - 2025-08-26

Obol Logo

This is a release candidate for Charon's v1.6.0 release. Feedback is welcome and appreciated, please use github issues or discord if you have trouble with this release.

Read the rest of the release notes for more:

Full Changelog: v1.5.2..v1.6.0-rc4

Notable features

This release ships with opt-in support for the QUIC transport protocol. QUIC aims to improve performance in large, distant clusters. This may become a default feature in future versions once proven stable and well-incorporated across our stack.

To enable this feature, make the following additions:

  • Add https://4.relay.obol.dev/ to your obol relay list, e.g. CHARON_P2P_RELAYS:-https://0.relay.obol.tech,https://2.relay.obol.dev,https://1.relay.obol.tech,https://4.relay.obol.dev/
  • Add CHARON_FEATURESET_ENABLE=quic as an env variable
  • Add CHARON_P2P_QUIC_ADDRESS=0.0.0.0:3610 as an env variable
  • Allow UDP traffic on your port 3610. If you're using our docker-compose examples, your ports section should be like
    ports:
      - ${CHARON_PORT_P2P_TCP:-3610}:3610/tcp       # P2P TCP libp2p
      - ${CHARON_PORT_P2P_QUIC:-3610}:3610/udp       # P2P QUIC libp2p
    

This release also introduces new ways of modifying existing cluster which are still in alpha version and are not recommended for Mainnet usage:

  • addvalidator command which adds N validators to an existing cluster. This requires a new deposit for newly added validators.
  • node_merge.sh script which helps combining validator keys and configuration for single pair of nodes by merging two nodes' folders.
  • cluster_merge.sh script which helps expand an existing cluster with new validators by merging two existing clusters, given the same operators set and cluster configuration.

Feature

  • Launchpad link per network (#3886)
  • charon --split-existing-keys support multiple formats (#3872)
  • cluster-lock merge script (#3847)
  • Support deleting partial exits (#3838)
  • Add add-validators command (#3857)
  • Replace go-eth2-client with in-house solution (#3862)
  • Put QUIC behind a feature flag (#3814)
  • Add zipped flag to DKG (#3903)
  • Add hostname verification (#3901)

Bug

  • Invalid UUIDs are generated (#3887)
  • Memory leak under attestation_inclusion feature flag (#3867)
  • Increased duty timeout margin (#3800)
  • Set content type in alpha test (#3808)
  • Fixed vapi monitoring code (#3812)
  • Fix attestation committee index (#3820)
  • Remove fulu from fork schedule (#3822)
  • Add missing encoding types (#3853)
  • Fix flaky test (#3888)

Refactor

  • Added sse_head_delay buckets (#3795)
  • Changed reorg gauge to historgram (#3796)
  • Changed sse-head-delay buckets (#3816)
  • Replace HasPrefix+TrimPrefix with CutPrefix (#3824)
  • Use maps.Copy for cleaner map handling (#3856)
  • Improve fallback beacon node logic and metric (#3870)
  • Batch duplicate logs (#3835)
  • combine default input should align with create cluster default output. (#3815)

Compatibility Matrix

This release of Charon is backwards compatible with Charon v1.0.*, v1.1.*, v1.2.0, v1.3.*, v1.4.*, v1.5.* Though only v1.3.* and newer are Pectra-ready.

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 v25.7.1 Lighthouse v7.1.0 Lodestar v1.33.0 Nimbus v25.7.1 Prysm v6.0.4 Vouch v1.10.3
Teku v25.7.1 🟡 🟡
Lighthouse v7.1.0 🟡 🟡
Lodestar v1.33.0 🟡 🟡
Nimbus v25.7.1 🟡 🟡
Prysm v6.0.4 🟡 🟡
Grandine v1.1.2 🟡 🟡

What's Changed

v1.6.0-rc3

20 Aug 09:12
1624952

Choose a tag to compare

v1.6.0-rc3 Pre-release
Pre-release

v1.6.0-rc3 - 2025-08-20

Obol Logo

This is a release candidate for Charon's v1.6.0 release. Feedback is welcome and appreciated, please use github issues or discord if you have trouble with this release.

Read the rest of the release notes for more:

Full Changelog: v1.5.2..v1.6.0-rc3

Notable features

This release ships with opt-in support for the QUIC transport protocol. QUIC aims to improve performance in large, distant clusters. This may become a default feature in future versions once proven stable and well-incorporated across our stack.

To enable this feature, make the following additions:

  • Add https://4.relay.obol.dev/ to your obol relay list, e.g. CHARON_P2P_RELAYS:-https://0.relay.obol.tech,https://2.relay.obol.dev,https://1.relay.obol.tech,https://4.relay.obol.dev/
  • Add CHARON_FEATURESET_ENABLE=quic as an env variable
  • Add CHARON_P2P_QUIC_ADDRESS=0.0.0.0:3610 as an env variable
  • Allow UDP traffic on your port 3610. If you're using our docker-compose examples, your ports section should be like
    ports:
      - ${CHARON_PORT_P2P_TCP:-3610}:3610/tcp       # P2P TCP libp2p
      - ${CHARON_PORT_P2P_QUIC:-3610}:3610/udp       # P2P QUIC libp2p
    

This release also introduces new ways of modifying existing cluster which are still in alpha version and are not recommended for Mainnet usage:

  • addvalidator command which adds N validators to an existing cluster. This requires a new deposit for newly added validators.
  • node_merge.sh script which helps combining validator keys and configuration for single pair of nodes by merging two nodes' folders.
  • cluster_merge.sh script which helps expand an existing cluster with new validators by merging two existing clusters, given the same operators set and cluster configuration.

Feature

  • Launchpad link per network (#3886)
  • charon --split-existing-keys support multiple formats (#3872)
  • cluster-lock merge script (#3847)
  • Support deleting partial exits (#3838)
  • Add add-validators command (#3857)
  • Replace go-eth2-client with in-house solution (#3862)
  • Put QUIC behind a feature flag (#3814)
  • Add zipped flag to DKG (#3903)
  • Add hostname verification (#3901)

Bug

  • Invalid UUIDs are generated (#3887)
  • Memory leak under attestation_inclusion feature flag (#3867)
  • Increased duty timeout margin (#3800)
  • Set content type in alpha test (#3808)
  • Fixed vapi monitoring code (#3812)
  • Fix attestation committee index (#3820)
  • Remove fulu from fork schedule (#3822)
  • Add missing encoding types (#3853)
  • Fix flaky test (#3888)

Refactor

  • Added sse_head_delay buckets (#3795)
  • Changed reorg gauge to historgram (#3796)
  • Changed sse-head-delay buckets (#3816)
  • Replace HasPrefix+TrimPrefix with CutPrefix (#3824)
  • Use maps.Copy for cleaner map handling (#3856)
  • Improve fallback beacon node logic and metric (#3870)
  • Batch duplicate logs (#3835)
  • combine default input should align with create cluster default output. (#3815)

Compatibility Matrix

This release of Charon is backwards compatible with Charon v1.0.*, v1.1.*, v1.2.0, v1.3.*, v1.4.*, v1.5.* Though only v1.3.* and newer are Pectra-ready.

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 v25.7.1 Lighthouse v7.1.0 Lodestar v1.33.0 Nimbus v25.7.1 Prysm v6.0.4 Vouch v1.10.3
Teku v25.7.1 🟡 🟡
Lighthouse v7.1.0 🟡 🟡
Lodestar v1.33.0 🟡 🟡
Nimbus v25.7.1 🟡 🟡
Prysm v6.0.4 🟡 🟡
Grandine v1.1.2 🟡 🟡

What's Changed

v1.6.0-rc2

13 Aug 14:52
b3e689c

Choose a tag to compare

v1.6.0-rc2 Pre-release
Pre-release

v1.6.0-rc2 - 2025-08-13

Obol Logo

This is a release candidate for Charon's v1.6.0 release. Feedback is welcome and appreciated, please use github issues or discord if you have trouble with this release.

Read the rest of the release notes for more:

Full Changelog: v1.5.2..v1.6.0-rc2

Notable features

This release ships with opt-in support for the QUIC transport protocol. QUIC aims to improve performance in large, distant clusters. This may become a default feature in future versions once proven stable and well-incorporated across our stack.

To enable this feature, make the following additions:

  • Add https://4.relay.obol.dev/ to your obol relay list, e.g. CHARON_P2P_RELAYS:-https://0.relay.obol.tech,https://2.relay.obol.dev,https://1.relay.obol.tech,https://4.relay.obol.dev/
  • Add CHARON_FEATURESET_ENABLE=quic as an env variable
  • Add CHARON_P2P_QUIC_ADDRESS=0.0.0.0:3610 as an env variable
  • Allow UDP traffic on your port 3610. If you're using our docker-compose examples, your ports section should be like
    ports:
      - ${CHARON_PORT_P2P_TCP:-3610}:3610/tcp       # P2P TCP libp2p
      - ${CHARON_PORT_P2P_QUIC:-3610}:3610/udp       # P2P QUIC libp2p
    

This release also introduces new ways of modifying existing cluster which are still in alpha version and are not recommended for Mainnet usage:

  • addvalidator command which adds N validators to an existing cluster. This requires a new deposit for newly added validators.
  • node_merge.sh script which helps combining validator keys and configuration for single pair of nodes by merging two nodes' folders.
  • cluster_merge.sh script which helps expand an existing cluster with new validators by merging two existing clusters, given the same operators set and cluster configuration.

Feature

  • Launchpad link per network (#3886)
  • charon --split-existing-keys support multiple formats (#3872)
  • cluster-lock merge script (#3847)
  • Support deleting partial exits (#3838)
  • Add add-validators command (#3857)
  • Replace go-eth2-client with in-house solution (#3862)
  • Put QUIC behind a feature flag (#3814)
  • Add zipped flag to DKG (#3903)
  • Add hostname verification (#3901)

Bug

  • Invalid UUIDs are generated (#3887)
  • Memory leak under attestation_inclusion feature flag (#3867)
  • Increased duty timeout margin (#3800)
  • Set content type in alpha test (#3808)
  • Fixed vapi monitoring code (#3812)
  • Fix attestation committee index (#3820)
  • Remove fulu from fork schedule (#3822)
  • Add missing encoding types (#3853)
  • Fix flaky test (#3888)

Refactor

  • Added sse_head_delay buckets (#3795)
  • Changed reorg gauge to historgram (#3796)
  • Changed sse-head-delay buckets (#3816)
  • Replace HasPrefix+TrimPrefix with CutPrefix (#3824)
  • Use maps.Copy for cleaner map handling (#3856)
  • Improve fallback beacon node logic and metric (#3870)
  • Batch duplicate logs (#3835)
  • combine default input should align with create cluster default output. (#3815)

Compatibility Matrix

This release of Charon is backwards compatible with Charon v1.0.*, v1.1.*, v1.2.0, v1.3.*, v1.4.*, v1.5.* Though only v1.3.* and newer are Pectra-ready.

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 v25.7.1 Lighthouse v7.1.0 Lodestar v1.33.0 Nimbus v25.7.1 Prysm v6.0.4 Vouch v1.10.3
Teku v25.7.1 🟡 🟡
Lighthouse v7.1.0 🟡 🟡
Lodestar v1.33.0 🟡 🟡
Nimbus v25.7.1 🟡 🟡
Prysm v6.0.4 🟡 🟡
Grandine v1.1.2 🟡 🟡

What's Changed

v1.6.0-rc1

08 Aug 08:38
b221696

Choose a tag to compare

v1.6.0-rc1 Pre-release
Pre-release

v1.6.0-rc1 - 2025-08-07

Obol Logo

This is a release candidate for Charon's v1.6.0 release. Feedback is welcome and appreciated, please use github issues or discord if you have trouble with this release.

Read the rest of the release notes for more:

Full Changelog: v1.5.2..v1.6.0-rc1

Notable features

This release ships with opt-in support for the QUIC transport protocol. QUIC aims to improve performance in large, distant clusters. This may become a default feature in future versions once proven stable and well-incorporated across our stack.

To enable this feature, make the following additions:

  • Add https://4.relay.obol.dev/ to your obol relay list, e.g. CHARON_P2P_RELAYS:-https://0.relay.obol.tech,https://2.relay.obol.dev,https://1.relay.obol.tech,https://4.relay.obol.dev/
  • Add CHARON_FEATURESET_ENABLE=quic as an env variable
  • Add CHARON_P2P_QUIC_ADDRESS=0.0.0.0:3610 as an env variable
  • Allow UDP traffic on your port 3610. If you're using our docker-compose examples, your ports section should be like
    ports:
      - ${CHARON_PORT_P2P_TCP:-3610}:3610/tcp       # P2P TCP libp2p
      - ${CHARON_PORT_P2P_QUIC:-3610}:3610/udp       # P2P QUIC libp2p
    

Feature

  • Launchpad link per network (#3886)
  • charon --split-existing-keys support multiple formats (#3872)
  • cluster-lock merge script (#3847)
  • Support deleting partial exits (#3838)
  • Replace go-eth2-client with in-house solution (#3862)
  • Put QUIC behind a feature flag (#3814)

Bug

  • Invalid UUIDs are generated (#3887)
  • Memory leak under attestation_inclusion feature flag (#3867)
  • Increased duty timeout margin (#3800)
  • Set content type in alpha test (#3808)
  • Fixed vapi monitoring code (#3812)
  • Fix attestation committee index (#3820)
  • Remove fulu from fork schedule (#3822)
  • Add missing encoding types (#3853)
  • Fix flaky test (#3888)

Refactor

  • Added sse_head_delay buckets (#3795)
  • Changed reorg gauge to historgram (#3796)
  • Changed sse-head-delay buckets (#3816)
  • Replace HasPrefix+TrimPrefix with CutPrefix (#3824)
  • Use maps.Copy for cleaner map handling (#3856)
  • Improve fallback beacon node logic and metric (#3870)
  • Batch duplicate logs (#3835)
  • combine default input should align with create cluster default output. (#3815)

Compatibility Matrix

This release of Charon is backwards compatible with Charon v1.0.*, v1.1.*, v1.2.0, v1.3.*, v1.4.*, v1.5.* Though only v1.3.* and newer are Pectra-ready.

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 v25.7.1 Lighthouse v7.1.0 Lodestar v1.33.0 Nimbus v25.7.1 Prysm v6.0.4 Vouch v1.10.3
Teku v25.7.1 🟡 🟡
Lighthouse v7.1.0 🟡 🟡
Lodestar v1.33.0 🟡 🟡
Nimbus v25.7.1 🟡 🟡
Prysm v6.0.4 🟡 🟡
Grandine v1.1.2 🟡 🟡

What's Changed

v1.5.2

04 Aug 15:32
c3d7169

Choose a tag to compare

v1.5.2 - 2025-08-04

Obol Logo

This is Charon's v1.5.2 release. Feedback is welcome and appreciated, please use github issues or discord if you have trouble with this release.

A memory leak fix, that was only affecting users with enabled attestation_inclusion feature flag.

Read the rest of the release notes for more:

Full Changelog: v1.5.1..v1.5.2

Bug

  • Trim state committees (#3868)

Compatibility Matrix

This release of Charon is backwards compatible with Charon v1.0.*, v1.1.*, v1.2.0, v1.3.*, v1.4.*, v1.5.* Though only v1.3.* and newer are Pectra-ready.

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 duties;
  • 🟠: One or more penalised duties may fail occasionally;
  • 🔴: One or more penalised duties fail consistently;
  • ❗: Remark regarding certain VC, CL or specific combination. Hover to reveal.
Validator 👉 Consensus 👇 Teku v25.6.0 Lighthouse v7.0.1 Lodestar v1.31.0 Nimbus v25.6.0 Prysm v6.0.4 Vouch v1.10.3
Teku v25.6.0 🟡 🟡
Lighthouse v7.0.1 🟡 🟡
Lodestar v1.31.0 🟡 🟡
Nimbus v25.6.0 🟡 🟡
Prysm v6.0.4 🟡 🟡
Grandine v1.1.1 🟡 🟡

What's Changed