Welcome to our weekly digest, where we unpack the latest in account and chain abstraction and the broader infrastructure shaping Ethereum.
This week: ERC-8421 proposes a reputation-based mempool for Frame Transactions; sig.golf launches a benchmark for smaller post-quantum signatures; EIP-8430 splits Base’s AA transaction type into a standalone proposal; zk.money returns on Aztec; and Gabriel Shapiro makes the case for an Ethereum-wide privacy push.
- ERC-8421 Proposes a Reputation-Based Frames Mempool
- sig.golf Hunts Post-Quantum Signatures
- EIP-8430 Splits Base's AA Transaction Type
- zk.money Returns on Aztec
- The “Enshieldening”: A Push for Privacy Across Ethereum
Please fasten your belts!
ERC-8421 Proposes a Reputation-Based Frames Mempool
Alex Forshtat published ERC-8421, a set of alternative mempool rules for EIP-8141 Frame Transactions that is structured like, and mostly backward compatible with, the ERC-7562 validation rules already used for ERC-4337 UserOperations. It is framed as a more permissive, reputation-based system that sits alongside the stricter canonical mempool defined in the core protocol.
It is a sibling to the MATCHA policy we covered two weeks ago. Both let the mempool safely admit many transactions from one shared sender, which privacy applications need, and the author notes the main difference is the unit of accounting, with ERC-8421 counting transactions seen where MATCHA meters gas used.
The first round of review has already prompted a few changes. A reviewer pointed out that one lifecycle rule did not account for EIP-8250 transactions carrying multiple nonce keys, and that a fixed per-sender pending cap would throttle the exact shared-sender privacy case the design targets.
The author pushed fixes in response. He patched the multi-key rule and updated the text so the per-sender count limit does not apply to staked sender addresses, restoring the intent that staked entities in good standing face no transaction-count cap.
sig.golf Hunts Post-Quantum Signatures
Yukon Research, in collaboration with the Ethereum Foundation, launched sig.golf, a competition to design the post-quantum signatures Ethereum will eventually need. As Yukon’s Zeeshan put it, Ethereum needs post-quantum signatures that stay small and cheap to verify.
The challenge is specific. Participants design stateless hash-based signatures, prove them secure in Lean, and compete to beat the record on size multiplied by verification cycles, the two costs that decide whether a scheme is practical onchain.
Hash-based signatures are an appealing target. They rely on the security of ordinary hash functions rather than newer and less-tested math, which fits Ethereum’s recent preference for conservative, battle-tested cryptography.
Native account abstraction through Frame Transactions is being designed to let accounts adopt new signature schemes, so a smaller and cheaper post-quantum signature is exactly the kind of primitive those accounts would swap in as quantum readiness becomes urgent.
EIP-8430 Splits Base’s AA Transaction Type
A new proposal, EIP-8430, pulls the transaction type out of EIP-8130 into its own standalone EIP with no Keystore dependency. EIP-8130 keeps the Keystore, and neither EIP now requires the other.
The reasoning is modularity. The transaction type is useful on its own, since it works for today’s EOAs with native secp256k1 authentication, so it can ship first while the Keystore follows later through ERC-4337, direct contract calls, or frame transactions.
This follows the Base and Ethereum split we have tracked. Rather than one monolithic standard, Base is breaking native account abstraction into pieces that can ship independently, which mirrors the composable approach proposed earlier and lowers the risk of the whole design stalling on one dependency.
Review is already probing the seams. Contributors raised a replay-identity edge case at the config-change boundary and asked whether EIP-8430 and EIP-8250 should share one nonce manager and one RPC read, so a single key is not split into two separate lanes for the same account.
zk.money Returns on Aztec
Aztec Labs is relaunching zk.money, a self-custodial wallet that hides payment amounts, balances, and recipients by moving funds onto the Aztec Network, while letting people pay by a readable name like bob.zk.money or a payment link. Users deposit DAI, USDC, or USDT from Ethereum, with USDC and USDT converted to DAI on the way in.
The privacy has clear edges. A deposit from Ethereum still reveals the sender and amount, so only activity inside Aztec is hidden, and the original zk.money served more than 75,000 wallets and processed over $100 million before it closed in 2024.
The relaunch is cautious. Each deposit, payment, and withdrawal is capped below $2,500 under a shared daily allowance, users get 100 sponsored transactions a day, and Aztec Labs says the software is an early alpha that has not been fully audited.
For our readers, the sponsored-transaction model is the familiar piece. Covering users’ network fees from a contract so they never hold gas is account abstraction in practice, and it is the same gasless pattern that Ethereum’s Hegotá privacy work aims to make native rather than dependent on outside services.
The “Enshieldening”: A Push for Privacy Across Ethereum
Gabriel Shapiro published a long essay arguing that Ethereum, not single-asset privacy coins, is positioned to lead on financial privacy, and proposing a community-wide month of shielding he calls the Enshieldening. His core claim is that asset-agnostic privacy protocols let any token take a private format without anyone having to buy a dedicated coin first.
He frames Ethereum’s edge as a full stack coming together. RAILGUN and Privacy Pools already shield assets on mainnet, Aztec adds private smart contracts, and the money rarely has to leave the chain to be useful, which keeps a deposit from becoming a chokepoint.
Account abstraction sits at the center of his supply-side case. He points to Hegotá’s Frame Transactions, keyed nonces (EIP-8250), and recent roots (EIP-8272), plus FOCIL, as the rails that let a shielded pool be its own sender and pay its own gas, removing the relayers that privacy pools lean on today.
The wallet side is the other half. He highlights the Ethereum Foundation’s Kohaku tooling, with shielded-by-default balances, one address per application, and a post-quantum ERC-4337 account with a kill switch, as the demand-side counterpart to the protocol changes. For our audience, it is a useful map of how privacy, account abstraction, and post-quantum work are converging into one design.
🛠️ 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
