We are welcoming you to our weekly digest! Here, we discuss the latest trends and advancements in account abstraction, chain abstraction and everything related, as well as bring some insights from Etherspot’s kitchen.
The latest news we'll cover:
- Ethereum PQTS Call Positions Native Account Abstraction as Post-Quantum Foundation
- Ethereum Foundation Awards $50K Maximum Bounty for ERC-4337 ‘High-Severity’ Attack Vector
- Rivet Fork Adds EIP-7702 Support, Showcases ‘Build Your Own Wallet’ Use Case
- KuCoin Lists TRIA in Global Premiere, Showcases Chain Abstraction Vision With $34,000 Incentives
Please fasten your belts!
Ethereum PQTS Call Positions Native Account Abstraction as Post-Quantum Foundation
Ethereum’s first Post Quantum Transaction Signature (PQTS) Breakout Room (#1889) centered on one clear conclusion: account abstraction is the architectural foundation for Ethereum’s post-quantum transition.
During the call, contributors emphasized that while the final post-quantum signature algorithm has not been selected, the ecosystem broadly agrees that AA will serve as the base layer enabling whichever scheme is ultimately adopted. Native account abstraction is viewed as the structural anchor that can support cryptographic migration without repeatedly redesigning transaction flows.
Nico, who has worked extensively on account abstraction, outlined the limitations of ERC-4337. While compatible with post-quantum cryptography, 4337 remains non-native, introducing gas overhead, bundler dependencies, and added complexity around entry points and gas management. These constraints are driving momentum toward native AA integration at the protocol level.
The discussion highlighted EIP-8141 (“Frame Transactions”), a proposed new transaction type designed to replace the rigid ECDSA-centric transaction model. Frame Transactions introduce a structured flow with verification, execution, and sender frames. Crucially, signature verification occurs in a read-only verification phase, meaning failed validation does not burn gas. This model allows flexible signature schemes without enshrining any single cryptographic primitive in the protocol.
Participants clarified that EIP-8141 would replace the earlier 7701 proposal. Existing ERC-4337 wallets would continue functioning, but a transitional migration toward native AA is expected over time.
Beyond structural changes, the call strongly emphasized cryptographic agility. Current Ethereum transaction formats hardcode ECDSA assumptions (V, R, S fields), making algorithm replacement costly and disruptive. Contributors argued that Ethereum must support multiple signature schemes simultaneously and allow modular replacement over time. Given the uncertainty of post-quantum cryptography, where schemes may evolve or break, designing for agility is considered critical.
Ethereum Foundation Awards $50K Maximum Bounty for ERC-4337 ‘High-Severity’ Attack Vector
The Ethereum Foundation has awarded a $50,000 bug bounty, its maximum high-severity payout, to Trust Security for identifying a previously undisclosed attack vector affecting ERC-4337, the standard that powers account abstraction. The issue was disclosed on Thursday and has since been patched in the latest release.
According to the foundation, the vulnerability allowed a malicious actor to intentionally cause certain ERC-4337 account-abstraction transactions to revert while still forcing users to pay gas fees, even though the transactions were valid and properly signed. Trust Security described the issue as a censorship and griefing vector rather than a fund-theft exploit.
At the time of discovery, usage of the vulnerable ERC-4337 transaction type was relatively limited. However, around 1.7 million such transactions were sent over the past week, roughly 9% of total Ethereum transactions during that period, underscoring the need to address the issue before wider adoption amplifies potential impact.
The root cause stemmed from a hidden assumption in the ERC-4337 implementation. Developers assumed account abstraction transactions would execute cleanly and in isolation, similar to standard Ethereum transactions. In practice, an attacker could frontrun certain pending account abstraction transactions interacting with protocols that use reentrancy protection or temporary state changes, causing the inner transaction to revert while still consuming gas.
To mitigate the issue, developers introduced changes requiring specific contract functions to be callable only from non-account-abstraction wallets. The Ethereum Foundation urged protocols relying on ERC-4337 to upgrade to the newest release as soon as possible.
In addition to the $50,000 bounty from the foundation, Trust Security reported receiving $59,500 in additional bounties from DeFi applications built on ERC-4337.
Rivet Fork Adds EIP-7702 Support, Showcases ‘Build Your Own Wallet’ Use Case
Dhruv (@0xdhruva) announced a new release of a Rivet fork that integrates support for EIP-7702 and EIP-5792, positioning it as a practical example of how developers can build their own programmable wallet experiences on top of Ethereum’s evolving account abstraction stack.
In his post, Dhruv highlighted several capabilities enabled by the update: native EIP-7702 support, contract interactions that “don’t fight you,” contract deployment, arbitrary calldata submission, and typed data signing. The release is available on GitHub under the tag v0.0.0-nightly.25702ab, with ongoing feature development planned for a utility-focused interface.
EIP-7702 allows externally owned accounts (EOAs) to delegate execution logic to smart contracts, effectively enabling execution abstraction without requiring users to abandon their existing addresses. In practice, this means wallet behavior can be upgraded or customized, including gas abstraction, batching, or alternative signature logic, while preserving user identity and balances.
The Rivet fork demonstrates how 7702 can be used as a foundation for custom wallet infrastructure rather than relying solely on standardized wallet implementations. By combining 7702 delegation with 5792 support (which standardizes wallet request capabilities), the tool provides a sandbox for experimenting with programmable account behavior at the transaction layer.
KuCoin Lists TRIA in Global Premiere, Showcases Chain Abstraction Vision With $34,000 Incentives
KuCoin has officially launched TRIA on its Spot platform on February 3, 2026, marking the project’s global premiere. The exchange is supporting the listing with a combined $34,000 USDT incentive program tied to trading, deposits, and on-chain participation.
The listing highlights TRIA’s positioning at the center of the chain abstraction narrative in 2026. While previous cycles focused on launching new Layer 1 and Layer 2 networks, TRIA targets what it describes as the resulting “fragmentation crisis.” As a self-custodial global neobank and unification layer, TRIA abstracts away blockchain complexity, enabling users to spend, trade, and earn across multiple chains without manually bridging assets or managing gas tokens.
At the infrastructure level, TRIA’s chain abstraction model is powered by its BestPath AVS (Actively Validated Service), an AI-driven intent engine. Rather than forcing users to execute multiple cross-chain steps, users declare their desired outcome, and the BestPath engine routes transactions end-to-end, aiming for optimal pricing and sub-second settlement.
The protocol reports that this technology is already utilized by more than 70 protocols and integrated across ecosystems such as Polygon, Arbitrum, and Injective.
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)