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

Transaction timestamp should have limited lifetime #119

Open
vekexasia opened this issue Mar 11, 2018 · 0 comments
Open

Transaction timestamp should have limited lifetime #119

vekexasia opened this issue Mar 11, 2018 · 0 comments

Comments

@vekexasia
Copy link
Contributor

Problem:
Currently if A needs to send a transaction to B and B is in the same network he could:

  • MITM
  • Collect the signed transaction on its way to a peer

By forcing A to rebroadcast a newly crafted transaction B can later broadcast the collected transaction effectively getting paid twice.

Solution?:
The timestamp field should not be allowed to be too old. Maybe we should do some research and decide a time-window after which a transaction expires and can no longer be accepted by the network.

Another, more complicated, solution might involve adding a new field to each transaction that reflect, somehow, the currenct account status so that one tx excludes the other.

@vekexasia vekexasia added this to To do in 1.1.0 via automation Mar 11, 2018
@vekexasia vekexasia removed this from To do in 1.1.0 Jul 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant