Deprecation Notice: eth_sendRawTransactionConditional

Abstract

Offchain intends to remove eth_sendRawTransactionConditional (ERC-7796) from the Arbitrum Nitro stack and the sequencer endpoints of Arbitrum One and Arbitrum Nova as part of our efforts to modernize and streamline the codebase. Formal deprecation of this method will take place following a 30-day public comment period and a subsequent 30-day grace period. This means the target date for formal deprecation of this method will be Jan 17, 2027. AIP-2, proposed by Alchemy, activated this method in 2023 for ERC-4337 bundlers, but our review found no known genuine bundler usage and very few successful calls. We expect no impact on account-abstraction users and are inviting comment on this thread before the decision is final.

Motivation

eth_sendRawTransactionConditional is eth_sendRawTransaction with preconditions attached: storage-slot values and block or timestamp bounds that must still hold when the sequencer includes the transaction. If these preconditions do not hold, the sequencer rejects calls before inclusion (with error -32003). AIP-2 activated the method for ERC-4337 bundlers, which pay gas up front for handleOps and are only repaid on-chain, so they would not lose money when an account changed its own state between simulation and inclusion.

That is not how the method is being used today. Analyzing sequencer calls over a recent 30 day period (Sept 29 – Oct 29, 2026), we found that fewer than 1% of conditional calls on Arbitrum One succeeded. A separate 14-day review of on-chain activity (Oct 20 – Nov 3, 2026) traced all measured traffic to two automated searcher fleets, not ERC-4337 bundlers.

We believe that bundler operators, like Alchemy who originally proposed AIP-2, are now handling the majority of UserOps on Abitrum chains with eth_sendRawTransaction instead, and most are permissioned bundlers repaid off-chain, so the guarantee this method offers does not apply to them. As a reference, shared-mempool bundlers like: Skandha, Voltaire, Rundler and even the reference bundler) ship conditional sends behind an off-by-default flag.

That leaves a second submission path in the sequencer, with its own validation rules to maintain, test and support in every Nitro release, serving callers it was never built for.

Rationale

AIP-2 was justified to align Arbitrum with Ethereum’s account-abstraction push around ERC-4337 over three years ago. However, the ERC-4337 landscape has evolved: the OPStack ships the method off by default behind an EntryPoint-only proxy (docs), and Polygon honors it only from validator-connected bundlers (PIP-15). Arbitrum One is an outlier in exposing it publicly to all callers.

Given the usage described above, we believe removal will streamline and modernize the codebase. Restriction-based approaches like rate limits, cost caps or an allow-list (see Specifications) would each add technical complexity and logic to protect a path its intended users don’t take. Deprecating this method simplifies transaction intake for every user of the chain, which serves the DAO’s interest in reliable, low-cost execution more than preserving a feature with no measured intended beneficiaries.

We are posting this notice to invite comment and discussion from the ArbitrumDAO.

Key Terms

  • Conditional transaction — a transaction sent via eth_sendRawTransactionConditional with preconditions (knownAccounts storage slots, block/timestamp bounds) that the sequencer must verify before inclusion (ERC-7796).

  • ERC-4337 bundler — a service that packages user operations (UserOps) into a handleOps call to the EntryPoint contract and pays the gas up front.

  • Comment period — the 30 days after this notice is posted during which feedback is collected on this thread before the decision is confirmed.

  • Grace period — the 30 days after the comment period closes during which the method continues to work so that any affected integrators can migrate.

Specifications

What changes. On Jan 17 2027, eth_sendRawTransactionConditional will be disabled at the public sequencer endpoints of Arbitrum One and Nova. On and after this date, calls using this method will return a standard method-not-found error (-32601). eth_sendRawTransaction and existing rate limits on failing submissions are unchanged. Code removal from Nitro follows in a later release and so chains running their own Nitro sequencer are unaffected until then.

Table 1: Usage data (as of 2026-10-29).

Metric measured Arbitrum One
Calls / successes, 30 d ~5.0M / ~48K (0.97%)
Who sends Unknown, but we’ve identified a 10-key fleet guarding calls to its own unverified contract and zero overlap with ~100 active bundler keys
Why calls fail 74% premature TimestampMin (a scheduler)
Genuine ERC-4337 bundler use None measured or observed.

Table 2: Alternatives considered

Option Why not
Keep, with per-IP or global rate limits Reduces failing volume but keeps the code path, and adds an operational rule every chain must maintain.
Keep, with OP Stack-style cost caps in Nitro Engineering work to keep a method with no measured legitimate users
Keep, restricted to allow-listed bundlers (Polygon model) Same work, plus an allow-list to operate, for users who have told us they do not need it
Remove (this notice) Retires the code path entirely; no supported use case affected

Steps to Implement

  1. Publish this notice on the Arbitrum DAO forum (this post) and in the Arbitrum technical docs, and mark the method “soon to be deprecated” in the Arbitrum docs.

  2. Notify known bundler operators and chain partners directly

  3. Collect feedback on this thread for 30 days, then confirm the decision here and start the 30-day grace period; extend the comment period or revisit the decision if a genuine dependency surfaces.

  4. Disable the method at the Arbitrum One and Nova sequencer endpoints at the end of the grace period.

  5. Remove the implementation from Nitro in a subsequent release, with the change noted in release notes, formally deprecating this method altogether.

Steps 1–5 are carried out by Offchain Labs. No governance action, treasury spend or contract upgrade is required.

Timeline

Date Milestone
Nov 18 2026 Notice published; docs updated; direct notices sent; 30-day comment period opens
Dec 18 2026 (Nov 18 + 30d) Comment period closes; decision confirmed on this thread; 30-day grace period begins
Jan 17 2027 (Nov 18 + 60d) Method disabled at the Arbitrum One and Nova sequencer endpoints
Subsequent Nitro release Implementation removed from the client

Call for comments.

If you operate a bundler, wallet, or application that relies on eth_sendRawTransactionConditional on Arbitrum One or Nova, reply on this thread before Dec 18 2026 with what you use it for and what breaks without it. Questions about the analysis, the timeline or the migration path are welcome from anyone.

Overall Cost

No DAO funds are requested. The endpoint change is a configuration change at infrastructure Offchain Labs already operates; the Nitro code removal and sampling work are absorbed by Offchain Labs engineering.

Conflicts of interest statement

Offchain Labs develops Nitro, and operates the sequencer infrastructure for Arbitrum One and Nova, on behalf of the Arbitrum Foundation. Offchain Labs, and therefore the Arbitrum Foundation, bears the operational cost of the traffic described above and benefits from removing it.

Offchain Labs also develops the ZeroDev UltraRelay bundler, which does not use the eth_sendRawTransactionConditional method.

The usage data in this notice was gathered and analyzed by Offchain Labs.

We believe that bundler operators, like Alchemy who originally proposed AIP-2, are now handling the majority of UserOps on Abitrum chains with eth_sendRawTransaction instead

Jake here from Alchemy. I am supportive of this deprecation.

While our bundler did use this method in the past, I can confirm that Alchemy is no longer using this method on Arbitrum chains.

1 Like

Thank you @jake-alchemy for your comment and for the additional context on Alchemy’s usage of the method.