v1.0.1 - 2024-07-15
This release updates go-eth2-client in order to support Lodestar Beacon Node v1.20, which now defaults to SSZ encoding.
Compatibility Matrix
This matrix details the combination of beacon node + validator clients and their corresponding versions the Obol 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.6.1 | Lighthouse v5.2.11 | Lodestar v1.20.0 | Nimbus v24.5.1 | Prysm PR | Remarks |
|---|---|---|---|---|---|---|
| Teku v24.6.1 | ✅ | 🟡 | ✅ | ✅ | ✅ | Teku bn needs the --validators-graffiti-client-append-format=DISABLED flag in order to produce blocks properly.
|
| Lighthouse v5.2.1 | ✅ | 🟡 | ✅ | ✅ | 🟠 | Lighthouse vc are only failing aggregation duties, which are not directly penalised but impact network density at high scale.
|
| Nimbus v24.5.1 | 🔴 | 🟡 | ✅ | ✅ | ✅ | Nimbus beacon nodes requires that you add the following flag to charon run: charon run --feature-set-enable=json_requests
|
| Prysm v5.0.3 | ✅ | 🟡 | ✅ | ✅ | ✅ | Prysm validator needs a particular pull request merged and released for aggregation duties to succeed.
|
| Lodestar v1.20.0 | ✅ | 🟡 | ✅ | ✅ | ✅ |
Full Changelog: v1.0.0..v1.0.1
What's Changed
Footnotes
-
sync committee and aggregator duties are not yet supported in a DV setup by Lighthouse, all other duties work as expected. ↩