-
Notifications
You must be signed in to change notification settings - Fork 3
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
Error: Could not place order: GraphQL error: Invalid timestamp using payload #20
Comments
Hi @DulajSP, are you making that call from a server or a browser? Anyway I think it might be the same error I'm getting: #15 (comment) For me the timeout comes from a |
Hi @DulajSP I took some time to investigate the issue yesterday and found it was because the settings we are running the pool filling with are not suitable for the browser. I've exposed a method to reconfigure those settings here: nash-io/nash-protocol#9 Once the MR has been merged and a new version of the protocol has been released you should be able to set it to a more appropriate level. |
@DulajSP From the server, I do witness a lag (4-5s I'd say) when placing the very first order. But the order does go through and I don't get the "Invalid timestamp" error. Maybe this has to do with your server location? But then the other calls would probably also fail.. |
@DulajSP Do you have Telegram? If you do, ping me |
Thanks @Marcpepe |
I'm getting following error when i try to place a limit order.
( Error: Could not place order: GraphQL error: Invalid timestamp using payload )
Any help would be appreciated.
The text was updated successfully, but these errors were encountered: