ERC-4337 Hits Final, Starknet Brings Private DeFi, Ethereum’s Privacy Week, Atomic Cross-Domain Proofs, RLUSD Goes Multichain

By Pillar | Etherspot | 1 hour ago


Welcome to our weekly digest, where we unpack the latest in account and chain abstraction, and the broader infrastructure shaping Ethereum.

This week: ERC-4337 reaches Final status; Starknet brings private DeFi to mainstream wallets through its STRK20 framework; a wave of privacy proposals turns the past week into an AA “privacy week,” led by the pERC20 token standard; researchers publish machine-checked proofs for atomic cross-domain state sync; and Ripple spreads RLUSD across 40+ chains via Wormhole.

  • ERC-4337 Reaches Final
  • Private DeFi Comes to Starknet with STRK20
  • pERC20 Proposes a Privacy-Native Token Standard
  • Mechanized Proofs for Atomic Cross-Domain State Sync
  • Ripple Brings RLUSD to 40+ Chains via Wormhole

Please fasten your belts!

ERC-4337 Reaches Final

ERC-4337, the standard that brought account abstraction to Ethereum without any consensus-layer changes, has moved to Final status. The change landed as a GitHub commit from co-author Yoav Weiss, merged by the EIP-Bot, flipping the spec from “Last Call” (deadline May 26) to “Final.”

Final status means the specification is now considered stable and complete. The EntryPoint contract, UserOperation flow, bundlers, and paymasters that the entire AA ecosystem builds on are locked in as a finished standard.

Authored by Vitalik Buterin, Yoav Weiss, Dror Tirosh, Shahaf Nacson, Alex Forshtat, Kristof Gazso and Tjaden Hess, and first created back in September 2021, it’s a quiet milestone for a standard that reshaped how the ecosystem thinks about Ethereum wallets.

b6f2baa0c5bb9df33250c20a290b0c5c4809d3a615671e589456be8c56888040.jpg

Private DeFi Comes to Starknet with STRK20

Starknet laid out how private DeFi is coming to its ecosystem through STRK20, its privacy framework for ERC-20 assets. The pitch: shielded balances, private transfers, and private app flows that live inside the wallets and apps people already use, rather than forcing users into a separate privacy app with isolated liquidity.

Users can shield assets directly from supported wallets like Ready X and Xverse, then swap, lend, or stake while keeping balances private. An anonymizing contract does the heavy lifting — for a shielded USDC → ETH swap, it unshields into the contract, routes the trade through existing Starknet liquidity (via avnu and Ekubo), and returns a fresh private note, all in one atomic transaction.

The first phase covers in-wallet shielding and swaps, with private lending (Vesu), staking (Endur), and vault strategies to follow. Amounts moving through public liquidity stay visible, and anonymity depends on the size of the privacy set, but the design breaks the direct public link between a user’s wallet and their DeFi activity. Each private transaction carries a flat 4 STRK fee.

pERC20 Proposes a Privacy-Native Token Standard

The past week turned into something of a “privacy week” across the AA ecosystem, with several proposals landing at once. Chief among them: EIP-8287 (pERC20), a draft standard for privacy-native fungible tokens on the EVM.

Unlike shielded-wrapper approaches, pERC20 tokens are private from issuance; there’s no public balanceOf, no approve/allowance, and no public-to-shielded conversion step. Balances and transfer amounts live as encrypted UTXO notes (an Orchard-style ZK model), while totalSupply stays public so there’s no invisible inflation. A compliance “frozen root” lets specific notes be blacklisted to satisfy regulatory requirements.

The proposal is complementary to EIP-8182’s private transfer layer, and it sparked immediate debate: reviewers on Ethereum Research argued its Groth16 proof system isn’t quantum-safe and pushed for an FRI/PLONK-based approach — a reminder that privacy and post-quantum concerns are increasingly being designed together.

Mechanized Proofs for Atomic Cross-Domain State Sync

A new Ethereum Research post tackles a problem every multi-chain and L2 designer quietly depends on but rarely states formally: when an asset exists on several domains at once, how do you guarantee that a state change on one takes effect on the others, simultaneously or not at all?

The author formalizes “atomic cross-domain state synchronization” and proves both safety (the resulting state is consistent across every connected domain) and liveness (synchronization actually completes under Byzantine faults, f < n/3) in Isabelle/HOL — a 3,215-line machine-checked artifact with zero gaps. The model is built from seven reusable “locales” covering message priority, deadlock-free locking, and fair leader rotation, among others.

The framing is grounded in real regulatory pressure, as FATF’s Travel Rule and BIS-IOSCO settlement-finality standards both effectively require that an effect (a freeze, a liquidation) hit all domains at once. For AA and chain-abstraction builders, it’s a rigorous look at what “atomic composition across rollups” actually demands.

49d45a6eba25d9982953f7077cde39d60ca4279960e4b51d341638ddfc2cce97.jpg

Ripple Brings RLUSD to 40+ Chains via Wormhole

Ripple has expanded its RLUSD stablecoin to more than 40 blockchain networks through Wormhole’s Native Token Transfers (NTT) framework, letting the token move natively between chains without relying on wrapped versions.

The rollout brings RLUSD to Ethereum L2s including Base, Optimism, Ink, and Unichain, plus the XRP Ledger EVM sidechain. Now around $1.7 billion in market cap and the 8th-largest stablecoin, RLUSD is being positioned as compliant, USD-backed liquidity for cross-border payments, institutional on/off-ramps, and tokenized real-world assets.

For chain-abstraction builders, more native (non-wrapped) stablecoin liquidity spread across more chains is exactly the kind of substrate that intent-based and cross-chain UX runs on.


 

🛠️ 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

👉 Learn more


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

TransactionKit | Pillar Wallet | Case Studies 

 

How do you rate this article?

4


Pillar
Pillar

A community-run, multichain & non-custodial DeFi wallet with one address, low-to-no gas fees and cross-chain super powers!


Etherspot
Etherspot

All-in-one Account Abstraction development platform. Get your dApp ready for mass adoption via slick UI in 2 lines of code. Build now with TransactionKit.com

Send a $0.01 microtip in crypto to the author, and earn yourself as you read!

20% to author / 80% to me.
We pay the tips from our rewards pool.