Welcome to our weekly digest, where we unpack the latest in account and chain abstraction and the broader infrastructure shaping Ethereum.
The latest news we’ll cover:
- EIP-7702 Draws Scrutiny After the Binance Hack
- Ephemeral Rollups Propose an L1.5 Model
- ERC-8478 Ties Agent Payments to Identity
- Stellar Connects to Ethereum Through VIA Labs
Please fasten your belts!
EIP-7702 Draws Scrutiny After the Binance Hack
Security firm Blockaid says EIP-7702 did not cause the $6.3 billion Binance hack, the largest in crypto history, but may have amplified the losses. CEO Ido Ben-Natan told Cointelegraph that attackers could have drained the wallets without 7702, but that the upgrade offered a way to do it in one sweep and possibly bypass some of the exchange’s checks.
The root cause points elsewhere. Binance found no evidence that private keys leaked, and Blockaid believes attackers reached the wallet-signing infrastructure through a compromised developer machine, so the signer ultimately approved a transaction it should not have.
Ambire’s Ivo Georgiev downplayed 7702’s role, since the attackers already had the ability to authorize transactions. He warned, though, that engineers who regain control of their systems might overlook the need to revoke a malicious 7702 delegation, calling it a problem that is still very poorly understood.
For our audience, that is the lesson worth keeping. Delegation is one of account abstraction’s most powerful features, and this episode is a reminder that revoking and auditing delegations has to be a first-class part of any smart-account security model, not an afterthought.
Ephemeral Rollups Propose an L1.5 Model
A new Ethereum Research post proposes a pattern its author calls L1.5, where the wallet keeps the user’s own state, L1 keeps the shared state and verifies every transition, and a stateless worker in between does the computation. Unlike an L2, nothing holds user state, so there is no rollup to exit from.
Native account abstraction is what makes it practical. Under EIP-8141, an application contract can check a proof in its own VERIFY frame and pay the fee from the funds it moves, so no sequencer or relayer has to submit the transition or hold ETH for it.
Two more proposals complete the picture. EIP-8250 keyed nonces, derived from a privacy nullifier, let the chain reject a double spend the way it rejects a reused nonce, and EIP-8288 lets each mempool node check a proof once while the block carries a single recursive STARK for all of them.
The post is concrete rather than purely theoretical. It walks through a privacy-pool redemption run on the Hegotá test network as a list of frames, where L1 checks the proof before any funds move, and sketches applications like gasless private payments and a stealth privacy pool built on the same primitives.
ERC-8478 Ties Agent Payments to Identity
A new draft, ERC-8478, addresses a gap in agent-to-agent payments. When one agent pays another over the x402 protocol, the destination address comes from an HTTP response, and nothing ties it to the paid agent’s ERC-8004 on-chain identity, so whoever controls that response, through a hijacked domain or an injected tool result, can redirect the money.
The measured scale of the gap is striking. On Robinhood Chain, of 5,575 registered ERC-8004 agents that answer with an x402 payment requirement, only five have a payout address matching their own registered agent wallet.
The fix uses an anchor ERC-8004 already provides. The draft binds the payout address to the agent’s identity when it equals the registered agent wallet, or when that wallet signed a time-limited EIP-712 delegation for the exact address, asset, and origin, with wallet rotation revoking every delegation.
This is the agent-payments frontier of account abstraction. As autonomous agents begin paying each other, verifying who actually controls the receiving account becomes as fundamental as the spend limits and session keys we have covered, and this draft makes that check a standard step before money moves.
Stellar Connects to Ethereum Through VIA Labs
VIA Labs launched bidirectional cross-chain messaging between Stellar’s Soroban smart-contract platform and Ethereum mainnet, as reported during Stellar’s Meridian conference. Applications can initiate instructions on one chain and have a contract execute the corresponding action on the other, aimed at stablecoin transfers and tokenized real-world assets.
The reference flow is a familiar burn-and-mint. VIA’s validators monitor the originating gateway and sign the message, a relayer submits it to the destination gateway, which checks the signatures before minting, and the company puts completion at roughly one to three minutes.
The protocol requires messages to originate from contracts, not directly from ordinary wallet accounts, so developers integrate the gateway through their applications while users interact with a token or service contract.
The launch fits a wider pattern we track. Cross-chain messaging keeps consolidating around contract-mediated routes rather than manual bridging, which is the substrate that chain abstraction depends on, and it arrived alongside Securitize and DTCC tokenization plans on Stellar.
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
Top comments (0)