IoTeX activated its v2.4.0 Yap hardfork at block height 48,985,561, bringing full Ethereum Pectra compatibility to the Decentralized Physical Infrastructure Network (DePIN)-focused layer-1 (L1). The upgrade includes EIP-7702 account abstraction, EIP-7623 calldata repricing, EIP-2935 historical block hashes, and EIP-2537 BLS12-381 precompiles, plus a three-stage candidate exit queue for delegates.
What is the Yap hardfork all about?
IoTeX’s Yap fork is a two-part upgrade: an Ethereum Virtual Machine (EVM) layer that pulls four Pectra Ethereum Improvement Proposals (EIPs) from Ethereum, and a staking-layer change that adds a candidate exit queue.
The headline feature is EIP-7702, which lets Externally Owned Accounts (standard wallets) temporarily delegate code execution to a smart contract through a new transaction type (0x04). For IoTeX’s DePIN use case (devices signing transactions from constrained hardware), that means a device’s EOA can be batched, sponsored, or session-scoped without migrating to a permanent smart wallet.
The other EIPs: EIP-7623 increases calldata costs (IoTeX set TX_COST_FLOOR_PER_TOKEN to 250 vs Ethereum’s 40), pushing DePIN builders toward batched, compressed payloads. EIP-2935 stores the last 8,191 block hashes in a system contract for light clients and bridges. EIP-2537 adds BLS12-381 precompiles for cheap onchain verification of aggregate signatures.
Important aspects of v2.4.0 Yap Hardfork
- EIP-7702 Account Abstraction (Tx Type 0x04): Standard wallets gain smart contract powers. A DePIN device can sign a session key delegation without migrating funds. Works identically to Ethereum’s Pectra rollout from May 2025.
- Calldata Repricing (EIP-7623): IoTeX deliberately raised calldata costs (250 per token vs Ethereum’s 40). At 100 gas/byte baseline (vs Ethereum’s 16), uncompressed device telemetry becomes meaningfully more expensive. Batched, compressed payloads are now a requirement, not an option.
- Historical Block Hashes (EIP-2935): System contract at 0x0000F90827F1C53a10cb7A02335B175320002935 stores the last 8,191 block hashes in state. Light clients and bridges no longer need archive nodes for historical reads.
- BLS12-381 Precompiles (EIP-2537): Addresses 0x0b through 0x11 unlock cheap onchain verification of Barreto-Lynn-Scott (BLS) aggregate signatures, critical for cross-chain proofs and light-client bridges.
- Candidate Exit Queue: Exiting the network is now a three-step process (Request, Schedule, and Confirm) to keep things stable when validators change/rotate. Just a heads-up: only one exit is allowed every 24-epoch window.
- Mandatory v2.4.1 Patch: All operators need to update to v2.4.1 or higher. The v2.4.0 version had some bugs with archive nodes and event data, but this patch clears those right up.
What this means for the IoTeX community
For DePIN builders, Yap is a game-changer. EIP-7702 means devices with limited signing capabilities can now interact with IoTeX without full wallet migrations. A Helium hotspot or Digital Infrastructure for Moving Objects (DIMO) device can authorize temporary sessions, batch telemetry, and sponsor transactions, all from a standard EOA. The calldata repricing is a deliberate lever: IoTeX wants efficient data packing, not raw sensor dumps.
For wallet and Software Development Kit (SDK) vendors, Yap delivers the same EIP-7702 surface as Ethereum mainnet. MetaMask, Rabby, and smart wallet SDKs from Alchemy or Pimlico get IoTeX support effectively for free.
For delegates, the exit queue adds predictability: no more instant validator exits destabilizing the network.
For the broader ecosystem, IoTeX joins a growing list of EVM chains (including Optimism and other rollups) pulling Pectra primitives into their own forks within months of Ethereum mainnet.
