Skip to content
This repository has been archived by the owner on Oct 4, 2019. It is now read-only.

Implement ReplayAttack protection #93

Closed
splix opened this issue Oct 22, 2016 · 3 comments
Closed

Implement ReplayAttack protection #93

splix opened this issue Oct 22, 2016 · 3 comments

Comments

@splix
Copy link
Contributor

splix commented Oct 22, 2016

Implement ReplayAttack protection by introducing new signature component, based on BlockHash of last fork.

Key elements:

  • optional, accept non-protected transactions on validation
  • enable signing after block 3,000,000
    • accept new signature
    • sign with new component by default
  • use hash of block 1,920,000
  • write tests
  • cli flag to disable new sign (optional task)
  • cli flag to require new sign for mining (optional task)

Reference:

@elaineo
Copy link
Member

elaineo commented Oct 24, 2016

Are we decided on ECIP1011?

@splix splix added the size/L label Oct 25, 2016
@splix
Copy link
Contributor Author

splix commented Oct 25, 2016

@elaineo not decided yet, but we want to use this task as a test task for a new developer. We may accept it or not, but it's good enough to get familiar with the code.

@avtarsehra
Copy link

@splix, thanks this looks good.

@splix splix self-assigned this Dec 6, 2016
@splix splix closed this as completed Dec 27, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants