This repository has been archived by the owner on Apr 15, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 60
"Invalid transaction timestamp" #365
Labels
Comments
You need to fix your local clock.
…On Fri, Jun 9, 2017 at 12:01 AM, Unhandled Exception < ***@***.***> wrote:
Sometimes i get "Invalid transaction timestamp" while sending transaction.
After retrying few times it works fine.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#365>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/APzFsLT0P0EDkyKhsODIJ7kkddEuItSfks5sCG8-gaJpZM4N0rQa>
.
|
My local clock is just fine. I'm not the only one with this issue. |
This was referenced Jul 13, 2017
In addition to mitigating this in lisk-js LiskArchive/lisk-elements#191 we could also provide a more user-friendly error message when this happens. |
It happens to me too, so I just change my local clock backward and then it worked. |
Fixed in |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Sometimes i get "Invalid transaction timestamp" while sending transaction. After retrying few times it works fine.
The text was updated successfully, but these errors were encountered: