v1.1.2 - 2024-10-28
This is a non-urgent, patch release, which introduces a fix for DKG key creation issues.
Due to an upstream dependency issue, DKG running on AVX-enabled CPUs might fail due to misgenerated private keys.
Details the bug can be found here.
Full Changelog: v1.1.1...v1.1.2
Bugfixes
Compatibility Matrix
This release of Charon is backwards compatible with Charon v1.0.0 - v1.1.1. DKGs need to be completed with clients on the same minor release.
Due to the above mentioned issue, it is recommended to run DKGs with Charon v1.1.2 onwards.
The below matrix details a combination of beacon node + 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
| Consensus 👇 Validator 👉 | Teku v24.8.0 | Lighthouse v5.3.01 | Lodestar v1.20.2 | Nimbus v24.7.0 | Prysm 5.1.0 | Remarks |
|---|---|---|---|---|---|---|
| Teku v24.8.0 | 🟡 | 🟡 | ✅ | ✅ | 🟠 | Teku bn needs the --validators-graffiti-client-append-format=DISABLED flag in order to produce blocks properly. Teku vc are only failing aggregation duties 50% of the time, which are not directly penalised but impact network density at high scale. |
| Lighthouse v5.3.0 | 🟡 | 🟡 | ✅ | ✅ | 🟠 | Lighthouse vc are only failing aggregation duties, which are not directly penalised but impact network density at high scale. |
| Nimbus v24.7.0 | 🟡 | 🟡 | ✅ | ✅ | ✅ | Nimbus beacon nodes requires that you add the following flag to charon run: charon run --feature-set-enable=json_requests |
| Prysm v5.1.0 | 🟡 | 🟡 | ✅ | ✅ | ✅ | |
| Lodestar v1.20.2 | 🟡 | 🟡 | ✅ | ✅ | 🔴 |
-
sync committee and aggregator duties are not yet supported in a DV setup by Lighthouse, all other duties work as expected. ↩