Ethereum Sets Fusaka for December, Epoch Protocol raises $1.2M, “Not All State Is Equal” Ethereum Study, Mono Protocol $2M

#web3 #ethereum

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 Schedules Fusaka Upgrade for December
Epoch Raises $1.2M to Coordinate Solvers for Intent-Based UX
Not All State Is Equal: What Actually Persists on Ethereum
Mono Raises $2M: Chain Abstraction with One Balance & One Account

Please fasten your belts!

Ethereum Schedules Fusaka Upgrade for December

Ethereum core developers agreed on a tentative mainnet date of Dec. 3, 2025 for the Fusaka upgrade during this week’s ACDC call, with public testnet rollouts in October to de-risk deployment.

A phased capacity plan will follow on mainnet via Blob-Parameter-Only (BPO) forks: one week after Fusaka, BPO-1 lifts the blob target/max from 6/9 → 10/15; a week later, BPO-2 raises it to 14/21, expanding space for L2 data without requiring new client software.

An official rollout timeline maintained by Ethereum researcher Barnabás Busa documents the sequence across Holesky, Sepolia and Hoodi testnets in October–November and shows mainnet activation on Dec. 3, 2025 (UTC), with BPO-1 on Dec. 17 and BPO-2 on Jan. 7, 2026. These BPOs adjust only blob parameters, letting developers observe network performance between steps and scale safely.

Blobs, introduced in March’s Dencun upgrade, are the data availability lane that rollups use to post transaction data at lower cost. More blob capacity should relieve L2 fees and increase headroom for throughput as usage grows.

For AA and chain-abstraction builders, the implication is straightforward: cheaper, more plentiful blob space improves the economics of L2-first UX, including intent flows and batched user operations that rely on rollup throughput. If testnets validate the targets, December’s Fusaka + staged BPOs could deliver a measurable cut in data costs within weeks of mainnet activation.

Epoch Raises $1,2M to Coordinate Solvers for Intent-Based UX

Epoch Protocol announced a $1.2 million pre-seed round to develop a solver coordination layer that turns user intents into atomic, verifiable outcomes across chains.

The press release lists backers including L2Iterative Ventures, Alphemy Capital, G20 Group, Longhash Ventures, SAFE, and HadronFC, plus angels such as Anurag Arjun and Prabal Banerjee (Avail), Adrian Brink (Anoma), Matt Wright (Gaianet), Harsh Rajat (Push), and others. The team says the capital will fund engineering, ecosystem partnerships, and a staged public testnet for developers, node operators, and solver contributors.

Epoch frames the problem as Web3 fragmentation: users and apps juggle bridges, gas tokens, approvals, and liquidity across many chains. Its approach lets users declare desired outcomes (e.g., “provide liquidity” or “swap to receive ≥X USDC”), while a decentralised solver network finds routes and executes plans atomically under on-chain constraints.

The company positions this as the “glue” between declarative intents and safe execution — directly complementary to account abstraction and chain abstraction stacks emerging around Ethereum.

If Epoch’s testnet proves robust, wallets and smart-account frameworks could outsource multi-step, multi-chain orchestration to a competitive solver market while keeping non-custodial verification on-chain, reducing prompts and hidden trust in single relayers.

Not All State Is Equal: What Actually Persists on Ethereum

A new post by @ngweihan_eth analyzes state usage from genesis through pre-Pectra block 22,431,083, showing that a small set of contracts holds most storage while the majority of deployments are short-lived.

Median activity span is 0 blocks for contracts versus ~22,317 blocks (~3.1 days) for EOAs; over 55% of contracts are accessed in a single block and never again. EOAs exhibit heavier right tails at the 75th and 95th percentiles, indicating more long-lived activity than contracts.

Contract diversity is narrower than it seems: ~150k template bytecodes account for ~97% of all contracts, yet unique bytecodes (one-off implementations) hold ~two-thirds of all storage slots (~875M vs ~429M for templates). This suggests that the state that actually persists tends to live in bespoke systems — DEXs, bridges, registries, admin/multisig and other infra — rather than mass-produced clones. Factory-minted contracts constitute ~89% of deployments, but non-factory contracts are generally more stateful and longer-lived.

The study also segments by code size and storage: stateless contracts (>50% of contracts) tend to have longer activity spans when active, whereas many stateful contracts churn quickly; “tiny” contracts dominate in count, but their non-zero cohort can remain active for months. Overall, the data points toward a highly concentrated, long-tail distribution where a minority of contracts drive most durable state.

Why it matters: For roadmap items like state-expiry, pruning, and client performance, optimizing around what actually persists (and where) could cut costs without harming UX. The findings argue for storage-light patterns (modules, session keys, off-chain intent metadata) and careful use of persistent slots, aligning wallet/app design with how state actually lives and dies on Ethereum today.

Mono Raises $2M: Chain Abstraction with One Balance & One Account

Mono Protocol announced a $2M private round to develop a chain-abstraction layer that makes Web3 feel like one network. In its press release, the team positions Mono as infrastructure that removes cross-chain fragmentation rather than another bridge or single-chain app.

Per the project’s site, Mono’s core idea is a single, per-token balance across networks (“one balance, one account, one click”). Behind the scenes, Mono coordinates routing and settlement to present a unified balance while aiming for instant, MEV-resilient execution — so users don’t manage bridges, gas tokens, or chain switching. The architecture also references liquidity locks and a solver/bonding model designed to guarantee execution.

Unified balances and universal accounts map directly to account abstraction and chain abstraction goals — fewer prompts, fewer failed txs, and intent-like flows that can settle across chains without exposing complexity. If Mono ships as described, wallets and dapps could compose multi-chain actions while preserving a single user identity and spendable balance.

🐞 Submit your UserOps through a reliable ERC-4337 bundler, trusted by Web3 developers.