DEV Community

Cover image for EF’s Fusaka Testnets Schedule, Trust Wallet’s TWT Roadmap to 1B Users, “Beyond Abstraction” Wallet Blockers, and SWIFT Linea
Alexandra for Etherspot

Posted on • Originally published at etherspot.io

EF’s Fusaka Testnets Schedule, Trust Wallet’s TWT Roadmap to 1B Users, “Beyond Abstraction” Wallet Blockers, and SWIFT Linea

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:

Please fasten your belts!

Ethereum Foundation Posts Fusaka Testnet Schedule

The Ethereum Foundation announced the Fusaka testnet activation schedule:

Ethereum Foundation Posts Fusaka Testnet Schedule

The post confirms that once all three testnets upgrade successfully, a mainnet activation slot will be chosen.

Fusaka’s headline feature is PeerDAS (EIP-7594), enabling nodes to sample data availability and paving the way to raise blob throughput without sacrificing security. To scale safely after PeerDAS, Ethereum will use Blob-Parameter-Only (BPO) forks that change only parameters (no new client software): BPO1 lifts the per-block blob target/max from 6/9 → 10/15, and BPO2 to 14/21; the post lists concrete dates for each testnet.

Beyond DA, Fusaka includes L1 performance and UX improvements: EIP-7935 sets a 60M default gas limit; EIP-7883 and EIP-7823 reprice/limit ModExp; EIP-7825 adds a transaction gas-limit cap (16,777,216); EIP-7642 (eth/69) cleans up network protocol baggage; UX-oriented items include the secp256r1 precompile (EIP-7951) and the CLZ opcode (EIP-7939). Client release candidates for Holesky/Sepolia/Hoodi are linked in the post.

Why it matters for Account and Chain Abstraction: more blob capacity should reduce L2 fees and increase headroom for intent-driven and batched AA flows; secp256r1 helps passkey/WebAuthn-style auth paths; and the staged BPOs give operators and wallets predictable checkpoints before mainnet.

Trust Wallet’s TWT-Powered Roadmap Targets Billion-User Scale

Trust Wallet released an official roadmap post describing a next-era plan to reach a billion users by 2030, with Trust Wallet Token (TWT) positioned as the utility layer for access to features such as sponsored gas, gas-less actions, advanced trading tools, and security enhancements. The post highlights scale metrics (210M+ installs, 100+ blockchains, $30B+ user balances) and claims prior work on Account Abstraction-related standards and features, including FlexGas tied to EIP-7702 and smart-wallet standards ERC-7779 and ERC-6900.

The roadmap is structured as progressive layers. “Everyday finance” targets simpler payments and transfers across chains with gas-free options and one-click protections; “advanced trading” aims for a self-custodial hub with cross-chain swaps and pro modes (including perpetuals and prediction markets) with MEV/front-running protections; an “earn” layer focuses on staking/lending opportunities and a rewards loop where engagement can boost yields and provide access to new project launches via Trust Alpha. A future layer envisions identity, credit, and embedded DeFi.

The connective tissue is the emphasis on gas sponsorship, cross-chain routing, and self-custodial UX — areas where AA features (e.g., 7702/FlexGas, modular smart-wallet standards) and Chain Abstraction patterns could make the “wallet as platform” model viable at scale.

Beyond Abstraction: The Practical To-Do List for Wallets and Smart Accounts

A new X post from @zuzazuber (Safe Ecosystem Manager) distills feedback from wallet builders, protocol teams, infra providers, and apps working at the edge of Account Abstraction.

The takeaway: despite progress with ERC-4337, ERC-7579, and EIP-7702, five persistent frictions still hold back mainstream self-custody:

  • Wallet landscape fragmentation that confuses both users and developers;
  • Cross-chain orchestration pain — funds on the wrong chain, fragmented balances, and network anxiety;
  • Key management and recovery that remain non-portable and intimidating;
  • Privacy that’s not yet a seamless “hygiene” layer;
  • User communication gaps: no standard wallet-level inbox, opaque calldata, and weak education.

The thread pairs each blocker with a “what’s needed” direction. Examples include opinionated reference paths and stronger defaults to cut complexity; infrastructure that hides chains entirely via unified balances and chain-agnostic accounts; robust, portable recovery frameworks; privacy embedded into infra rather than bolted on; and standardized wallet-native comms and interpreters that explain transactions in plain language.

The priorities here map directly to shipping production UX: fewer prompts, unified balances, safer recovery, and better explanations at the point of action. If wallet and infra teams coalesce around these patterns, Account Abstraction features and Chain Abstraction rails can translate into experiences that feel trustworthy and understandable to non-experts, not just power users.

SWIFT Chooses Linea for Blockchain Testing

Grégory Raymond from The Big Whale reports that SWIFT and several major banks (including BNP Paribas and BNY Mellon) have selected Linea, Consensys’ Ethereum L2, to test migrating parts of the interbank messaging system on-chain.

The X thread says Linea was chosen for its privacy-oriented cryptographic proofs and that the pilot is already in motion with more than a dozen institutions.

As of today, neither SWIFT nor Consensys has issued an official confirmation; The Defiant notes Consensys “declined to confirm or deny” details when asked. Separately (and more broadly), mainstream outlets have reported SWIFT’s blockchain push with Consensys’ involvement, but without naming Linea specifically.

Why it matters: a Linea-based pilot by SWIFT and Tier-1 banks would be one of the strongest signals yet that Ethereum-aligned infrastructure is fit for regulated, privacy-sensitive financial rails, feeding directly into Account/Chain Abstraction wallets that can route payments without user-visible chain complexity.


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)