Replies: 1 comment 2 replies
-
It depends a lot on your use case, but if this is for signing in, a common technique might be to use the current timestamp, which can also be verified by a server when checking the signature to make sure old signatures are not used, and that the signing occurred within some timeframe. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Richard @ricmoo
I have the above code.
Now, in the smart contract, I got the
ecrecover
stuff.I am wondering what I can put instead of
nonceHere
so that replay attacks would never happen. I don't want to be storing something on my own server so that whenever I generate new random nonce, i check if i already got generated on my server.What would be the
ethers.js
way of so secure mechanism in this case ?Beta Was this translation helpful? Give feedback.
All reactions