Skip to content

docs: tw-1122 - #3799

Open
pete-vielhaber wants to merge 12 commits into
masterfrom
tw1122
Open

pete-vielhaber wants to merge 12 commits into
masterfrom
tw1122

Conversation

@pete-vielhaber

Copy link
Copy Markdown
Contributor

No description provided.

@vercel

vercel Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
arbitrum-docs-fumadocs Ready Ready Preview Nov 20, 2026 7:31pm UTC

Request Review

@pete-vielhaber
pete-vielhaber marked this pull request as draft November 12, 2026 20:19

@leeederek leeederek left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you Pete for putting this together! I appreciate it. There's alot of nuanced details that will require someone like @mglowack to help us confirm.

I also want to make a note that we will want to update all this when the change is live on arbitrum sepolia and then again when it is live on mainnet arbitrum one.

@@ -0,0 +1,171 @@
---
title: 'Migrate your transaction submission code'

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally, this sounds fine but won't it be a temporary page when we have yet to enable it formally?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you clarify what you mean by temporary page, @leeederek ?

| `timestampMin` / `timestampMax` | L2 timestamp window. |

- `eth_sendRawTransactionSync` submits a raw signed transaction and blocks until the node sees its receipt (or a timeout fires), returning the full receipt instead of just the tx hash.
- `eth_sendRawTransactionSync` submits a raw signed transaction and returns its receipt, or an error if a timeout fires first. Today the node returns the full receipt after the block is complete. A change rolling out to Arbitrum Sepolia first, then Arbitrum One, returns the receipt as soon as the sequencer executes the transaction. That receipt's `blockHash` is zero, because the block isn't complete yet. As a result, the method doesn't comply with [EIP-7966](https://eips.ethereum.org/EIPS/eip-7966), the Ethereum Improvement Proposal that defines it. For how it compares with `eth_sendRawTransaction`, see [Transaction submission behavior](/arbitrum-essentials/arbitrum-vs-ethereum/transaction-submission).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's make sure we include that the chain must be on the required version (3.13) and also that node operators need to set this flag --execution.rpc.tx-sync-forward=true


</Callout>

Arbitrum chains give you two ways to submit a signed transaction. They differ in when they return and what they return:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just as a note: there is a 3rd way to submit txns but we are removing it in Jan 2027 with a public deprecation notice posted separately. The language here is fine as is but wanted to flag this in case you wanted to say something more about it


When a submission hits a queue limit, `eth_sendRawTransaction` behaves as follows:

- **Queue full:** it returns an error right away.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does the txn get dropped in this case too?

anegg0 and others added 6 commits November 20, 2026 11:16
…transaction-submission.mdx

Co-authored-by: Derek Lee <103802618+leeederek@users.noreply.github.com>
…transaction-submission.mdx

Co-authored-by: Derek Lee <103802618+leeederek@users.noreply.github.com>
…ion-submission.mdx

Co-authored-by: Derek Lee <103802618+leeederek@users.noreply.github.com>
…ion-submission.mdx

Co-authored-by: Derek Lee <103802618+leeederek@users.noreply.github.com>
…transaction-submission.mdx

Co-authored-by: Derek Lee <103802618+leeederek@users.noreply.github.com>
…transaction-submission.mdx

Co-authored-by: Derek Lee <103802618+leeederek@users.noreply.github.com>
Apply the rest of Derek's review on PR #3799 and fix the formatting
that broke the Gates and Build jobs.

- Use Nitro 3.13.x and --execution.rpc.tx-sync-forward=true in the
  guide, the behavior page, rpc-methods and the published notice, so
  every page names the same version.
- Mark eth_sendRawTransactionConditional out of scope and link its
  deprecation notice.
- Add the 12-second default queue timeout to the deadline step, and
  state that a queue-full error means the sequencer never admitted
  the transaction.
- Rename the "Stop treating..." heading and update its anchor link.
@anegg0

anegg0 commented Nov 20, 2026

Copy link
Copy Markdown
Contributor

Thanks Derek. All suggestions are applied, and every page now says Nitro 3.13.x. Four open items:

  • --execution.rpc.tx-sync-forward=true: I can't find this flag in the Nitro source yet. Can you confirm the exact name?
  • Nonce retry window: I kept the SME question open until engineering confirms the 1-minute value.
  • eth_sendRawTransactionSync timeout in the example (5000 ms): waiting on engineering for a recommended value.
  • Temporary page: the guide stays after the rollout. Only the "Rollout status" callout changes at each stage.

The wider cells from the review edits left two tables unaligned, which
failed the Formatting gate.
@anegg0
anegg0 marked this pull request as ready for review November 20, 2026 19:50

This branch was successfully deployed

1 active deployment
Preview — 11dea64b Deployed Nov 20, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants