Limit account nonce to 2^64-1

The five-minute read

One action, walked through

1. Open EIP 2681 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: Account nonces are currently specified to be arbitrarily long unsigned integers.
3. Name the object that changes: CREATE, CREATE2.
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing EIP 2681 at the status the text itself states: Final.
• The object that has to change is CREATE, CREATE2. A neighbouring document with a similar name is not this one.
• Status in the header is not adoption.

What happened after the paper

The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What must an implementation of Limit account nonce to 2^64-1 accept, and what may it ignore?
• Is this consensus, peer policy, or an application interface?
• Which names does the text pin down: CREATE, CREATE2?

Terms

EIP 2681

The public text titled Limit account nonce to 2^64-1.

Final

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

An interface that is only a name in a repository will be re-implemented differently by every team, which is how shared contracts break.

What the design proposes

• Account nonces are currently specified to be arbitrarily long unsigned integers.
• Dealing with arbitrary length data in the state witnesses is not optimal, therefore this EIP will allow proofs to represent the nonce in a more optimized way.
• Additionally it could prove beneficial to transaction formats, where some improvements are potentially sought by at least three other proposals.

How the mechanism is specified

• Taken from the specification, the next constraint is: Dealing with arbitrary length data in the state witnesses is not optimal, therefore this EIP will allow proofs to represent the nonce in a more optimized way.
• Locate CREATE, CREATE2 in EIP 2681 and apply it to one transaction or call.
• Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

• This document does not set a fee, a valuation, or a security proof.
• Status in the header is not adoption.
• The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it.

Why a venture studio still reads it

Use EIP 2681 when a pitch says 'Limit account nonce to 2^64-1' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.