Skip to content
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

Closed
vbuterin opened this issue Oct 28, 2016 · 3 comments
Closed

Replay protection via high-order bits of nonce #166

vbuterin opened this issue Oct 28, 2016 · 3 comments
Labels

Comments

@vbuterin
Copy link
Contributor

Specification.

Let CHAIN_ID = 18 for mainnet, 28 for testnet.

If block.number >= FORK_BLKNUM, then:

  • For a transaction to be valid, it must be the case that nonce // 2**64 is equal to either 0 or CHAIN_ID.
  • The nonce of the transaction for verification purposes is now nonce % 2**64. That is, for the transaction to be valid, it must be the case that account.nonce == tx.nonce % 2**64, and after the transaction is processed we set account.nonce == (tx.nonce % 2**64) + 1.
@Nashatyrev
Copy link
Member

@vbuterin Why do we need another replay protection together with #155 ?

@github-actions
Copy link

github-actions bot commented Jan 5, 2022

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.

@github-actions github-actions bot added the stale label Jan 5, 2022
@github-actions
Copy link

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.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants