Skip to content
This repository has been archived by the owner. It is now read-only.

Mitigate "Timestamp is in the future" error #191

Closed
slaweet opened this issue Jul 13, 2017 · 0 comments

Comments

@slaweet
Copy link
Contributor

commented Jul 13, 2017

When user's OS time is a few seconds ahead, all transactions are rejected with "Invalid transaction timestamp. TimeStamp is in the Future" error message.

When this error is obtained in lisk-js, it could try to do the transaction again with timestamp 10 seconds in the past. Maybe try to repeat this step 3 times with 10, 20, 30 seconds?

There are several issues on Lisk Nano reporting this: LiskArchive/lisk-nano#485 LiskArchive/lisk-nano#458 LiskArchive/lisk-nano#365
I heard even more on Lisk Chat, so I consider this to be a big problem. It happens mainly on Windows due to its lack of time sync.

@slaweet slaweet added the 🐛bug label Jul 13, 2017

willclarktech added a commit that referenced this issue Jul 17, 2017

@willclarktech willclarktech self-assigned this Jul 17, 2017

@willclarktech willclarktech added the *easy label Jul 17, 2017

@willclarktech willclarktech added this to In Progress in Version 1.0.0 Jul 17, 2017

@willclarktech willclarktech added *medium and removed *easy labels Jul 17, 2017

willclarktech added a commit that referenced this issue Jul 17, 2017

willclarktech added a commit that referenced this issue Jul 17, 2017

willclarktech added a commit that referenced this issue Jul 18, 2017

Merge pull request #195 from LiskHQ/191-retry_timestamp_future
Use offsets in transaction creation - Closes #191

@willclarktech willclarktech removed this from In Progress in Version 1.0.0 Jul 18, 2017

willclarktech added a commit that referenced this issue Jul 18, 2017

willclarktech added a commit that referenced this issue Jul 19, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants
You can’t perform that action at this time.