Etherspot 🐞

Everything you need to start building with Account Abstraction — in one place. At Etherspot, we provide the full stack: modular SDK, Skandha bundler, Arka paymaster, and developer-ready infrastructure. Build with Etherspot 🛠️

Etherspot Explains: EIP-8151 EIP-8151 proposes a small but important change to how Ethereum verifies signatures. Today, many smart contracts rely on the ecrecover precompile to check whether a message was signed by a specific address. If the signature is valid, ecrecover returns the signer’s address. However, EIP-7851 introduces the ability for delegated EOAs to deactivate their private keys. The problem is that ecrecover is stateless. Even if a private key is deactivated at the protocol level, ecrecover would still return the original address when verifying an old signature. This creates a mismatch: from the protocol’s perspective the key is inactive, but contracts using ecrecover may still treat signatures from that key as valid. EIP-8151 proposes updating ecrecover so that after recovering the address, it checks whether that key has been deactivated. If the key is deactivated, the function would return the zero address instead. This helps protect immutable contracts that rely on ecrecover for authorization, such as ERC-2612 permit-based tokens or systems like Uniswap’s Permit2. One limitation: contracts that implement ECDSA verification directly in Solidity instead of using the ecrecover precompile would not be affected. In short, EIP-8151 ensures that signature verification stays consistent with key deactivation, closing an important gap introduced by EIP-7851.

Etherspot Explains: EIP-8141 (Frame Transactions) Most Ethereum transactions today follow a fixed validation model: a single ECDSA signature authorizes the transaction, the sender pays gas, and validation + execution are tightly coupled in one predefined flow. EIP-8141 proposes a different model. It introduces a new core transaction type called Frame Transactions, which separates how a transaction is validated, what logic it executes, and how gas is paid. Instead of baking all of this into one signature check, transactions can be composed of multiple frames, each responsible for a specific step. For developers, EIP-8141 removes the assumption that transaction authorization must follow a single, protocol-defined signature model. Validation is handled by programmable frames instead of a fixed ECDSA signature check. Frame Transactions organize data into ordered frames with different modes. Some frames handle signature verification, others execute contract logic, and others explicitly approve gas payment. This means transactions no longer have to follow a single, fixed flow. The proposal builds on ideas explored in EIP-7702, but goes further by removing the protocol’s dependency on a single authorization mechanism. It also updates gas accounting and receipts to support multi-frame execution, while remaining compatible with recent changes like blob gas fees from EIP-4844. This flexibility also introduces new risks. If transaction validation becomes too computationally complex, it could strain the network, so the proposal includes limits to keep validation predictable and safe. Despite being recently published, EIP-8141 represents a foundational shift: moving from “one transaction shape fits all” to transactions that are programmable, future-ready, and no longer tied to today’s cryptographic assumptions.