stakestack
UTC
GitHub

Charon

Obol · Go · BUSL-1.1

DVT middleware that splits one validator across a cluster of nodes (Obol Network).

dvtEthereum MainnetHoodiSepoliaHolesky
ObolNetwork/charonDocsWebsiteobolnetwork/charon

Charon enforces a compatibility matrix with CL and VC versions; breaking changes usually require a cluster-wide coordinated upgrade.

Releases

Rated by the charon-notes rules · weight 1.5
Channel
Severity
Type
Network
Fork
34 releases
Charonv2.0.0-rc2
Why this rating
  • high (hoodi): > [!WARNING] > This is a release candidate and a required upgrade for hoodi operators only.
  • high (hoodi): All nodes in a cluster must run Charon v2.0.0-rc2 or newer before the Gloas fork activates on Hoodi on October 26, 2026, at 17:42:48 UTC.
  • security wording: "- ci: fix sonarcloud supply-chain vulnerabilities (#4631) by @KaloyanTanev"
  • performance wording: "Consensus messages stay small, so the cluster agrees on the block faster and submits it to the beacon node sooner."
Oct 21, 2026
Charonv1.11.2
Why this rating
  • high (all networks): > [!CAUTION] > This is a required release for all Operators. > > This release is not Gloas/Glamsterdam ready, another upgrade will be required before the hardfork on your network.
  • security wording: "It bumps golang's version to latest fixing known vulnerabilities including compromised CA certificates in CVE-2026-111943."
Oct 21, 2026
Charonv2.0.0-rc1
Why this rating
  • high (hoodi): > [!WARNING] > This is a release candidate and a required upgrade for hoodi operators only.
  • high (hoodi): All nodes in a cluster must run Charon v2.0.0-rc1 or newer before the Gloas fork activates on Hoodi on October 26, 2026, at 17:42:48 UTC.
  • security wording: "- ci: fix sonarcloud supply-chain vulnerabilities (#4631) by @KaloyanTanev"
  • performance wording: "Consensus messages stay small, so the cluster agrees on the block faster and submits it to the beacon node sooner."
Oct 20, 2026
Charonv1.11.1
Why this rating
  • medium (all networks): This is a recommended patch release of Charon v1.11.1.
  • security wording: "It hardens the chain_split_halt feature flag, invalidates cached duties that a lagging beacon node computed from a stale chain view, and bundles a number of stability and security…"
Oct 14, 2026
Charonv1.11.0
Why this rating
  • medium (all networks): As always, we recommend upgrading all nodes in a cluster in close succession.
  • security wording: "- ci: fix sonarcloud supply-chain vulnerabilities (#4631)"
  • deprecation wording: "- Remove deprecated holesky testnet support (#4485)"
  • performance wording: "- *: optimise sync contribution fetching (#4615)"
Aug 25, 2026
Charonv1.10.3
Why this rating
  • medium (all networks): This is recommended patch release of Charon v1.10.3.
  • fork readiness: "This release of Charon is backwards compatible with Charon >= v1.0.*, though only v1.7.* and newer are Fulu-ready."
Jun 24, 2026
Charonv1.10.2
Why this rating
  • medium (all networks): This is highly recommended patch release of Charon v1.10.2.
  • fork readiness: "This release of Charon is backwards compatible with Charon >= v1.0.*, though only v1.7.* and newer are Fulu-ready."
  • performance wording: "This patch has numerous security and performance fixes."
Jun 10, 2026
Charonv1.9.5
Why this rating
  • medium (all networks): This is highly recommended patch release of Charon v1.9.5.
  • fork readiness: "This release of Charon is backwards compatible with Charon >= v1.0.*, though only v1.7.* and newer are Fulu-ready."
May 20, 2026
Charonv1.10.1
Why this rating
  • medium (all networks): This is highly recommended patch release of Charon v1.10.1.
  • fork readiness: "This release of Charon is backwards compatible with Charon >= v1.0.*, though only v1.7.* and newer are Fulu-ready."
May 20, 2026
Charonv1.10.0
Why this rating
  • consensus-safety wording: "- *: missed proposal debug skill (#4349)"
  • fork readiness: "This release of Charon is backwards compatible with Charon >= v1.0.*, though only v1.7.* and newer are Fulu-ready."
Apr 27, 2026
Charonv1.9.4
Why this rating
  • medium (all networks): This is highly recommended patch release of Charon v1.9.4.
  • fork readiness: "This release of Charon is backwards compatible with Charon >= v1.0.*, though only v1.7.* and newer are Fulu-ready."
Apr 22, 2026
Charonv1.10.0-rc2
Why this rating
  • consensus-safety wording: "- *: missed proposal debug skill (#4349)"
  • fork readiness: "This release of Charon is backwards compatible with Charon >= v1.0., though only v1.7. and newer are Fulu-ready."
Apr 8, 2026
Charonv1.9.3
Why this rating
  • medium (all networks): This is highly recommended patch release of Charon v1.9.3.
  • fork readiness: "This release of Charon is backwards compatible with Charon >= v1.0.*, though only v1.7.* and newer are Fulu-ready."
  • performance wording: "This patch fixes memory leak in the duties cache."
Apr 1, 2026
Charonv1.9.3-rc1
Why this rating
  • fork readiness: "This release of Charon is backwards compatible with Charon >= v1.0.*, though only v1.7.* and newer are Fulu-ready."
  • performance wording: "This patch fixes memory leak in the duties cache."
Mar 25, 2026
Charonv1.9.2
Why this rating
  • medium (all networks): This release Charon v1.9.2 is recommended for Operators sending logs to Obol.
  • fork readiness: "This release of Charon is backwards compatible with Charon >= v1.0.*, though only v1.7.* and newer are Fulu-ready."
  • performance wording: "This patch improves the performance of nodes sending logs, by taking the log submission out of contention with the main runtime."
