Firedancer Mainnet: Solana's New Validator Client Is Live

Ethereum's Pectra upgrade went live on the mainnet at epoch 364032 — 10:05:11 UTC on May 7, 2025 — activating 11 Ethereum Improvement Proposals (EIPs) simultaneously, the largest single deployment of protocol changes since the Merge in 2022. For application developers and infrastructure operators, three changes require immediate attention: EIP-7702 enables smart account features on existing externally owned accounts (EOAs) without address migration, EIP-7251 raises the maximum validator staking balance from 32 ETH to 2,048 ETH, and EIP-7691 doubles average blob throughput for Layer 2 (L2) rollups from three to six blobs per block.

What Ethereum Pectra Actually Shipped at Epoch 364032

The Pectra name fuses Prague — the Ethereum execution layer upgrade convention following Devcon IV — with Electra, a consensus layer update named after a star in the constellation Taurus. According to the Ethereum Foundation's April 23, 2025 announcement post, the upgrade had been previously activated on the Hoodi, Holesky, and Sepolia testnets before mainnet deployment.

The 11 EIPs divide across three functional clusters. Staking mechanics received three EIPs: EIP-7251 raises the maximum effective validator balance to 2,048 ETH, EIP-7002 introduces execution-layer triggered withdrawals, and EIP-6110 moves deposit processing fully on-chain. Account abstraction received one protocol-level EIP: EIP-7702, which introduces Type 4 transactions. L2 scaling received EIP-7691 for doubled blob targets and EIP-7623 to cap worst-case block sizes in response to the increased bandwidth. Additional EIPs addressed BLS12-381 cryptographic precompile efficiency, consolidation operations for existing validators, and inter-layer deposit/withdrawal request standardisation.

The road to mainnet activation was not linear. Initial testnet deployments on Holesky and Sepolia encountered finality failures in February and early March 2025. The Ethereum core developer team launched a new dedicated testnet — Hoodi — as a final proving ground. Hoodi achieved full finalization on March 26, 2025, according to the Ethereum Foundation, which cleared the path for May 7. The mainnet date was locked in on April 3 following a core developer call. All major execution and consensus client teams released Pectra-compatible versions by April 21.

Ethereum Foundation Pectra mainnet announcement

The Staking Architecture Problem Pectra Solves for Operators

Ethereum's validator design had a structural inefficiency that compounded as institutional staking grew. Every validator node was capped at 32 ETH in effective balance. Operators running large validator sets for a single principal — staking pools, institutional custodians — had to maintain hundreds of individually managed 32-ETH validators. Any ETH earned beyond a validator's 32-ETH cap did not count toward active stake and required manual compounding by initiating new validator deposits.

EIP-7251 directly resolves this. By raising the maximum effective balance to 2,048 ETH — a 64× increase — existing validators can consolidate. An operator running 64 separate 32-ETH validators for one principal can merge these into a single node. According to the Ethereum Foundation's technical documentation, this reduces attestation gossip bandwidth requirements for the Beacon Chain's peer-to-peer layer and eliminates the overhead of coordinating exits and deposits across multiple validator identities. The change is opt-in and requires a credential-type update transaction on the execution layer.

EIP-7002 makes withdrawal operations more predictable for operators. Before Pectra, triggering a validator exit required action from the validator's signing key on the consensus layer — an operational dependency that complicated automated staking infrastructure. EIP-7002 allows exits to be triggered directly from the execution layer using the withdrawal credential address, decoupling signing key availability from exit processing.

Ethereum infrastructure and staking coverage→ /categories/web3-builder

EIP-7702 Changes the Account Abstraction Starting Point

Before Pectra, building smart account features on Ethereum required directing users to deploy a new smart contract wallet — a process carrying approximately 200,000 to 300,000 gas in deployment costs per user, plus the friction of migrating assets to a new address. ERC-4337, the existing account abstraction standard released in 2023, addressed programmable transaction logic but required this separate deployment step.

