Skip to content

chore(deps): update ethereum el/cl client updates#658

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
renovate/ethereum-clients
Open

chore(deps): update ethereum el/cl client updates#658
github-actions[bot] wants to merge 1 commit into
mainfrom
renovate/ethereum-clients

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 22, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
erigontech/erigon minor v3.4.3 → v3.5.0
ethereum/go-ethereum patch v1.17.3 → v1.17.4
sigp/lighthouse minor v8.1.3 → v8.2.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

erigontech/erigon (erigontech/erigon)

v3.5.0

Compare Source

Erigon v3.5.0 — Tidal Tails

Erigon 3.5.0 is a major release headlined by parallel block execution becoming the default and initial support for Ethereum's upcoming Glamsterdam hardfork. It is a drop-in upgrade for 3.4.x users — no re-sync required; existing datadirs upgrade their prune configuration automatically (see Breaking Changes).

Key Features
  • Parallel block execution, on by default. Erigon now executes EVM transactions across multiple cores by default, using the Block-STM (software transactional memory) design pioneered by Aptos: transactions run optimistically in parallel and are re-validated against a multi-version state, re-executing only on conflict (#​21591 by @​mh0lt, closes #​17630). Revert to serial with EXEC3_PARALLEL=false or --exec.serial.
  • Glamsterdam devnet support. Initial implementation of Ethereum's next hardfork: Block-Level Access Lists (EIP-7928), enshrined Proposer-Builder Separation / "Gloas" (EIP-7732) in Caplin, gas repricings (EIP-8037, EIP-7976, EIP-7981), larger contracts (EIP-7954), transfer logs (EIP-7708), and the eth/71 Block Access List wire protocol (EIP-8159). Devnet/testing only — not scheduled on mainnet or any public testnet.
  • debug_executionWitness. Stateless execution-witness generation (EIP-7928/8025) with reth-compatible output, for zkEVM and stateless clients (#​20205 by @​antonis19, #​21629 by @​awskii).
  • More aggressive history pruning by default. --prune.mode=full now follows the EIP-8252 reorg-retention window (~36 days / 262,144 blocks) — see Breaking Changes.
  • GraphQL API revival. Broad resolver coverage restored — queries, logs, call, sendRawTransaction, estimateGas, gasPrice, storage, and EIP-4844 fields.
Breaking Changes
--prune.mode=full: EIP-8252 retention window replaces pre-merge history-expiry

Full mode now retains state and block data for the last 262,144 blocks (~36.4 days), matching EIP-8252's REORG_RETENTION_WINDOW (#​21342). Previously full mode pruned only pre-merge block data (EIP-4444 history-expiry) and kept the last 100,000 blocks of state history.

What changed:

Before After
State history retention last 100,000 blocks last 262,144 blocks
Block data retention pre-merge pruned, all post-merge kept (EIP-4444) last 262,144 blocks

Migration: existing datadirs upgrade automatically and silently. To keep the old "retain all post-merge block data" behavior, set --prune.distance.blocks=18446744073709551615.

Note: physical deletion of frozen snapshot files is not implemented yet (see #​21306), so existing on-disk historical blocks persist for now, though the new cutoff is already recorded at the config level.

In practice, this means only freshly synced full nodes will have a reduced disk footprint.

--prune.mode=blocks: state history retention bumped to 262,144 blocks

--prune.mode=blocks keeps the same shape as before (all block data retained), but its state history retention also bumps from 100,000 to 262,144 blocks. --prune.mode=minimal is unchanged — both block and state history retain the 100,000-block window, deliberately sub-EIP-8252 for disk-constrained operators. See #​21342 for details.

Single p2p listener: --p2p.allowed-ports removed, all eth versions multiplex on --port

Erigon now opens a single TCP listener on --port (default 30303) carrying every configured eth protocol version, instead of one listener per protocol on 30303/30304/30305. This fixes a discovery-DHT race that left inbound peers stuck at a fraction of --maxpeers for multi-protocol deployments: per-protocol ENRs collided under one Node ID, so only one survived in the DHT and peers dialed the wrong listener (#​21335).

What changed:

Aspect Before After
Inbound peer ports 30303, 30304, 30305, … (one per eth version) 30303 only
--p2p.allowed-ports flag Picked one port per protocol from this list Removed — passing it now errors
--maxpeers semantics Per-protocol cap; actual ceiling ≈ N × maxpeers Honest total cap
Default --maxpeers 32 64 (compensates for the now-honest cap)
Enode database directory <datadir>/nodes/eth68, <datadir>/nodes/eth69, … <datadir>/nodes/eth

Migration:

  • Remove --p2p.allowed-ports=... from CLI args / config files; it is no longer recognised.
  • Firewall, Kubernetes Service, and monitoring rules that explicitly opened 30304/30305 can drop those entries — only --port is bound now.
  • If you previously lowered --maxpeers because you knew the per-protocol multiplication inflated the real ceiling, raise it back to the target total (the cap is now what the flag says).
  • First run after upgrade loses the warm peer cache in nodes/eth{68,69,…} — nothing on disk is deleted, the directories are simply no longer read; discovery rebuilds the peer set from bootnodes within a few minutes.

Standalone sentry binary (cmd/sentry) and --sentry.api.addr (remote sentry over gRPC) are unaffected — neither had the bug.

debug_trace* RPC: enableMemory / enableReturnData replace disableMemory / disableReturnData

Aligns Erigon with the execution-apis specification (ethereum/execution-apis#762) and Geth behavior.

What changed:

Field Before (Erigon) After (Erigon / Geth / Spec)
Memory in trace disableMemory (default: included) enableMemory (default: excluded)
Return data in trace disableReturnData (default: included) enableReturnData (default: excluded)

Both the key and its default changed: disable* → enable*, and memory and return data are now excluded unless explicitly enabled — matching the spec and Geth.

Migration: memory and return data are now excluded by default. To include them, add the new opt-in key (omit it to keep the default):

  • Memory: { "enableMemory": true }
  • Return data: { "enableReturnData": true }

Affected RPC methods: debug_traceTransaction, debug_traceBlockByHash, debug_traceBlockByNumber, debug_traceCall.

Clique PoA consensus engine removed

The legacy Clique proof-of-authority engine has been removed (#​20532 by @​yperbasis). --chain=dev now runs on an embedded proof-of-stake consensus instead of Clique (#​20451 by @​mh0lt), matching how all live networks operate post-Merge. Networks or tooling that still depended on Clique are no longer supported.

Silkworm integration removed

The optional Silkworm C++ execution-backend integration and its --silkworm.* flags have been removed (#​19662 by @​canepat). Erigon uses its native Go execution engine exclusively.

Glamsterdam (Devnet Support)

3.5.0 adds an initial implementation of Ethereum's next hardfork — Glamsterdam (consensus-layer "Gloas" + execution-layer "Amsterdam") — for devnet testing and validation. It is not scheduled on mainnet or any public testnet, and these code paths are inert on production networks until an activation time is configured.

Added
RPC
CLI & Operations
Changed
RPC
Networking & P2P
  • New eth/70 wire protocol: partial block receipt lists (EIP-7975, #​19755) — by @​yperbasis
  • All eth protocol versions now multiplex on a single TCP listener (see Breaking Changes, #​21335) — by @​lystopad
  • Peer hygiene / DoS hardening: cap and rate-limit inbound NewBlockHashes (#​21557), enforce the 4096-hash limit on NewPooledTransactionHashes (#​20577), drop peers failing blob KZG verification (#​21421), and bound fan-out stream buffers (#​20783) — by @​yperbasis
  • Skip chain-specific bootnodes on genesis-hash mismatch (#​19807); honour an explicitly empty --bootnodes (#​20630) — by @​yperbasis
TxPool
  • Proactive dormancy-based eviction of stale queued transactions (#​19862) — by @​lystopad
  • Transaction parsing migrated onto the shared execution/types transaction types (#​19757); malformed EIP-7702 authorization tuples are now tolerated rather than rejected wholesale (#​20809) — by @​yperbasis
Caplin (Consensus Layer)
  • Unified Engine API client for standalone mode (#​20035) — by @​mh0lt
  • Fork-choice and ENR-stability fixes — recovery from a post-Gloas fork-choice stall and a persistent node key for stable ENR across restarts (#​21228, #​21276) — by @​domiwei
  • Block production: give the EL builder a build window before stopping it, fixing near-empty proposed blocks (~0–2% gas) on otherwise-healthy validators (#​21990) — by @​lystopad
Storage & Performance
Removed
Security

Full Changelog: erigontech/erigon@v3.4.4...v3.5.0

v3.4.4

Compare Source

v3.4.4 is a bugfix release recommended for all users.

Bugfixes

  • execution/stagedsync: prune in-RAM overlay when execution unwind is a no-op (#​21824, #​21847) by @​JkLondon — third fix for the post-reorg gas used mismatch.
  • caplin: serialize uint64 beacon API fields as JSON strings (#​21805) by @​BitWonka - Per the beacon-APIs spec, Uint64/Gwei fields must be serialized as JSON strings. Several Caplin response types were emitting them as JSON numbers, breaking spec-compliant clients. Fixes #​20562.

Full Changelog: erigontech/erigon@v3.4.3...v3.4.4

ethereum/go-ethereum (ethereum/go-ethereum)

v1.17.4: Flexible Polymer Casing (v1.17.4)

Compare Source

This is a maintenance release with accumulated bug fixes and improvements, and is recommended for all users. It also continues the implementation work for the upcoming Amsterdam hardfork.

One thing worth highlighting:

Fork Implementation (Amsterdam)
Geth
RPC

  • eth_baseFee has been added, returning the base fee of the next block (#​34904, #​35023)

  • eth_capabilities has been added, letting clients discover which historical data a node can serve (#​33886)

  • debug_clearTxpool has been added to clear the transaction pool (#​33347, #​35130)

  • State-reading methods (eth_getBalance, eth_getCode, eth_getStorageAt, etc.) now default the block parameter to latest when omitted (#​35100)

  • Fixes for eth_simulateV1: an incorrect "base fee too low" error code and a pre-Shanghai withdrawal regression (#​34951, #​34939)

  • debug_setHead now propagates rewind errors instead of silently ignoring them (#​35001)

  • EIP-7702 transactions with a nil To address are now rejected (#​35094)

  • HTTP RPC responses now always set Content-Length, and a WebSocket handshake status-code bug was fixed (#​35072, #​35111)

  • The client can now configure trace-context propagation via the traceparent header, and response writes are now traced (#​35132, #​35049)

GraphQL
  • GraphQL request bodies are now limited to 5 MiB (#​35034)
  • Log-range queries with begin > 0 and end == 0 are now rejected (#​35032)
  • The Block.raw resolver now returns empty bytes when the block body is missing (#​35027)
Core
  • A global cache for JUMPDEST bitmaps speeds up EVM execution (#​34850)
  • EVM stack operations are now computed in place, avoiding per-operand copies (#​35156)
  • New code-cache hit/miss meters have been added (#​34821)
  • A shutdown race in snapshot generation has been fixed (#​33540)
Engine API & Blobs
  • Engine API JSON encoding for large blob payloads has been optimized, and gzip is disabled on the engine API (#​33969, #​35057)
  • engine_hasBlobs has been added, and engine_getBlobs now counts only actually-available blobs (#​34859, #​35028)
  • A cache for GetBlobs requests reduces engine API latency, and otel tracing has been added to the GetBlobs endpoints (#​35124, #​35026)
  • Reorged v0 blob sidecar transactions are now dropped rather than converted (#​35099)
  • testing_commitBlockV1 has been added as the write companion to testing_buildBlockV1 (#​34995)
  • New payloads are now imported at genesis regardless of sync status (#​32673)
Networking
  • NAT STUN discovery no longer fails on IPv6 servers (#​35084)
  • Several snap-sync robustness fixes: uncovered state is removed before resuming, a catch-up stall was fixed, sync restarts when the required BAL is unavailable, and the pivot is frozen once state download completes (#​35159)

For a full rundown of the changes please consult the Geth 1.17.4 release milestone.

As with all our previous releases, you can find the:

sigp/lighthouse (sigp/lighthouse)

v8.2.0: Mr. Goldenfold

Compare Source

Summary

⚠️ Lighthouse v8.2.0 is a high-priority release containing fixes for several security vulnerabilities, as well as optimisations and new features.

All beacon node users should upgrade as soon as practical. Validator client users should review the fee-recipient and graffiti changes below before upgrading.

This release also contains substantial Gloas preparation, Fulu data-availability networking improvements, and new standard API support.

Upgrade Notes

  • Mandatory fee recipient: Validator clients now refuse to startup when an enabled validator has no suggested_fee_recipient field in validator_definitions.yml and no global --suggested-fee-recipient fallback is configured. This prevents validator income from being lost accidentally.
  • Validator graffiti: Lighthouse beacon nodes now append client version information to user graffiti by default. To opt-out use the --graffiti-append false flag with Lighthouse VC or set graffiti that is between 30-32 bytes long. There is no change in behaviour if you are already using the --private flag for the beacon node.
  • 💾 Database schema v29: Lighthouse beacon nodes will automatically migrate the database from schema v28 to v29 on startup. A downgrade back to v28 is available prior to the Gloas hard fork, follow the instructions in the Lighthouse Book.

⚠️ Breaking Changes ⚠️

  • Validator fee recipient: Validator clients now refuse to startup when an enabled validator has no suggested_fee_recipient and no global --suggested-fee-recipient fallback is configured. This prevents validator income from being lost accidentally.

💻 Breaking Changes for Devs

  • Mplex will be disabled by default in the next release.
  • Removed non-standard Lighthouse APIs: /lighthouse/analysis/block_rewards, /lighthouse/analysis/attestation_performance/{index}, and /lighthouse/analysis/block_packing_efficiency.
  • Updated /eth/v1/beacon/rewards/* responses to match the beacon API spec wrappers, including execution optimistic/finalized metadata.
  • Pre-Fulu devnet support has been removed.
  • Merge transition support has been removed.

🗑️ Deprecated CLI Flags

The follow CLI flags for the beacon node have been deprecated:

  • --libp2p-addresses is deprecated in favour of --boot-nodes.
  • --reconstruct-historic-states is deprecated in favour of --archive.
  • --proposer-reorg-* flags are deprecated. We do not recommend changing these values.

🧩 Partial Data Columns

Lighthouse now supports partial data columns (EIP-8136). Partial columns reduce the bandwidth used to propagate blob data, utilizing data already present in the EL client. While partial data columns do not require a hard fork, the benefits scale as more of the network upgrades.

For now, Lighthouse only enables partial data columns by default on Hoodi and Sepolia. To opt out, use --enable-partial-columns false.

Notable Changes

  • Added extensive Gloas/ePBS support: payload envelopes, payload bids, payload attestations, PTC duties, proposer preferences, fork-choice changes, gossip verification, lookup/range sync, HTTP APIs, and validator-client duties.
  • Added standard API support for proposer lookahead, v2 proposer duties, payload bids, payload envelopes, PTC duties, proposer preferences, and new SSE topics including execution_payload, execution_payload_gossip, and proposer_preferences.
  • Improved validator-client behaviour for proposer preferences, payload attestation duties, per-validator fee-recipient validation, graffiti defaults, and validator-manager imports.

Update Priority

This table provides priorities for which classes of users should update particular components.

User Class Beacon Node Validator Client
Staking Users High Low
Non-Staking Users High ---

See Update Priorities for more information about this table.

Security Content

This section will be updated with security advisories as they are made public. We are not disclosing the complete security content of this release in order to give users time to upgrade.

  • Fix for a fork choice bug which could cause incorrect justification and finalization: #​9471.
  • Fix for a fork choice bug resulting in #​9364.
  • Fix for a slasher OOM: #​9141.

All Changes

  • Release v8.2.0
  • Update deps
  • Add proposer preferences SSE event (#​9308)
  • Fix race condition between validator duties service and proposer preferences (#​9309)
  • Fix and improve handling of empty columns after getBlobs response (#​9361)
  • Enable late re-org and re-org interactive tests (#​9405)
  • Update DB docs for v8.2.0/schema v29 (#​9489)
  • Refactor payload attestation service (#​9492)
  • Correct unrealized justification for blocks with slashings (#​9471)
  • Gloas attestation payload reprocess (#​9440)
  • SSZ fallback to JSON in proposer_preferences (#​9475)
  • fix(http_api): ignore committee_index in attestation data endpoint (#​9437)
  • Remove --disable-partial-columns in favour of bool argument to --enable... (#​9478)
  • Make single block lookup respect earliest_available_slot for column requests (#​9447)
  • Use hashlink over lru for LruCache (#​8911)
  • Enable mplex by default and change --enable-mplex to take bool (#​9476)
  • Gloas alpha spec 9 (#​9393)
  • Append client version info to user graffiti by default (#​9313)
  • Allow release branches to target stable in target-branch-check (#​9457)
  • deprecate disallowed-offsets config for re-orgs (#​9449)
  • Only bake warpbuild snapshot from stable (#​9462)
  • Bump discv5 (#​9394)
  • Update warp snapshot build job (#​9459)
  • Better partial diagnosics (#​9436)
  • Gloas range sync (#​9362)
  • Refactor payload_attestation_service and add payload attestation test to validator client (#​9357)
  • Gloas lookup sync (#​9155)
  • Fix sending partials from immediately complete columns (#​9433)
  • Simplify lookup sync da_checker oracle (#​9428)
  • Optimise slow block verification tests (#​9274)
  • fix(network): clear ENR nfd field when no next fork is scheduled during runtime transitions (#​9131)
  • Update gloas api routes to match updated spec (#​9418)
  • Update libp2p (#​9331)
  • Improve error types for envelopes (#​9414)
  • Fix O(n²) find_head and stack overflow in filter_block_tree (#​9090)
  • Ensure PTC votes accurately reflect data availability (#​9412)
  • Remove unused spec field from AvailableBlock (#​9411)
  • Reject importing Gloas block until parent's payload is imported (#​9382)
  • Regression test for range sync CGC race condition (#​8039)
  • Gloas data column reprocess queue (#​9339)
  • Remove RequestState trait from lookup sync (#​9391)
  • Disable Mplex by default (#​9365)
  • Delete unnecessary SyncMessage variants (#​9379)
  • Move BlockProcessingResult match out of block lookups (#​9327)
  • Deprecate blob lookup sync (#​9383)
  • Add POST beacon/bid endpoint (#​9347)
  • Make proposer_score_boost non-optional in ChainSpec (#​9386)
  • Use correct slot in custody request (#​9380)
  • Delete bogus InvalidBestNode error (#​9364)
  • Deprecate gossip blobs (#​9126)
  • Rust 1.96 lints (#​9368)
  • Add gossip validation spec tests for proposer/attester slashings (#​9323)
  • Ensure we can serve blocks and columns after head event is emitted (#​9338)
  • Fix non-canonical payload attestation processing (#​9305)
  • Deprecate some reorg-related CLI flags and read from spec (#​9177)
  • Enable partial data columns by default on Hoodi and Sepolia (#​9343)
  • Add macro to simplify into_full_block implementations (#​9294)
  • Add support for jemalloc memory profiling (#​9326)
  • Gloas dont enforce peer column custody on block import (#​9341)
  • Custody backfill sync only penalize peers once per batch (#​9340)
  • Ensure we use the right fork when calculating payload attestation sig domain (#​9342)
  • Gloas alpha spec 8 (#​9315)
  • Add getBlobsV3 to LIGHTHOUSE_CAPABILITIES (#​9330)
  • Drop unused EthSpec generic from Stores (#​9281)
  • Partial columns cleanup (#​9321)
  • Gloas lookup sync boilerplate (#​9322)
  • Use dedicated cache for HTTP API route (#​9318)
  • Remove outdated SPRP hint (#​9312)
  • Gloas payload cache (#​9209)
  • ignore-ws-check flag doesnt allow the node to start outside the weak subjectivity period (#​9290)
  • Fix stale beacon_state_root in test helpers (#​9289)
  • Dont penalize payload envelope peers after gossip verification (#​9283)
  • chore: remove builder_index from produce_block_v4 (#​9267)
  • Fix execution integration test CI failure (#​9277)
  • Implement beacon_blocks_by_head (#​9237)
  • Generalise reconstruct_historic_states for ranged replay (#​9222)
  • Remove TestRandom (#​9006)
  • Remove libssl dependency for cargo udeps (#​9263)
  • fix: payload_attestation_data when no block received for slot (#​9225)
  • Implement gloas proposer preference vc duty (#​9208)
  • Unblock CI by temporarily ignoring hickory-proto audit failures (#​9257)
  • fix: prevent duplicate column reconstruction dispatch (#​9250)
  • Avoid 0x00 block hashes in fcU (#​9233)
  • Update CI: warp runnner to use snapshot and use warm (#​9217)
  • Gloas proposer preferences alpha 7 (#​9239)
  • Gloas HTTP API tests passing (#​9154)
  • Submit ptc votes that we produce to the ptc op pool (#​9231)
  • Remove test_logger feature (#​9125)
  • Import execution payload envelope locally during HTTP API publication (#​9226)
  • Update proposer boost calculation (#​9215)
  • Add Gloas bid inclusion (#​9221)
  • Spec v1.7.0-alpha.6 and Gloas genesis (#​9190)
  • Gossip reprocessed payload envelopes that are timely (#​9210)
  • Gloas publish data columns during local block building (#​9182)
  • Gloas filter conflicting voluntary exits (#​9183)
  • Add payload attestation to op pool and pack into block (#​9180)
  • Fix validator manager compilation (#​9187)
  • Wire up ePBS SSE events and fix envelope availability (#​9199)
  • Fix spurious re-org logs on ePBS payload status changes (#​9191)
  • Add method to Hash256 to display shortened hashes (#​9118)
  • Add payload attestation validator duty (#​9178)
  • Gloas PayloadAttestation gossip verification (#​9145)
  • Gloas ptc duties beacon node response (#​8415)
  • Gloas set AttestationData.index (#​9100)
  • Fix builder exit signature batch verification logic and small refactor (#​9173)
  • Re-issue ForkchoiceUpdate based on updated PayloadStatus (#​9102)
  • Cell Dissemination (Partial messages) (#​8314)
  • Avoid lint and fmt for agents (#​9166)
  • Ensure payload envelope streamer always serves canonical envelopes after the split slot (#​9085)
  • At the fork transition ensure we build ontop of the correct parent block hash (#​9160)
  • Fix audit failure for rustls-webpki (#​9161)
  • Remove more mentions of "pending"/"full" states (#​9156)
  • Gloas engine api updates (#​9150)
  • Revert Gloas API changes from 9092 (#​9151)
  • Gloas spec v1.7.0-alpha.5 and beacon_chain tests (#​8998)
  • Fix slasher OOM (#​9141)
  • Fix total_effective_balance=0 in PreEpochCache (#​9106)
  • Gloas - add get_payload_attestation_endpoint (#​8497)
  • Rust 1.95 lints (#​9142)
  • Gloas vc ptc duty (#​8338)
  • Add mixed V17/V29 execution payload invalidation test (#​9089)
  • Prefix VC root spans with lh_ so they get exported to tracing backend (#​9129)
  • Bump rustls-webpki to unblock CI (#​9130)
  • Gloas: envelope peer penalties and REJECT/IGNORE mapping (#​8981)
  • Gloas bid and preference verification (#​9036)
  • Add missing beacon API config/spec values (#​9112)
  • Truncated Display impl for ExecutionBlockHash (#​9108)
  • Refactor timestamp_now (#​9094)
  • Fix graffiti calculator test mock commit fallback (#​9087)
  • feat(execution_layer): log more detail when JWT auth fails (#​9051)
  • added check for fee recipient per validator and added unit tests (#​8454)
  • Reduce slow test runtimes to under 60s (#​9012)
  • Allow --validator-dir to be specified after subcommands (#​8329)
  • Gloas serve post block state for finalized/justified state requests (#​9092)
  • Add cargo-hack to CI to check crate features (#​8927)
  • Remove unused exit-future (#​9095)
  • Use spec constants for PTC thresholds in fork choice (#​9088)
  • Add test for protocol registration completeness (#​8920)
  • Gloas fork choice redux (#​9025)
  • Automatically pass spans into blocking handles (#​8158)
  • Update blob_delay_ms to track data columns seen (#​9024)
  • Emit SSE: execution_payload (#​9065)
  • Emit SSE: execution_payload_gossip (#​9063)
  • Never use MIN_EPOCHS_FOR_DATA_COLUMN_SIDECARS_REQUESTS for networks that started with Fulu enabled (#​8731)
  • Gloas get payload envelope beacon API (#​9038)
  • Add Gloas SSE event boilerplate (#​9053)
  • Update to spec v1.7.0-alpha.4 (#​9046)
  • Add range sync tests ([#​8989](https://redirect.github.com/sigp/li

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 6am on monday"
  • 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR has been generated by Mend Renovate.

@github-actions github-actions Bot force-pushed the renovate/ethereum-clients branch 2 times, most recently from acc1737 to e9b21d3 Compare June 22, 2026 12:07
@github-actions github-actions Bot force-pushed the renovate/ethereum-clients branch from e9b21d3 to 2f66e99 Compare June 26, 2026 12:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

renovate/ethereum-clients

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants