chore(deps): update obolnetwork/charon docker tag to v1.8.0

[renovate]

This PR contains the following updates:

Package	Update	Change
obolnetwork/charon	minor	v1.7.1 → v1.8.0

---

Release Notes

obolnetwork/charon (obolnetwork/charon)

v1.8.0

Compare Source

v1.8.0 - 2025-12-17

This is Charon's v1.8.0 release. Feedback is welcome and appreciated, please use github issues or discord if you have trouble with this release.

Partial deposit submission and retrieval

Support for submitting and fetching partial validator deposits via the new charon deposit sign and charon deposit fetch commands. This enables operators to update deposit data for validators after cluster creation but before activation.

This feature is particularly useful for large clusters where only a subset of validators are activated initially, and business or operational requirements may change over time. Operators can re-sign updated deposit data, with partial signatures aggregated once a threshold is reached, after which the full deposit data can be retrieved with charon deposit fetch or from the Obol API.

Read the rest of the release notes for more:

Full Changelog: v1.7.3..v1.8.0

Feature

• charon deposit sign && charon deposit fetch #​3992 (#​4032)
• Update minimum version warning log for fusaka fork #​3978 (#​4000)
• Track blinded/unblinded block building from the BN #​4106 (#​4117)
• Add Date-Milliseconds and X-Timeout-Ms to charon alpha test mev #​4045 (#​4074)

Bug

• Unknown git hash in Charon v1.5.2 pre-built binary #​4001 (#​4057)
• Signed block fetcher retries on missed blocks #​4035 (#​4041)

Refactor

• Catch HTTP 409 Duplicate Request gracefully in charon dkg --publish #​4107 (#​4121)
• Errors revamp #​3882 (#​4050,#​4044,#​4046,#​4047,#​4038)
• Remove the pretty key from JSON logging #​3924 (#​4005)
• Move chain split check to pre-prepare round (#​4011)
• Add eth2wrap logic to proxy (#​4042)]
• Builder registration redesign (#​4060)

Test

• Rework all disabled and removed tests #​3988 (#​4064,#​4063,#​4062,#​4058)

Misc

• Automate release with pipelines #​3933 (#​4125,#​4101,#​4084,#​4100)

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 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.12.0 ❗	Lighthouse v8.0.1	Lodestar v1.38.0	Nimbus v25.11.1	Prysm v7.1.0	Vouch 1.12.0 ❗
Teku v25.12.0 ❗	✅	✅	✅	✅	✅	🟡
Lighthouse v8.0.1	✅	✅	✅	✅	✅	🟡
Lodestar v1.38.0	✅	✅	✅	✅	✅	🟡
Nimbus v25.11.1	✅	✅	✅	✅	✅	🟡
Prysm v7.1.0	✅	✅	✅	✅	✅	🟡
Grandine v2.0.1	✅	✅	✅	✅	✅	🟡

[!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 in version <v1.37.0 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. This has been fixed in v1.37.0.

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.

What's Changed

• app: bump version from 1.7-dev to 1.8-dev (#​3998)

• *: bump go-eth2-client v0.27.1 (#​4002)

• docs: fix some a/an issues (#​4007)

• qbft: move chain split check to preprepare round (#​4011)

• cmd: update docker flags and api url in create dkg (#​4024)

• *: replace context.WithCancel with t.Context (#​4026)

• app/sse: fix bucket delay values (#​4029)

• cmd: use WaitGroup.Go to simplify code (#​4033)

• *: fix some minor issues (#​4036)

• *: claude init (#​4037)

• *: various optimizations (#​4039)

• core/validatorapi: add eth2wrap logic to proxy (#​4042)

• *: replace Split in loops with more efficient SplitSeq (#​4043)

• *: function comments revamp (#​4048)

• *: replace sort.Slice with slices.Sort for natural ordering (#​4054)

• *: builder reg redesign (#​4060)

• Bump golangci-lint v2.6.1 (#​4075)

• eth2util/rlp: fixed wrong condition (#​4087)

• cmd: relay override for add-vals (#​4091)

• cluster: fix incorrect function name in comment (#​4097)

• cluster: fixed testdata (#​4124)

• core: fix incorrect struct name in comment (#​4135)

• core/validatorapi: support proxy of SSE events (#​4140)

• *: bump golangci-lint v2.6.2 (#​4142)

• dkg: fixed edit remove-operators (#​4147)

• *: new github actions user (#​4152)

• *: add base64 decode to relase scripts (#​4158)

• *: add check-latest to setup-go (#​4159)

• app/version: bump minor version to v1.8-rc (#​4160)

• *: cherry pick for 1.8.0 (#​4173)

• *: v1.8.0-rc2 (#​4178)

• *: v1.8.0-rc2 (#​4182)

• *: cherry pick for v1.8.0 (#​4185)

• app/version: bump v1.8 to stable (#​4191)

v1.7.3

Compare Source

v1.7.3 - 2025-12-12

This is recommended, but not required, non-urgent patch release for Charon v1.7.3. Feedback is welcome and appreciated, please use github issues or discord if you have trouble with this release.

Read the rest of the release notes for more:

Full Changelog: v1.7.2..v1.7.3

Features

• Add new core_fetcher_proposal_blinded metric #​4117

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	Lodestar v1.37.0	Nimbus v25.9.2	Prysm v6.1.3	Vouch 1.12.0 ❗
Teku v25.10.0 ❗	✅	✅	✅	✅	✅	🟡
Lighthouse v8.0.0	✅	✅	✅	✅	✅	🟡
Lodestar v1.37.0	✅	✅	✅	✅	✅	🟡
Nimbus v25.9.2	✅	✅	✅	✅	✅	🟡
Prysm v6.1.3	✅	✅	✅	✅	✅	🟡
Grandine v2.0.0	✅	✅	✅	✅	✅	🟡

[!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 in version <v1.37.0 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. This has been fixed in v1.37.0.

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.

What's Changed

• *: cherry pick for 1.7.3 (#​4172)

v1.7.2

Compare Source

v1.7.2 - 2025-12-05

This is recommended, but not required, non-urgent patch release for Charon v1.7.1. Feedback is welcome and appreciated, please use github issues or discord if you have trouble with this release.

Read the rest of the release notes for more:

Full Changelog: v1.7.1..v1.7.2

Features

• Add new core_fetcher_proposal_blinded metric #​4117

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.

What's Changed

• *: cherry picking blinded metric (#​4129)

• app/version: bump v1.7 to stable (#​4145)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.