EIP-7702 introduces a third path. It adds a new transaction type — 0x04, denominated as Type 4 — that carries an authorization_list field. This field contains the target chain ID, the delegation contract address, and the user's ECDSA signature parameters (y_parity, r, s). When the user or a paymaster submits a Type 4 transaction, the EOA's execution context loads code from the pointed-to smart contract for that transaction's duration. The delegation is revocable and re-pointable; the user's original address does not change.

This enables builders to implement batch transactions (multiple protocol interactions in one atomic call), gas sponsorship (a third-party paymaster covers ETH costs), session keys (scoped temporary permissions without private key exposure), and social recovery — all accessible from an existing MetaMask or hardware wallet address. According to The Block's coverage from May 2025, more than 11,000 EIP-7702 authorizations occurred within one week of Pectra's mainnet activation, with MetaMask confirming support for gasless transaction flows using the new standard.

Infrastructure provider Etherspot launched a shared mempool for EIP-7702 UserOperations compatible with existing ERC-4337 bundlers, initially on Ethereum and Optimism, with Arbitrum, Base, and Linea integrations staged. Wallet-as-a-Service providers including Dynamic and Openfort published dashboard-level toggles for activating 7702 on embedded EOA wallets.

The Block: EIP-7702 authorization surge post-Pectra

L2 Builders and What Doubled Blob Throughput Means in Practice

The Dencun upgrade in March 2024 introduced blob transactions via EIP-4844, reducing L2 calldata costs by 10–100× across rollups that adopted the format. But the base layer supported only three blobs per block on average, with a maximum of six during demand spikes. As more rollups posted data to Ethereum and total value locked rebounded through 2025, competition for available DA slots intensified.

EIP-7691 raises the average blob target to six per block and the maximum to nine. According to the Ethereum Foundation, the binding constraint for blob capacity is peer-to-peer bandwidth — blobs must be gossiped across the network and are pruned after approximately 18 days (4,096 epochs). EIP-7623 counterbalances this bandwidth increase by capping worst-case block sizes; it limits the maximum calldata a block can carry, reducing the scenario where a single high-calldata block creates outsized bandwidth pressure.

For rollup developers, the change requires no code modifications on their end. The additional blob capacity is available immediately at the L1 level. The practical effect — lower fees for L2 users — depends on whether demand fills the new capacity. Linea confirmed it pre-staged EIP-7691 support ahead of mainnet to ensure its developers could access the doubled blob space from day one, according to the ConsenSys Pectra summary.

Security Considerations Builders Should Not Skip

One security tradeoff in EIP-7702 requires specific attention. Before Pectra, token approvals required users to send a transaction directly to each smart contract. This created a natural firewall: a single contract interaction could not batch-drain multiple tokens from an EOA in one transaction. EIP-7702 removes this constraint by design.

Ledger's security team noted in a post-Pectra advisory that several hardware wallet providers restricted initial EIP-7702 support to only the Ethereum Foundation's audited reference delegation contract, precisely because delegating an EOA to a malicious or poorly audited 7702 contract could batch-drain all approved tokens in a single atomic transaction. Builders implementing 7702 delegation flows in their applications must ensure the delegation contract they point users toward has undergone formal audit.

A second consideration: the authorization_list in Type 4 transactions includes chain ID as a replay protection mechanism. Developers building multi-chain applications should confirm their EIP-7702 integrations sign per-chain authorizations rather than re-using the same signed delegation across chains where the deployed contract at that address may differ.

QuickNode EIP-7702 implementation guide for Ethereum developers

Ethereum's Fusaka upgrade followed Pectra later in 2025, introducing PeerDAS and further expanding DA throughput for rollups at a protocol level beyond what EIP-7691 achieves — the milestone for builders to track is whether PeerDAS adoption reduces the per-blob cost structure enough to shift rollup economic models. For EIP-7702 integrations built today, the decision point to watch is progress on EIP-6900, the modular smart account standard that would determine how delegation contracts should be structured for forward compatibility with any future protocol-level account model.