v1.7.1
v1.7.1 - 2025-10-23
This is recommended, but not required, non-urgent patch release for Charon v1.7.0. Feedback is welcome and appreciated, please use github issues or discord if you have trouble with this release.
Fulu Activation Schedule
Please consult the official Ethereum blog for the latest client versions to run ahead of the hardfork.
| Network | Hardfork Date |
|---|---|
| Holesky | Completed |
| Sepolia | Completed |
| Hoodi | October 28th 2025 18:53:12 UTC |
| Mainnet | December 3rd 2025 (Estimated) |
Warning
Failure to update all your client versions before the hardfork date could cause your validator to go offline, or worse.
Read the rest of the release notes for more:
Full Changelog: v1.7.0..v1.7.1
Bugfixes
- Fix bucket delay values #4029
- Update docker flags and api url in create dkg #4024
- Handle 404 errors gracefully for signed blocks on inclusion check #4041
Compatibility Matrix
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.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.10.0 ❗ | Lighthouse v8.0.0-rc.2 | Lodestar v1.35.0 | Nimbus v25.9.2 | Prysm v6.1.3 | Vouch 1.12.0-beta.3 ❗ |
|---|---|---|---|---|---|---|
| Teku v25.10.0 ❗ | ✅ | ✅ | ✅ | ✅ | ✅ | 🟡 |
| Lighthouse v8.0.0-rc.2 | ✅ | ✅ | ✅ | ✅ | ✅ | 🟡 |
| Lodestar v1.35.0 | ✅ | ✅ | ✅ | ✅ | ✅ | 🟡 |
| Nimbus v25.9.2 | ✅ | ✅ | ✅ | ✅ | ✅ | 🟡 |
| Prysm v6.1.3 | ✅ | ✅ | ✅ | ✅ | ✅ | 🟡 |
| Grandine v2.0.0.rc0 | ✅ | ✅ | ✅ | ✅ | ✅ | 🟡 |
Note
There is currently an incompatibility between validator clients that may cause attestation aggregation duties to fail. Aggregation duties are not economically rewarded nor punished for their completion.
To ensure aggregations succeed; have at least threshold of nodes in the cluster running one of Lodestar, Lighthouse, and Nimbus, or alternatively; have a threshold of nodes in the cluster running one of Teku and Prysm. This incompatibility will be remediated in upcoming client releases.
Warning
Lodestar's validator client's default behaviour is to skip the next slot if it fails an attestation or aggregation. 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 validators running in the cluster.
If your cluster is not successfully aggregating, you should ideally swap to a set of compatible validator clients listed above, along with ensuring your clients have the appropriate --distributed flag set to enable distributed aggregation mode.