Repository navigation
Conversation
Add the nonce validity predicate (base/base v1.5.0) to the predicate tables, overview, and build guide, with an example and evaluation notes. Add the mandatory block_number upper bound to the RPC request example, which the RPC already rejects without one.
Collaborator
🟡 Heimdall Review Status
|
Explain that the block_number example value is a placeholder and how to set it, clarify that the nonce predicate checks protocol nonce state only, and correct the expiry behavior after a nonce mismatch.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed? Why?
base/base adds a
noncevalidity predicate in v1.5.0 (seeValidityPredicate::Nonceincrates/execution/txpool/src/validity.rs). This PR documents it:nonce(address,op,value) to the predicate tables on Predicates and Safety and Validity Transaction RPC.0nonce for absent accounts, and what happens when a nonce moves past an upper bound (the transaction stays pending until itsblock_numberbound passes).nonceon the Overview and Build a Validity Transaction pages.It also fixes the RPC request example. Every submission must include a
block_numberupper bound within the 60-second window (enforced since v1.4.2, and already described under Expiry on Fees, Ordering, and Lifecycle), but the example had only a storage predicate, so the RPC would reject it as written.Notes to reviewers
Draft until base/base 1.5.x reaches mainnet nodes. Please don't merge before then. Signed validity predicates and the fill-or-kill flag are feature-flag gated and will get separate comms, so this PR leaves them out.
An independent review by GPT-6 Astra checked the PR against base/base. Its changes are applied in the second commit:
block_numbervalue in the RPC and build-guide examples is marked as a placeholder, with instructions to set it frometh_blockNumber(latest + 10).0) and does not prove that an earlier transaction succeeded.flashblock_indexbound can end it earlier.How has it been tested?
node scripts/lint-mdx.json the changed files: 0 errors (7 existinghighlight={}suggestions).npm test: pass.mainand thev1.5.0-rc.8/v1.4.2tags.Screenshots
N/A (text and table changes only; no layout changes)
Generated with Toshi