Some transactions return TIMESTAMP_TOO_FAR_IN_FUTURE

Tech Support
#1

Hi there,
since a few days, some transactions are returning error FAILURE_TIMESTAMP_TOO_FAR_IN_FUTURE

Given that the web site has not been updated, is there any new version release in NIS testnodes that maybe has changed the behaviour of timestamps’ transactions?

We are using nem-sdk from QuantumMechanics.

We have changed endpoints, but it doesn’t fix the problem.

This error never happened before.

Do you know any examples how to specify a timestamp to send a transaction using nem-sdk?

As far as I know the sdk manages timestamp automatically.

#2

Sorry I have no idea but have you read this?:

#3

Yes, I have.
It seems that in testnet there has been some issue with timestamps.
We are using nem-sdk, but sdk is coded in a way that sometimes some issues occur, because from time to time, it appears this error.
In mainnet we haven’t seen it yet.

The best thing would be a fix in the nem-sdk code and call the NIS api time, instead of creating new Date().
A simple workaround maybe would be to create a timestamp with some seconds behind, so that the transactions will not occur in the future once they are send to the blockchain.

#4

I am not a programmer (I can write a bit of basic code thats all), hope some one here can shed some light on it.
Dan

#5

Best option is to fetch timestamp from node and use it as nanowallet (nano use also nem-sdk)

I also noticed this problem on testnet last days.