|Author||Micah Zoltu, Alex Beregszaszi|
Table of Contents
Limit account nonce to be between
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.
Lastly, this facilitates a minor optimisation in clients, because the nonce no longer needs to be kept as a 256-bit number.
block.number >= FORK_BLOCK introduce two new restrictions:
- Consider any transaction invalid, where the nonce exceeds
CREATEinstruction to abort with an exceptional halt, where the account nonce is
It is unlikely for any nonce to reach or exceed the proposed limit. If one would want to reach that limit via external transactions, it would cost at least
21000 * (2^64-1) = 387_381_625_547_900_583_915_000gas.
It must be noted that in the past, in the Morden testnet, each new account had a starting nonce of
2^20in order to differentiate transactions from mainnet transactions. This mode of replay protection is out of fashion since EIP-155 introduced a more elegant way using chain identifiers.
Most clients already consider the nonce field to be 64-bit, such as go-ethereum.
All integer values <= 2^52 can be encoded in a 64-bit floating point without any loss of precision, making this value easy to work with in languages that only have floating point number support.
While this is a breaking change, no actual effect should be visible:
- There is no account in the state currently which would have a nonce exceeding that value. As of November 2020, the account
0xea674fdde714fd979de3edf0f56aa9716b898ec8is responsible for the highest account nonce at approximately 29 million.
Copyright and related rights waived via CC0.
Please cite this document as: