v1.4.0 - 2025-05-05
Note
Both this version and the prior v1.3.0 version of Charon are Pectra ready. You do not need to upgrade to this version ahead of the hardfork, and may schedule this upgrade when convenient.
This is Charon's v1.4.0 release. Feedback is welcome and appreciated, please use github issues or discord if you have trouble with this release.
Notable user-facing features shipping in this release include:
- Charon's
--graffiti
and--graffiti-disable-client-append
flags (to disable client version packing), allow operators to set custom graffiti strings to be attached to block proposals their node makes. - Charon's
--publish
(and--publish-address
) flag in thetest
command, allows operators to opt into publishing their test data. This data assists in the ongoing improvement of Charon's performance. - Charon can now verify Safe{Wallet} signatures (and other EIP1271 smart contract signatures) on the
dkg
andrun
commands with the addition of the--execution-client-rpc-address
flag. - Users can now prepare DKG invitations using the DV Launchpad from the
charon create dkg
command, by adding--operator-addresses
(instead of--operator-enrs
) and the--publish
flag. (Using the DV Launchpad comes with standard terms of use.) - This release also includes our first iteration of pre-built binaries for Charon. Use them with caution for the time being.
Read the rest of the release notes for more:
Full Changelog: v1.3.0..v1.4.0
Feature
- New default partial deposits in compounding mode #3640 (#3641)
- Custom Graffiti #3608 (#3604)
- Traceability of Proposal flow #3429 (#3606,#3593)
- Add optional --publish flags to our test commands #3350 (#3631)
- Smart contract based signature support in cluster definitions/locks #3458 (#3510)
charon create dkg
can return a launchpad invitation to a DKG #3518 (#3583)- Add Hoodi testnet (#3587)
Bug
- Review fetch active/complete activators by slot #3636 (#3642)
- SSZ unmarshaling failures (#3599)
- Loaded keys ordering (#3655)
Docs
Misc
- Run CI pipeline tests in parallel #3209 (#3622)
- Updated year to 2025 in file headers #3592 (#3595)
- Manage dependencies with
tool
directive #3613 (#3614) - Bump golang version to 1.24 #3596 (#3605)
Compatibility Matrix
This release of Charon is backwards compatible with Charon v1.0, v1.1.*, v1.2, v1.3.
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.4.1 | Lighthouse v7.0.0 | Lodestar v1.29.0 | Nimbus v25.4.1 | Prysm v6.0.0 | Remarks |
---|---|---|---|---|---|---|
Teku v25.4.1 | ✅ | 🟡 | ✅ | ✅ | ✅ | Teku beacon node needs the --validators-graffiti-client-append-format=DISABLED flag in order to produce blocks properly.
|
Lighthouse v7.0.0 | ✅ | 🟡 | ✅ | ✅ | ✅ | Lighthouse validator client is only failing aggregation duties, which are not directly penalised but impact network density at high scale. We expect a fix for this very soon. |
Lodestar v1.29.0 | ✅ | 🟡 | ✅ | ✅ | ✅ | |
Nimbus v25.4.1 | ✅ | 🟡 | ✅ | ✅ | ✅ | |
Prysm v6.0.0 | ✅ | 🟡 | ✅ | ✅ | ✅ | Prysm beacon node experienced failed proposal duties only in the first epoch of electra. |
Note
All combinations miss duties in only the first slot of the first epoch of electra hardfork. We are working on a fix for this.