Skip to content

chore(deps): update obolnetwork/charon docker tag to v1.9.1#268

Merged
OisinKyne merged 1 commit intomainfrom
renovate/obolnetwork-charon-1.x
Mar 10, 2026
Merged

chore(deps): update obolnetwork/charon docker tag to v1.9.1#268
OisinKyne merged 1 commit intomainfrom
renovate/obolnetwork-charon-1.x

Conversation

@renovate
Copy link

@renovate renovate bot commented Feb 24, 2026

This PR contains the following updates:

Package Update Change
obolnetwork/charon minor v1.8.2v1.9.1

Release Notes

obolnetwork/charon (obolnetwork/charon)

v1.9.1

Compare Source

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

Compare Source

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

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


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/obolnetwork-charon-1.x branch from d76c0e8 to f51c6ff Compare March 6, 2026 18:14
@renovate renovate bot changed the title chore(deps): update obolnetwork/charon docker tag to v1.9.0 chore(deps): update dependency obolnetwork/charon to v1.9.1 Mar 6, 2026
@renovate renovate bot changed the title chore(deps): update dependency obolnetwork/charon to v1.9.1 chore(deps): update obolnetwork/charon docker tag to v1.9.1 Mar 9, 2026
@renovate renovate bot force-pushed the renovate/obolnetwork-charon-1.x branch from f51c6ff to 991b851 Compare March 9, 2026 15:38
@OisinKyne OisinKyne merged commit 6e1e952 into main Mar 10, 2026
3 checks passed
@OisinKyne OisinKyne deleted the renovate/obolnetwork-charon-1.x branch March 10, 2026 18:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant