-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replay protection via high-order bits of nonce #166
Comments
There has been no activity on this issue for two months. It will be closed in a week if no further activity occurs. If you would like to move this EIP forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review. |
This issue was closed due to inactivity. If you are still pursuing it, feel free to reopen it and respond to any feedback or request a review in a comment. |
Specification.
Let CHAIN_ID = 18 for mainnet, 28 for testnet.
If
block.number >= FORK_BLKNUM
, then:nonce // 2**64
is equal to either 0 or CHAIN_ID.nonce % 2**64
. That is, for the transaction to be valid, it must be the case thataccount.nonce == tx.nonce % 2**64
, and after the transaction is processed we setaccount.nonce == (tx.nonce % 2**64) + 1
.The text was updated successfully, but these errors were encountered: