Skip to content

chore(deps): update obolnetwork/charon docker tag to v1.11.0 - #304

Open
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/dv-pod-chart-updates
Open

renovate[bot] wants to merge 2 commits into
mainfrom
renovate/dv-pod-chart-updates

Conversation

@renovate

@renovate renovate Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
obolnetwork/charon minor 1.10.0 → 1.11.0
obolnetwork/charon minor v1.10.0 → v1.11.0

Release Notes

obolnetwork/charon (obolnetwork/charon)

v1.11.0

Compare Source

v1.11.0 - 2026-08-25

Obol Logo

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

This release focuses on hardening and stability across consensus, DKG and networking. The release includes one wire-format change - a new per-subcommittee sync committee contribution format is negotiated automatically between nodes, only activating once a threshold of cluster peers advertise v1.11 or newer and otherwise falling back to the previous format. As always, we recommend upgrading all nodes in a cluster in close succession.

Read the rest of the release notes for more:

Full Changelog: v1.10.3..v1.11.0

Hardening and stability

This release is a substantial hardening and stability release. It bundles a large batch of QBFT consensus correctness fixes (rejecting zero-value and equivocating-leader messages, preserving local values on comparison failure), DKG and cluster definition/lock validation hardening, more robust partial signature exchange and p2p stream handling, a per-subcommittee sync committee contribution fix, and a fix for a potential code-injection vector in CI. See the Bug and Refactor sections below for the full list.

NAT hole punching improvements

Charon now uses libp2p's native EnableHolePunching() to establish direct connections between NAT'd peers, replacing the previous ForceDirectConnections approach that only succeeded when both peers happened to dial at the same moment. This should improve peer connectivity for operators behind NATs without requiring manual port forwarding.

Feature
  • Add support for cluster-definition v1.11 format #​4265 (#​4291)
  • Check fee recipient against local node configuration (#​4474)
  • Surface remote cluster state in the list command (#​4497)
  • Adopt beacon node v2 API endpoints (#​4504)
  • Add p2p message send duration histogram metric (#​4506)
  • Add metric tracking insufficient round-change messages #​4478 (#​4512)
  • Improve NAT hole punching for peer connectivity #​4233 (#​4516)
  • Adopt versioned proposer duties v2 endpoints (#​4564)
  • Add metric for sync committee message cohorts (#​4587)
  • Opt-in loading of incomplete validator_keys store (#​4591)
  • Add dv_client field to the peerinfo protocol (#​4632)
Bug
Refactor
  • Remove deprecated holesky testnet support (#​4485)
  • Refactor consensus and QBFT message handling (#​4505,#​4557)
  • Harden fee recipient signing and fetching paths (#​4571)
  • Improve DKG reshare and ceremony robustness (#​4574,#​4616,#​4650)
  • Correct typo in p2p error message (#​4578)
  • Add leading slash to priority protocol ID (#​4605)
  • Remove noisy QUIC happy-path debug logs (#​4645)
Docs
  • Refresh stale CLAUDE.md and README.md docs (#​4573)
  • Refresh architecture and package structure documentation (#​4580)
  • Auto-fetch latest client versions for release notes (#​4597)
Test
Misc
Compatibility Matrix

❗ An issue between Lodestar BN and Lighthouse, Nimbus and Prysm VCs has been discovered. It has surfaced with testing latest versions of the above mentioned clients, however, it is applicable for multiple older Lodestar CL versions. Those duty failures are not related to Charon v1.11.0. If node operators are using any of those 3 combinations and are experiencing issues, we strongly recommend switching to different VC or BN until patches are released. We will keep this section of the release notes up to date with latest updates.

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 clients 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 fail consistently
Validator 👉 Consensus 👇 Teku v26.8.0 Lighthouse v8.2.2 Lodestar v1.46.0 Nimbus v26.7.0 Prysm v7.1.8 Vouch v1.13.0 ❗
Teku v26.8.0 ❗ ✅ ✅ ✅ ✅ ✅ 🟡
Lighthouse v8.2.2 ✅ ✅ ✅ ✅ ✅ 🟡
Lodestar v1.46.0 ✅ 🟠 ✅ 🟠 🟠 🟡
Nimbus v26.7.0 ✅ ✅ ✅ ✅ ✅ 🟡
Prysm v7.1.8 ✅ ✅ ✅ ✅ ✅ 🟡
Grandine v2.0.6 ✅ ✅ ✅ ✅ ✅ 🟡
What's Changed

v1.10.3

Compare Source

v1.10.3 - 2026-06-24

Obol Logo

This is recommended patch release of Charon v1.10.3. This patch fixes proposer duties fetching in Lighthouse VC v8.2.0 and improves fetch_att_on_block feature flag. It also includes couple of dependency bumps. 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.10.2..v1.10.3

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.4.0 Lighthouse v8.1.3 Lodestar v1.42.0 Nimbus v26.3.1 Prysm v7.1.3 Vouch v1.12.1 ❗
Teku v26.4.0 ❗ ✅ ✅ ✅ ✅ ✅ 🟡
Lighthouse v8.1.3 ✅ ✅ ✅ ✅ ✅ 🟡
Lodestar v1.42.0 ✅ ✅ ✅ ✅ ✅ 🟡
Nimbus v26.3.1 ✅ ✅ ✅ ✅ ✅ 🟡
Prysm v7.1.3 ✅ ✅ ✅ ✅ ✅ 🟡
Grandine v2.0.4 ✅ ✅ ✅ ✅ ✅ 🟡

What's Changed

v1.10.2

Compare Source

v1.10.2 - 2026-06-10

Obol Logo

This is highly recommended patch release of Charon v1.10.2. This patch has numerous security and performance fixes. 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.10.1..v1.10.2

Bugfix

  • Fix memory leak of prometheus metrics, growing cardinality uncontrollably #​4553
  • Do not store expired duties in ParSigDB; rework deadliner #​4552
  • Fix key in the KV in-memory storage of aggregation duties in DutyDB #​4544
  • Fix charon exit fetch signature aggregation #​4542

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.4.0 Lighthouse v8.1.3 Lodestar v1.42.0 Nimbus v26.3.1 Prysm v7.1.3 Vouch v1.12.1 ❗
Teku v26.4.0 ❗ ✅ ✅ ✅ ✅ ✅ 🟡
Lighthouse v8.1.3 ✅ ✅ ✅ ✅ ✅ 🟡
Lodestar v1.42.0 ✅ ✅ ✅ ✅ ✅ 🟡
Nimbus v26.3.1 ✅ ✅ ✅ ✅ ✅ 🟡
Prysm v7.1.3 ✅ ✅ ✅ ✅ ✅ 🟡
Grandine v2.0.4 ✅ ✅ ✅ ✅ ✅ 🟡

What's Changed

v1.10.1

Compare Source

v1.10.1 - 2026-05-20

Obol Logo

This is highly recommended patch release of Charon v1.10.1. This patch fixes an issue with Charon node panic-ing on unknown payload from another Charon node. There is also a fix of deposit fetch command that failed to verify signature in certain cases. 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.10.0..v1.10.1

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.4.0 Lighthouse v8.1.3 Lodestar v1.42.0 Nimbus v26.3.1 Prysm v7.1.3 Vouch v1.12.1 ❗
Teku v26.4.0 ❗ ✅ ✅ ✅ ✅ ✅ 🟡
Lighthouse v8.1.3 ✅ ✅ ✅ ✅ ✅ 🟡
Lodestar v1.42.0 ✅ ✅ ✅ ✅ ✅ 🟡
Nimbus v26.3.1 ✅ ✅ ✅ ✅ ✅ 🟡
Prysm v7.1.3 ✅ ✅ ✅ ✅ ✅ 🟡
Grandine v2.0.4 ✅ ✅ ✅ ✅ ✅ 🟡

What's Changed


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Every minute (* * * * *)
  • 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 these updates 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 requested a review from a team as a code owner October 6, 2026 18:36
@renovate

renovate Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

This branch has not been deployed

No deployments
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.

0 participants