Skip to content

Releases: ObolNetwork/charon

v1.10.0-rc2

08 Apr 09:23
v1.10.0-rc2
2c0722a

Choose a tag to compare

v1.10.0-rc2 Pre-release
Pre-release

v1.10.0-rc2 - 2026-04-08

Obol Logo

This is Charon's v1.10.0 pre-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.9.3..v1.10.0-rc2

Feature

Compatibility Matrix

This release of Charon is backwards compatible with Charon >= v1.0., though only v1.7. and newer 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 v26.2.0 Lighthouse v8.1.0 Lodestar v1.40.0 Nimbus v26.1.0 Prysm v7.1.2 Vouch v1.12.0
Teku v26.4.0
Lighthouse v8.1.3
Lodestar v1.41.1
Nimbus v26.3.1
Prysm v7.1.3
Grandine v2.0.4

What's Changed

v1.9.3

01 Apr 20:49
v1.9.3
b50f15c

Choose a tag to compare

v1.9.3 - 2026-03-25

Obol Logo

This is highly recommended patch release of Charon v1.9.3. This patch fixes memory leak in the duties cache. Feedback from early testers is very 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.9.2..v1.9.3

Bugfix

Compatibility Matrix

This release of Charon is backwards compatible with Charon >= v1.0., though only v1.7. and newer 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 v26.2.0 Lighthouse v8.1.0 Lodestar v1.40.0 Nimbus v26.1.0 Prysm v7.1.2 Vouch v1.12.0
Teku v26.2.0 🟡
Lighthouse v8.1.0 🟡
Lodestar v1.40.0 🟡
Nimbus v26.1.0 🟡
Prysm v7.1.2 🟡
Grandine v2.0.1 🟡

What's Changed

v1.9.3-rc1

25 Mar 17:40
v1.9.3-rc1
22e2189

Choose a tag to compare

v1.9.3-rc1 Pre-release
Pre-release

v1.9.3-rc1 - 2026-03-25

Obol Logo

This a pre-release Charon v1.9.3-rc1. This patch fixes memory leak in the duties cache. Feedback from early testers is very 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.9.2..v1.9.3-rc1

Bugfix

  • Fix duteis cache memory leak #4413

Compatibility Matrix

This release of Charon is backwards compatible with Charon >= v1.0., though only v1.7. and newer 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 v26.2.0 Lighthouse v8.1.0 Lodestar v1.40.0 Nimbus v26.1.0 Prysm v7.1.2 Vouch v1.12.0
Teku v26.2.0 🟡
Lighthouse v8.1.0 🟡
Lodestar v1.40.0 🟡
Nimbus v26.1.0 🟡
Prysm v7.1.2 🟡
Grandine v2.0.1 🟡

What's Changed

Full Changelog: v1.9.2...v1.9.3-rc1

v1.9.2

12 Mar 14:45
v1.9.2
c207700

Choose a tag to compare

v1.9.2 - 2026-03-11

Obol Logo

This release Charon v1.9.2 is recommended for Operators sending logs to Obol. This patch improves the performance of nodes sending logs, by taking the log submission out of contention with the main runtime. 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.9.1..v1.9.2

Bugfix

Compatibility Matrix

This release of Charon is backwards compatible with Charon >= v1.0., though only v1.7. and newer 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 v26.2.0 Lighthouse v8.1.0 Lodestar v1.40.0 Nimbus v26.1.0 Prysm v7.1.2 Vouch v1.12.0
Teku v26.2.0 🟡
Lighthouse v8.1.0 🟡
Lodestar v1.40.0 🟡
Nimbus v26.1.0 🟡
Prysm v7.1.2 🟡
Grandine v2.0.1 🟡

What's Changed

v1.8.3

12 Mar 01:09
ac17e92

Choose a tag to compare

v1.8.3 - 2026-03-10

Obol Logo

This release Charon v1.8.3 is recommended for Operators sending logs to Obol. This patch improves the performance of nodes sending logs, by taking the log submission out of contention with the main runtime. An equivalent patch for 1.9.* versions will be released soon. 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.8.2..v1.8.3

Features

Compatibility Matrix

This release of Charon is backwards compatible with Charon >= v1.0., though only v1.7. and newer 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.12.0 Lighthouse v8.0.1 Lodestar v1.38.0 Nimbus v25.11.1 Prysm v7.1.0 Vouch 1.12.0
Teku v25.12.0 🟡
Lighthouse v8.0.1 🟡
Lodestar v1.38.0 🟡
Nimbus v25.11.1 🟡
Prysm v7.1.0 🟡
Grandine v2.0.1 🟡

What's Changed

Full Changelog: v1.8.2...v1.8.3

v1.9.1

06 Mar 15:05
v1.9.1
f8ef713

Choose a tag to compare

v1.9.1 - 2026-03-06

Obol Logo

This is non-urgent but recommended patch release of Charon v1.9.0. This patch removes an unnecessary miss-firing VC missing validators ready check. 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.9.0..v1.9.1

Bugfix

  • remove VC Missing validators ready check #4359

Compatibility Matrix

This release of Charon is backwards compatible with Charon >= v1.0., though only v1.7. and newer 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 v26.2.0 Lighthouse v8.1.0 Lodestar v1.40.0 Nimbus v26.1.0 Prysm v7.1.2 Vouch v1.12.0
Teku v26.2.0 🟡
Lighthouse v8.1.0 🟡
Lodestar v1.40.0 🟡
Nimbus v26.1.0 🟡
Prysm v7.1.2 🟡
Grandine v2.0.1 🟡

What's Changed

v1.9.0

24 Feb 15:52
v1.9.0
0f0391e

Choose a tag to compare

v1.9.0 - 2026-02-24

Obol Logo

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

For perfect backwards compatibility, Charon users on v1.8.2 and older should add the --feature-set-enable=fetch_only_commidx_0,proposal_timeout as a flag, or CHARON_FEATURE_SET_ENABLE=fetch_only_commidx_0,proposal_timeout as an environment variable to their setups before the nodes in the cluster begin to update to v1.9.0. Alternatively, update all of the nodes in the cluster to this version in close succession.

Read the rest of the release notes for more:

Full Changelog: v1.8.2..v1.9.0

Promote proposal_timeout feature flag to stable

We have extensively tested the proposal_timeout flag in the past months with numerous DV clusters on mainnet. From this version it is considered stable and moved to default-enabled. Clusters running Charon v1.9.0 will have the first QBFT round for proposal duties set at 1.5s (with second round timing out at 3.5s) in comparison to the current of 1.0s (with second round timing out at 3.0s). There is no urgent need to synchronise upgrades between cluster nodes, as the cluster will reach consensus on whichever timeout threshold of nodes agree on.

Note

This feature flag can be manually turned off by setting the --feature-set-disable=proposal_timeout flag.

Promote fetch_only_commidx_0 feature flag to stable

Post-electra Validator Clients were expected to request data from the beacon node (and hence, the DV) for a hardcoded committee index of 0. However, some clients continued requesting for their specific committee index. This forced Charon to also request the same index from the upstream beacon node(s). Now that this behaviour has been updated in all validator clients supported by Charon, we can promote this opt-in feature flag to stable, reducing the amount of requests we send to a beacon node by up to 64x.

In this issue can be found the list with the minimum required VC version.

Note

This feature flag can be manually turned off by setting --feature-set-disable=fetch_only_commidx_0 flag.

Scheduled Duties Cache

This version releases a caching mechanism for validator duties. To save on slow, burdensome requests to a BN, Charon caches them locally. Allowing it to reduce the amount of load on upstream beacon nodes.

Note

If there are any issues spotted with scheduled duty caching, it can be turned off by setting the --feature-set-enable=disable_duties_cache feature flag.

Replace operator command

This release adds the ability to directly replace an existing node operator in a cluster, rather than adding, and removing operators sequentially.

Warning

Charon's editability features are relatively new. Use them with caution, and practice actions on a testnet before mainnet. Flag any confusion or difficulties with User Experience to an Obol Core team member.

Feature

Bug

Refactor

  • Double the DKG timeouts #4272 (#4279)
  • Charon run hitting relays when its not going to be able to startup without a cluster lock #4242 (#4255)

Compatibility Matrix

This release of Charon is backwards compatible with Charon >= v1.0., though only v1.7. and newer 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 v26.2.0 Lighthouse v8.1.0 Lodestar v1.40.0 Nimbus v26.1.0 Prysm v7.1.2 Vouch v1.12.0
Teku v26.2.0 🟡
Lighthouse v8.1.0 🟡
Lodestar v1.40.0 🟡
Nimbus v26.1.0 🟡
Prysm v7.1.2 🟡
Grandine v2.0.1 🟡

What's Changed

v1.9.0-rc3

18 Feb 19:32
v1.9.0-rc3
97adf46

Choose a tag to compare

v1.9.0-rc3 Pre-release
Pre-release

v1.9.0-rc3 - 2026-02-18

This is a pre-release for Charon's upcoming v1.9.0. Feedback from early testers is very welcome and appreciated, please use github issues or discord if you have trouble with this release.

For perfect backwards compatibility, Charon users on v1.8.2 and older should add the --feature-set-enable=fetch_only_commidx_0,proposal_timeout as a flag, or CHARON_FEATURE_SET_ENABLE=fetch_only_commidx_0,proposal_timeout as an environment variable to their setups before the nodes in the cluster begin to update to v1.9.0. Alternatively, update all of the nodes in the cluster to this version in close succession.

Read the rest of the release notes for more:

Full Changelog: v1.8.2..v1.9.0-rc3

Promote proposal_timeout feature flag to stable

We have extensively tested the proposal_timeout flag in the past months with numerous DV clusters on mainnet. From this version it is considered stable and moved to default-enabled. Clusters running Charon v1.9.0 will have the first QBFT round for proposal duties set at 1.5s (with second round timing out at 3.5s) in comparison to the current of 1.0s (with second round timing out at 3.0s). There is no urgent need to synchronise upgrades between cluster nodes, as the cluster will reach consensus on whichever timeout threshold of nodes agree on.

Note

This feature flag can be manually turned off by setting the --feature-set-disable=proposal_timeout flag.

Promote fetch_only_commidx_0 feature flag to stable

Post-electra Validator Clients were expected to request data from the beacon node (and hence, the DV) for a hardcoded committee index of 0. However, some clients continued requesting for their specific committee index. This forced Charon to also request the same index from the upstream beacon node(s). Now that this behaviour has been updated in all validator clients supported by Charon, we can promote this opt-in feature flag to stable, reducing the amount of requests we send to a beacon node by up to 64x.

In this issue can be found the list with the minimum required VC version.

Note

This feature flag can be manually turned off by setting --feature-set-disable=fetch_only_commidx_0 flag.

Scheduled Duties Cache

This version releases a caching mechanism for validator duties. To save on slow, burdensome requests to a BN, Charon caches them locally. Allowing it to reduce the amount of load on upstream beacon nodes.

Note

If there are any issues spotted with scheduled duty caching, it can be turned off by setting the --feature-set-enable=disable_duties_cache feature flag.

Replace operator command

This release adds the ability to directly replace an existing node operator in a cluster, rather than adding, and removing operators sequentially.

Warning

Charon's editability features are relatively new. Use them with caution, and practice actions on a testnet before mainnet. Flag any confusion or difficulties with User Experience to an Obol Core team member.

Feature

Bug

Refactor

  • Double the DKG timeouts #4272 (#4279)
  • Charon run hitting relays when its not going to be able to startup without a cluster lock #4242 (#4255)

Compatibility Matrix

This release of Charon is backwards compatible with Charon >= v1.0., though only v1.7. and newer 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 v26.2.0 Lighthouse v8.1.0 Lodestar v1.40.0 Nimbus v26.1.0 Prysm v7.1.2 Vouch v1.12.0 Remarks
Teku v26.2.0
Lighthouse v8.1.0
Lodestar v1.40.0
Nimbus v26.1.0
Prysm v7.1.2
Grandine v2.0.1

What's Changed

v1.9.0-rc2

11 Feb 12:40
v1.9.0-rc2
83793cb

Choose a tag to compare

v1.9.0-rc2 Pre-release
Pre-release

v1.9.0-rc2 - 2026-02-10

Obol Logo

