Welcome to our weekly digest, where we unpack the latest in account and chain abstraction and the broader infrastructure shaping Ethereum.
This week: Frame Transactions cross a real testing milestone as two supporting proposals advance toward Hegotá; a new ERC defines a portable spend grant for agents and session keys; Safe makes v1.5.0 the default, adding module guards and stricter signature checks; and Arbitrum replaces Timeboost with priority gas auctions.
- Frame Transactions Clear a Testnet Milestone
- ERC-8427 Defines Portable Spend Grants
- Safe Makes Contracts v1.5.0 the Default
- Arbitrum Launches Priority Gas Auctions
Please fasten your belts!
Frame Transactions Clear a Testnet Milestone
Native account abstraction moved from spec to running code this week. At the fifth Frame Transaction Breakout call, the ethrex team reported that the EIP-8141 frames testnet has been live for 14 days, with three independent clients now validating the network: ethrex, Geth, and Nethermind.
The activity numbers are small but meaningful for a brand-new transaction type. Nearly 400 frame transactions have been sent from 21 distinct senders, the clients are passing all spec tests, and the team says it is ready to move to an interop devnet.
Tooling is catching up alongside the protocol. The Viem team flagged that JSON-RPC support for frames still needs gas estimation and simulation endpoints, and ethrex has proposed a standard way to simulate frame transactions so wallets and apps can build against them.
Two supporting proposals also advanced. At All Core Developers Execution call #246, EIP-8250 (Keyed Nonces) and EIP-8272 (Recent Roots) both moved to Considered for Inclusion for Hegotá. Both underpin the shared-sender privacy use cases we covered last week, since keyed nonces let many users transact through one sender and recent roots bound how validation is checked.
ERC-8427 Defines Portable Spend Grants
A new draft, ERC-8427, tackles a permission that anyone building with agents or session keys has needed: letting a key spend up to a set amount of specific assets for a while, with the ability to revoke it. The author notes that ERC-20 approve does not fit, since it usually covers one token with no expiry and no time window.
The design centers on one signed object called a SpendGrant. The principal signs who may act, which assets, per-call, rolling-window, and lifetime caps for each asset, who may receive funds, and a validity range, all in a single signature that can be revoked once.
A detail that matters is how the window works. The cap looks back over a true trailing period, so a 24-hour cap is not a calendar day that resets at midnight, closing the loophole where a delegate spends the full cap at 11:59 and again at 12:01.
It is built to slot into the existing stack. The draft relates to ERC-7710 and ERC-7715 for delegation and permission requests and to ERC-8312 for tracking remaining usage, and it is tagged for AI agents, which is exactly the setting where bounded, revocable spending authority is becoming essential.
Safe Makes Contracts v1.5.0 the Default
Safe made contracts v1.5.0 the default for new Safes in Safe{Wallet}, and existing Safes on 1.3.0 or 1.4.1 can upgrade from settings in a single transaction. The team recommends upgrading now, since new security features will build on this version.
The security upgrades are the headline for smart account users. Failed transactions now return the underlying error instead of a generic revert, signature validation moves to current ERC-1271, and a new Module Guard checks every module transaction against the same rules as your other transactions, so modules can no longer bypass guards.
That module change closes a real gap. Guards previously governed ordinary transactions but not module-initiated ones, and bringing modules under the same checks tightens a common source of smart-account risk.
There is one compatibility caveat worth flagging. Version 1.5.0 checks contract signatures more strictly, so a Safe owned by another smart contract needs that contract to implement isValidSignature in the exact ERC-1271 format, and owners should confirm this before upgrading if that signer is needed to reach their threshold.
Arbitrum Launches Priority Gas Auctions
Arbitrum activated Priority Gas Auctions and Fast Feed on Arbitrum One, replacing its Timeboost ordering policy with a standard priority-fee system for transaction ordering. Users and applications now compete for earlier execution by attaching a priority fee to individual transactions using standard EIP-1559 fee fields.
The mechanics are built for speed. Each 250-millisecond block contains two 125-millisecond PGA rounds, and transactions are ordered by priority fee within each round, with the resulting priority-fee revenue flowing to the ArbitrumDAO treasury.
Fast Feed is the companion piece. It is a paid data stream that gives subscribers ordered sequencer data in real time during block construction rather than after the block completes, aimed at searchers and latency-sensitive applications, though it does not affect ordering itself.
For our readers, the move is a useful signal. As L2s tune their fee and ordering markets toward standard EIP-1559 mechanics, the way transactions get priced and sequenced across chains grows more consistent, which is the substrate that account and chain abstraction ultimately have to route over.
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)