Mar 12, 2026
Charonv1.8.3
Why this rating
  • medium (all networks): This release Charon v1.8.3 is recommended for Operators sending logs to Obol.
  • fork readiness: "This release of Charon is backwards compatible with Charon >= v1.0.*, though only v1.7.* and newer are Fulu-ready."
  • performance wording: "This patch improves the performance of nodes sending logs, by taking the log submission out of contention with the main runtime."
Mar 12, 2026
Charonv1.9.1
Why this rating
  • high (all networks); medium (all networks): This is non-urgent but recommended patch release of Charon v1.9.0.
  • fork readiness: "This release of Charon is backwards compatible with Charon >= v1.0.*, though only v1.7.* and newer are Fulu-ready."
Mar 6, 2026
Charonv1.9.0
Feb 24, 2026
Charonv1.9.0-rc3
Feb 18, 2026
Charonv1.9.0-rc2
Feb 11, 2026
Charonv1.8.2
Why this rating
  • high (all networks); medium (all networks): This is non-urgent but recommended patch release of Charon v1.8.1.
  • fork readiness: "This release of Charon is backwards compatible with Charon >= v1.0.*, though only v1.7.* and newer are Fulu-ready."
  • performance wording: "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."
Feb 9, 2026
Charonv1.8.1
Why this rating
  • high (all networks): This is not required, non-urgent patch release for Charon v1.8.0.
  • fork readiness: "This release of Charon is backwards compatible with Charon >= v1.0.*, though only v1.7.* and newer are Fulu-ready."
Jan 7, 2026
Charonv1.8.0
Why this rating
  • consensus-safety wording: "- Signed block fetcher retries on missed blocks #4035 (#4041)"
  • fork readiness: "Though only v1.3.* and newer are Pectra-ready and v1.7.* and newer are Fulu-ready."
  • performance wording: "This can impact your cluster's performance, particularly if you have more than the fault tolerance threshold of your cluster running Lodestar's validator client, and many validato…"
Dec 18, 2025
Charonv1.7.3
Why this rating
  • high (all networks): This is recommended, but not required, non-urgent patch release for Charon v1.7.3.
  • fork readiness: "This release of Charon is backwards compatible with Charon v1.0.*, v1.1.*, v1.2.0, v1.3.*, v1.4.*, v1.5.*, v1.6.*, v1.7.* Though only v1.3.* and newer are Pectra-ready and only v1…"
  • performance wording: "This can impact your cluster's performance, particularly if you have more than the fault tolerance threshold of your cluster running Lodestar's validator client, and many validato…"
Dec 16, 2025
Charonv1.7.2
Why this rating
  • high (all networks): This is recommended, but not required, non-urgent patch release for Charon v1.7.1.
  • fork readiness: "This release of Charon is backwards compatible with Charon v1.0.*, v1.1.*, v1.2.0, v1.3.*, v1.4.*, v1.5.*, v1.6.*, v1.7.* Though only v1.3.* and newer are Pectra-ready and only v1…"
  • performance wording: "This can impact your cluster's performance, particularly if you have more than the fault tolerance threshold of your cluster running Lodestar's validator client, and many validato…"
Dec 5, 2025
Charonv1.7.1
Why this rating
  • high (all networks): This is recommended, but not required, non-urgent patch release for Charon v1.7.0.
  • fork readiness: "This release of Charon is backwards compatible with Charon v1.0.*, v1.1.*, v1.2.0, v1.3.*, v1.4.*, v1.5.*, v1.6.*, v1.7.* Though only v1.3.* and newer are Pectra-ready and only v1…"
  • performance wording: "This can impact your cluster's performance, particularly if you have more than the fault tolerance threshold of your cluster running Lodestar's validator client, and many validato…"
Oct 24, 2025
Charonv1.7.0
Why this rating
  • consensus-safety wording: "- Attestation source and target vote consensus - chain split halt #3876 #4011 (#3946)"
  • fork readiness: "This is Charon's first Fulu-ready version."
  • performance wording: "Now, most VCs have updated their implementations, and we are releasing opt-in support for the performance improvement, if you confirm your VC supports the behaviour."
Oct 8, 2025
Charonv1.7.0-rc4
Why this rating
  • consensus-safety wording: "- Attestation source and target vote consensus - chain split halt #3876 #4011 (#3946)"
  • fork readiness: "This is Charon's first Fulu-ready pre-release version."
  • performance wording: "Now, most VCs have updated their implementations, and we are releasing opt-in support for the performance improvement, if you confirm your VC supports the behaviour."
Oct 6, 2025
Charonv1.7.0-rc3
Why this rating
  • consensus-safety wording: "- Attestation source and target vote consensus - chain split halt #3876 (#3946)"
  • fork readiness: "This is Charon's first Fulu-ready pre-release version."
Oct 1, 2025
Charonv1.7.0-rc2
Why this rating
  • consensus-safety wording: "- Attestation source and target vote consensus - chain split halt #3876 (#3946)"
  • fork readiness: "This is Charon's first Fulu-ready pre-release version."
Sep 29, 2025
Charonv1.7.0-rc1
Why this rating
  • consensus-safety wording: "- Attestation source and target vote consensus - chain split halt #3876 (#3946)"
  • fork readiness: "This is Charon's first Fulu-ready pre-release version."
Sep 26, 2025
Charonv1.6.1
Why this rating
  • fork readiness: "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."
Sep 15, 2025
Charonv1.6.0
Why this rating
  • performance wording: "QUIC aims to improve performance in large, distant clusters."
Aug 27, 2025
Charonv1.6.0-rc5
Why this rating
  • performance wording: "QUIC aims to improve performance in large, distant clusters."
Aug 26, 2025