Repository navigation
chore(deps): update obolnetwork/charon docker tag to v1.11.0 - #302
Open
renovate[bot] wants to merge 2 commits into
Open
renovate[bot] wants to merge 2 commits into
renovate[bot] wants to merge 2 commits into
Conversation
Contributor
Author
Edited/Blocked NotificationRenovate 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. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.10.0→v1.11.01.10.0→1.11.0Release Notes
obolnetwork/charon (obolnetwork/charon)
v1.11.0Compare Source
v1.11.0 - 2026-08-25
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 previousForceDirectConnectionsapproach 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
cluster-definitionv1.11 format #4265 (#4291)listcommand (#4497)v2API endpoints (#4504)NAThole punching for peer connectivity #4233 (#4516)v2endpoints (#4564)validator_keysstore (#4591)dv_clientfield to thepeerinfoprotocol (#4632)Bug
app/eth2wrap(#4486)SSEevent proxying to validator clients (#4495)charonCLI command behaviours (#4523,#4559,#4577,#4579)SSZoffset validation when decoding (#4529)DutyDBby committee index for aggregation #4006 (#4544)deadlinerscheduling logic (#4552)headevent (#4561)validator_keysstore (#4576)core/priorityprotocol sorting and duty gating (#4611,#4643)sloghandler panic on named types (#4640)Refactor
holeskytestnet support (#4485)priorityprotocol ID (#4605)QUIChappy-path debug logs (#4645)Docs
CLAUDE.mdandREADME.mddocs (#4573)Test
Misc
libp2p,golangci-lint, and Debian base image (#4475,#4568,#4575,#4584)v1.11dev, rc, and stable (#4494,#4589,#4664)QUICfalse-error logs (#4582,#4585)1MBlimit onpeerinfoprotocol messages (#4625)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
What's Changed
v1.10.3Compare Source
v1.10.3 - 2026-06-24
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_blockfeature 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
What's Changed
app: bump patch version to v1.10-rc (#4565)
*: v1.10.3-rc1 (#4567)
app/version: bump v1.10 to stable (#4569)
v1.10.2Compare Source
v1.10.2 - 2026-06-10
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
charon exit fetchsignature aggregation #4542Compatibility 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
What's Changed
app: bump patch version to v1.10-rc (#4548)
*: v1.10.2-rc1 (#4549)
*: cherry-picks for v1.10.2-rc2 (#4555)
app/version: bump v1.10 to stable (#4556)
v1.10.1Compare Source
v1.10.1 - 2026-05-20
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 fetchcommand 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
What's Changed
Cherry-pick #4526 PR (#4532)
core: ssz offset validation (#4529) (#4530)
Configuration
📅 Schedule: (UTC)
* * * * *)🚦 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.
This PR was generated by Mend Renovate. View the repository job log.