This is a pre-release for Charon's upcoming v1.9.0. Feedback from early testers is very welcome and appreciated, please use github issues or discord if you have trouble with this release.

For perfect backwards compatibility, Charon users on v1.8.2 and older should add the --feature-set-enable=fetch_only_commidx_0,proposal_timeout as a flag, or CHARON_FEATURE_SET_ENABLE=fetch_only_commidx_0,proposal_timeout as an environment variable to their setups before the nodes in the cluster begin to update to v1.9.0. Alternatively, update all of the nodes in the cluster to this version in close succession.

Read the rest of the release notes for more:

Full Changelog: v1.8.2..v1.9.0-rc2

Promote proposal_timeout feature flag to stable

We have extensively tested the proposal_timeout flag in the past months with numerous DV clusters on mainnet. From this version it is considered stable and moved to default-enabled. Clusters running Charon v1.9.0 will have the first QBFT round for proposal duties set at 1.5s (with second round timing out at 3.5s) in comparison to the current of 1.0s (with second round timing out at 3.0s). There is no urgent need to synchronise upgrades between cluster nodes, as the cluster will reach consensus on whichever timeout threshold of nodes agree on.

Note

This feature flag can be manually turned off by setting the --feature-set-disable=proposal_timeout flag.

Promote fetch_only_commidx_0 feature flag to stable

Post-electra Validator Clients were expected to request data from the beacon node (and hence, the DV) for a hardcoded committee index of 0. However, some clients continued requesting for their specific committee index. This forced Charon to also request the same index from the upstream beacon node(s). Now that this behaviour has been updated in all validator clients supported by Charon, we can promote this opt-in feature flag to stable, reducing the amount of requests we send to a beacon node by up to 64x.

In this issue can be found the list with the minimum required VC version.

Note

This feature flag can be manually turned off by setting --feature-set-disable=fetch_only_commidx_0 flag.

Scheduled Duties Cache

This version releases a caching mechanism for validator duties. To save on slow, burdensome requests to a BN, Charon caches them locally. Allowing it to reduce the amount of load on upstream beacon nodes.

Note

If there are any issues spotted with scheduled duty caching, it can be turned off by setting the --feature-set-enable=disable_duties_cache feature flag.

Replace operator command

This release adds the ability to directly replace an existing node operator in a cluster, rather than adding, and removing operators sequentially.

Warning

Charon's editability features are relatively new. Use them with caution, and practice actions on a testnet before mainnet. Flag any confusion or difficulties with User Experience to an Obol Core team member.

Feature

Bug

Refactor

  • Double the DKG timeouts #4272 (#4279)
  • Charon run hitting relays when its not going to be able to startup without a cluster lock #4242 (#4255)

Compatibility Matrix

This release of Charon is backwards compatible with Charon >= v1.0., though only v1.7. and newer 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 v26.2.0 Lighthouse v8.1.0 Lodestar v1.40.0 Nimbus v26.1.0 Prysm v7.1.2 Vouch v1.12.0 Remarks
Teku v26.2.0
Lighthouse v8.1.0
Lodestar v1.40.0
Nimbus v26.1.0
Prysm v7.1.2
Grandine v2.0.1

What's Changed

v1.8.2

09 Feb 17:11
v1.8.2
2eec107

Choose a tag to compare

v1.8.2 - 2026-02-09

Obol Logo

This is non-urgent but recommended patch release of Charon v1.8.1. This patch removes an unnecessary dependency on MEV-registration for proposals in slot 0 of an epoch, to improve proposal performance for large clusters using certain relays. 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.8.1..v1.8.2

Features

  • Asynchronous builder registration #4271

Compatibility Matrix

This release of Charon is backwards compatible with Charon >= v1.0., though only v1.7. and newer 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.12.0 Lighthouse v8.0.1 Lodestar v1.38.0 Nimbus v25.11.1 Prysm v7.1.0 Vouch 1.12.0
Teku v25.12.0 🟡
Lighthouse v8.0.1 🟡
Lodestar v1.38.0 🟡
Nimbus v25.11.1 🟡
Prysm v7.1.0 🟡
Grandine v2.0.1 🟡

What's Changed