Welcome to our weekly digest, where we unpack the latest in account and chain abstraction and the broader infrastructure shaping Ethereum.
This week: Ethereum commits EIP-8141 Frame Transactions to its next major upgrade so users can transact without holding ETH; Vitalik pushes EIP-8288 to cut the cost of quantum-safe private transactions by more than 99%; EIP-8130 and Frames collaboration breaks down, sending Base and Ethereum down separate native AA paths; Matter Labs open-sources Prividium’s permissioning engine as the Bundesbank tests it; a16z argues permissionless networks are compatible with financial-integrity laws and leans on account abstraction to make the case.
- Ethereum Commits Frame Transactions to Its Next Upgrade
- Vitalik Pushes EIP-8288 for Cheaper Private Transactions
- Base and Ethereum Split on Native AA
- Matter Labs Open-Sources Prividium as Bundesbank Tests It
- a16z Makes the Case for Permissionless Compliance
Please fasten your belts!
Ethereum Commits Frame Transactions to Its Next Upgrade
Ethereum core developers moved EIP-8141 Frame Transactions to Scheduled for Inclusion at their August 27 call, marking native account abstraction as part of a coming network upgrade rather than just a candidate for one. The feature is slated for Hegotá, the upgrade due in 2027 after Glamsterdam, and Vitalik Buterin, one of the proposal’s ten authors, said a lot of quiet progress on Frames has landed over the past few months.
The core idea is to break a transaction into separate steps. One step checks that the user authorized it, one establishes who is paying the fee, and the rest carry out the instructions, so the account sending funds and the account paying to move them no longer have to be the same.
That split is what lets people transact without holding ETH. A payments app could cover the fee itself, or take stablecoins from the user and settle the ETH bill on their behalf, so Ethereum still gets paid in ether while the user never has to buy any.
Frames also groups steps that only make sense together. Trading a token today often means approving an app to spend it and then submitting the trade, and Frames bundles the two so that if the trade fails, the permission granted alongside it is withdrawn rather than left sitting there.
There is a post-quantum angle too. Frames would let an account define its own rules for approving transactions, so the key controlling it could be swapped for a new one, including a quantum-resistant type, without moving anything to a new address.
Vitalik Pushes EIP-8288 for Cheaper Private Transactions
Vitalik Buterin said he hopes to see EIP-8288, a proposal cutting the cost of quantum-safe private transactions by more than 99%, land in I-star, the upgrade after Hegotá. He co-authored it in June with Thomas Coratger and describes it as the next step after Frames.
The savings come from keeping the heaviest cryptography off-chain. A transaction instead declares a “dependency,” a 96-byte claim that some message was signed by some key or that some data satisfies some proof, and mempool nodes collect those claims every second, generate a single recursive STARK proving all of them at once, and pass it on, so each block carries one proof covering everything in it.
The numbers Vitalik cites are striking. A well-engineered private transaction costs about 300,000 gas today and roughly 10 million if you want it quantum-safe, and under EIP-8288 both would fall to the low tens of thousands.
There is a big architectural decision attached. Recursive proofs need a common language, and the leading candidate is RISC-V, so adopting the proposal would make it Ethereum’s de facto canonical instruction set, a move Vitalik called a “big decision” that should be taken carefully.
For our audience, the account abstraction payoff is direct. One use he sketched is private account abstraction, keeping an account’s logic hidden on-chain and then changing ownership of every position and holding attached to it in a single transaction, without revealing which ones.
Base and Ethereum Split on Native AA
Derek Chiang of Ethlabs reported that the account abstraction collaboration between EIP-8130 and EIP-8141 Frame Transactions has broken down, and that Base and Ethereum are now going separate ways to implement different native AA standards. This reverses the convergence we covered two weeks ago, when a shared transaction type was the preferred outcome.
His explanation is that L1 and L2s now want different things. Ethereum L1 optimizes AA for censorship resistance, privacy, and quantum resistance, pointing toward standards like ERC-4337, EIP-7701, and Frames, while L2s optimize for scale and compliance, pointing toward standards like EIP-8130.
The authors found technical solutions, but each required one side to compromise on a core goal. Ethereum wanted to be the best version of Ethereum and Base the best version of Base, so interoperability lost out and the burden of handling the resulting fragmentation now falls on wallets.
Chiang argues this is not necessarily a bad outcome. Forcing chains to adopt the same approach even when it stops serving their users would be worse, and both chains are now free to innovate on AA in line with their own visions.
He lays out two paths forward for anyone who still wants a consistent cross-chain experience. One is a broader coordination mechanism that gives L2s a real voice in shaping the EVM, and the other is accepting fragmentation and building wallets and apps that speak each chain’s native transaction types while hiding the complexity from users.
Matter Labs Open-Sources Prividium as Bundesbank Tests It
Matter Labs, the developer behind ZKsync, open-sourced the permissioning engine of Prividium, its distributed-ledger platform for financial institutions. Publishing it as open source means institutions can run a permissioned chain from public code in their own environment, inspecting and modifying the core rather than depending on a single vendor.
The setup keeps sensitive data private while proving correctness. Smart contract and token data stay within the operator’s environment, and zero-knowledge proofs verify that everything was processed correctly.
A central bank is the first to try it. Deutsche Bundesbank, Germany’s central bank, is testing and deploying Prividium’s open-source permissioning engine in its own infrastructure, and Matter Labs said it will keep collaborating on the platform’s design and testing.
CEO Alex Gluchowski framed the release as a milestone for the industry, comparing open-sourcing the core to what open weights did for AI by letting serious institutions hold the technology in their own hands. Administration tools and integrations into an institution’s existing systems will remain commercial products, and the move does not change the role of the ZK token.
a16z Makes the Case for Permissionless Compliance
a16z crypto published a paper arguing that financial institutions can build and transact on permissionless networks without running afoul of financial-integrity laws like the Bank Secrecy Act and U.S. sanctions rules. Its core claim is that these laws require risk-based controls at the layer an institution operates, not ownership or screening of the underlying infrastructure.
The authors compare a permissionless network to the internet or the phone network. An institution does not choose the validator that processes its transaction, cannot bargain over the protocol-set fee, and has no way to learn who the validator is, which the paper likens to the neutral, protocol-mediated carriage that already governs email routers and phone switches.
Privacy is where the argument gets closest to our beat. The paper says cryptography has advanced far enough for an institution to prove a compliance-relevant fact, such as a counterparty sitting outside the sanctions list, without publishing the data behind it, using confidential transfers, proofs of provenance, and viewing keys for examiners.
The paper also points to tools already in production, including address rotation and account abstraction, alongside custody structures and messaging protocols that keep client-level details off the public ledger. The broader argument is that institutions may not need permissioned networks to get both compliance and privacy.
🛠️ Builder note: Etherspot
AA infra should make development easier, not harder.
- One RPC endpoint across chains
- Pay-as-you-go pricing on mainnet
- No markup on gas fees
- API key controls with built-in security
Start exploring Account Abstraction with Etherspot!
- Learn more about account abstraction here.
- Head to our docs and read all about Etherspot Prime.
- 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 and join our Discord.
❓Is your dApp ready for Account Abstraction? Check it out here: https://eip1271.io/
Follow us
Website | X | Discord | Telegram | Github | Developer Portal
Powered by Etherspot
