You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Problem:
Currently if
A
needs to send a transaction toB
andB
is in the same network he could:By forcing
A
to rebroadcast a newly crafted transactionB
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.
The text was updated successfully, but these errors were encountered: