Welcome to our weekly digest, where we unpack the latest in account and chain abstraction, and the broader infrastructure shaping Ethereum.

This week: Ethereum explores verifiable routing for agent-generated state, new ZK designs upgrade wallets without key exposure, Glamsterdam scaling targets solidify, and the 7702 Collective launches to highlight infrastructure-driven adoption.

• Soldøgn Interop Locks In Key Glamsterdam Targets
• New EIP-7702-Based Proposal Uses ZK Proofs to Hide Wallet Public Keys
• New Ethereum Proposal Targets Verifiable Routing for Agent Solver Outputs
• Introducing the 7702 Collective and Its New Industry Report

Please fasten your belts!

Soldøgn Interop Locks In Key Glamsterdam Targets

Ethereum core contributors used the Soldøgn Interop gathering in Svalbard to align on major technical targets for the Glamsterdam upgrade, including a post-upgrade gas limit floor of 200 million, stable ePBS implementations with external builders, and final EIP-8037 repricing numbers. The week brought together more than 100 contributors for a single-track working session focused on turning Glamsterdam’s scaling and hardening goals into production-ready progress.

A large share of the work centered on ePBS, where teams moved from early instability to a multi-client devnet running with external builders by the end of the week. Contributors simplified parts of the Builder API, debugged cross-client edge cases, and tested the full external builder pipeline end-to-end. Two issues remain open for further All Core Devs discussion: whether request signatures should commit to the receiving builder, and how a low-stake builder design can remain resilient against Sybil-based liveness attacks.

On the execution layer side, teams worked in parallel on Block-Level Access Lists (BALs) and gas repricings. BAL benchmark work focused on lifting worst-case performance paths across clients rather than optimizing only the fastest implementations. For EIP-8037, contributors dropped dynamic per-state-byte pricing in favor of a fixed cost model, then iterated through several accounting designs before stabilizing the spec on bal-devnet-6. The combined outcome of ePBS, BAL optimization, and repricing work formed the basis for the 200M gas-limit target.

The interop also pushed forward non-headliner Glamsterdam items, while opening space for deeper Hegotá work on FOCIL and Native Account Abstraction. The broader significance is that Glamsterdam is no longer just about isolated feature work: contributors are now treating execution time, state growth, block construction, and gas accounting as one connected scaling problem.

New EIP-7702-Based Proposal Uses ZK Proofs to Hide Wallet Public Keys

A new Ethereum Research post proposes a way to upgrade any existing Ethereum wallet to post-quantum-style protection in a single transaction using EIP-7702 delegation, zero-knowledge proofs, and a hidden public key. The design keeps the same address, avoids asset migration, and does not require consensus changes. Instead of moving funds to a new post-quantum wallet, an EOA delegates execution to a GatedWallet contract that only accepts ZK proofs showing knowledge of an ECDSA key whose public key never appears on-chain.

The post argues that this matters because any EOA that has already transacted once has exposed its secp256k1 public key on-chain, which would make it vulnerable to Shor-based key extraction by a cryptographically relevant quantum computer. In the proposed construction, the user generates a new hidden keypair off-chain and stores only a hash of that public key in the contract.

The author presents this as a faster migration path for existing wallets, especially institutional setups that still depend on HSMs or MPC systems built around ECDSA. Rather than replacing ECDSA immediately, the approach wraps it inside a proof layer, allowing the lower wallet infrastructure to stay unchanged while shielding the public key from mempool and on-chain exposure.

The post also outlines a hybrid transition mode where both a normal exposed-key signature and a hidden-key ZK proof are required, giving protection against both quantum key extraction and potential proof-system bugs during early deployment.

Benchmarks in the post show a working implementation with roughly 87 ms proving time, 65 ms verification time, a 226 KB proof, and about 3 million gas on-chain in the current form, with further reductions expected from a designated-prover optimization.

New Ethereum Proposal Targets Verifiable Routing for Agent Solver Outputs

A new draft proposal, Autonomous State Gateway (ASG), argues that Ethereum’s agent stack still lacks a standardized way to route valuable off-chain work into a verifiable, settlement-ready on-chain state. While recent agent-related ERCs have focused on identity, authorization, escrow, and conditional settlement, ASG is positioned earlier in the flow: it standardizes how an off-chain solver’s output is committed, collateralized, verified, disputed, and finally settled.

The draft treats every off-chain result as a Proposed State Transition. Instead of each marketplace or agent system inventing its own custom verifier gateway, ASG suggests a shared routing pattern: off-chain result → collateralized commitment → verifier attestation → dispute window → settlement.

The proposal is designed to be domain-neutral, meaning the same gateway logic could support code patches, vulnerability proofs, model-context changes, dataset transformations, or trading strategy updates.

Architecturally, the draft separates ASG Core from ASG Profiles. The Core defines the common state machine and economic rules, including commitment matching, collateral reservation, verifier attestation requirements, priority for the earliest valid commitment, and terminal settlement or slashing. Profiles then define how a specific domain interprets the submitted state_root, such as a repository patch hash, transformed dataset root, or strategy-state hash.

The proposed flow starts with a solver committing a salted hash of the result and reserving collateral. After ordering is anchored, the solver reveals the state root and evidence, the gateway routes it to a verifier, a dispute window opens, and the transition is either settled or slashed.

Introducing the 7702 Collective and Its New Industry Report

Particle Network announced the launch of the 7702 Collective, a new coalition positioned around highlighting the infrastructure trends driving crypto adoption and ecosystem consolidation. As its first initiative, the group released The State of Crypto Innovation, which it describes as a builders-first assessment of the industry’s maturing infrastructure.

The Collective is intended to shift attention away from short-lived narratives and toward the structural developments that are shaping the next phase of Web3. The report gathers input from builders across the industry and focuses on what they believe is pushing crypto to the next level.

The 7702 Collective is powered by Particle Network, LI.FI, Openfort, Avail, ZeroDev, Etherspot, Magic Labs and Rhinestone, while the report also includes contributions from industry participants such as Centrifuge, Avalanche and Noble. This gives the initiative a multi-project foundation rather than positioning it as a single-company campaign.

The announcement also makes clear that the Collective is designed as an open industry effort. Teams interested in participating can apply through the same website hosting the report, suggesting that the group intends to expand beyond its founding contributors over time.

---

Start exploring Account Abstraction with Etherspot!

• Learn more about account abstraction here.
• Head to our docs and read all about Etherspot Modular SDK.
• Skandha — developer-friendly Typescript ERC4337 Bundler.
• Arka — an open-source Paymaster Service for gasless & sponsored transactions.
• Explore our TransactionKit, a React library for fast & simple Web3 development.
• Follow us on X (Twitter) and join our Discord.

❓Is your dApp ready for Account Abstraction? Check it out here: https://eip1271.io/

Follow us

Etherspot Website | X | Discord | Telegram | Github | Developer Portal