FAILURE_TIMESTAMP_TOO_FAR_IN_FUTURE There was no such problem last week. but today, it always appears when I transfer on testnet, What happened?

exchange universe
FAILURE_TIMESTAMP_TOO_FAR_IN_FUTURE There was no such problem last week. but today, it always appears when I transfer on testnet, What happened?

Look here http://127.0.0.1:7890/chain/last-block

exchange universe
FAILURE_TIMESTAMP_TOO_FAR_IN_FUTURE There was no such problem last week. but today, it always appears when I transfer on testnet, What happened?

somehow the network time is drifting from standard time.

network time does not depend on system time

even if you host your own node, you should use nem network time for the transaction timestamp. The nem network time is not guaranteed to be in sync with UTC time, it is only guaranteed that all other nodes use that time to validate the timestamps.

Quick fix is set timestamp 5 seconds back in time, but I consider we should not fix this in our apps development. SDK should when create, initialize or prepare transaction.

why take so long to fix issues in nanowallet?

sdk uses system time and substract with nem_epoch which when using system time can cause some issues that's why as BR pointed out, NIS network time is independent of UTC time

If you are using directly api or sdk you should use timestamp from node. Always and not local time. /time-sync/network-time endpoint (receiveTimeStamp)

Nanowallet use already it for normal transactions. Not sure about multisig or other features. Because there was reports that it's doesn't work.

43912
why take so long to fix issues in nanowallet?

Probably because all only complains and no one checked and fixed and dev on vacation or he's busy :) It's open source project. Everyone with js knowledge can fork, prepare fix and pull request.

cryptoBeliever
Probably because all only complains and no one checked and fixed and dev on vacation or he's busy :) It's open source project. Everyone with js knowledge can fork, prepare fix and pull request.

👍

cryptoBeliever
Probably because all only complains and no one checked and fixed and dev on vacation or he's busy :) It's open source project. Everyone with js knowledge can fork, prepare fix and pull request.

Hi at all, @tongokongo suggested I should post my offer here. We are looking for a Nem-developer for our MVP at the moment who is familiar with the notarization tools of nem (Apostille etc.). We are building a register for last wills. 3-5 days work, remote possible (we are in Berlin and Munich mainly). Longterm cooperation possible as well. Anyone interested? Don´t hesitate to reach out to me for more details: [email protected] (www.eternitas.io)