Skip to content

docs: allow any nonce for expiring nonce transactions - #937

Merged
shekhirin merged 1 commit into
mainfrom
centaur/expiring-nonce-any-nonce-1790725507
Sep 30, 2026
Merged

shekhirin merged 1 commit into
mainfrom
centaur/expiring-nonce-any-nonce-1790725507

Conversation

@decofe

@decofe decofe commented Sep 29, 2026

Copy link
Copy Markdown
Member

The expiring nonces guide says nonce must be set to 0. TIP-1106 removes that requirement starting at T12, so the guide no longer says it.

This PR also adds a short "Distinguishing identical transactions" subsection. Expiring nonce transactions with the same sender, calls, fee parameters and validBefore hash to the same value, so the second one is rejected as a replay. After T12, nonce can be any uint64 value. Setting it to a distinct or random value makes each transaction hash unique. The subsection also notes that before T12, nonce must still be 0.

Validation: pnpm check:types

Prompted by: @klkvr

Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
@vercel

vercel Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
tempo-docs Ready Ready Preview Sep 29, 2026 11:48pm UTC

Request Review

@shekhirin
shekhirin merged commit 8c9bf42 into main Sep 30, 2026
14 checks passed
@shekhirin
shekhirin deleted the centaur/expiring-nonce-any-nonce-1790725507 branch September 30, 2026 09:47

This branch was successfully deployed

1 active deployment
Preview — 2542db3f Deployed Sep 29, 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