Timeline for How to verify MetaMask account holder is the real owner of the address?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 9, 2022 at 13:57 | comment | added | ßiansor Å. Ålmerol | You can just use ethers.utils.verifyMessage(message,signature) | |
| Dec 22, 2021 at 13:52 | comment | added | Mike Monteiro |
on the client side, this is the code I needed to use now that window.web3 is deprecated in favor of window.ethereum: window.ethereum.sendAsync({method: 'personal_sign', params: [window.ethereum.selectedAddress, nonce], from: window.ethereum.selectedAddress}, (err, result) => { console.log('signature', result.result) });
|
|
| Oct 26, 2021 at 10:51 | comment | added | 70ny | Each nonce should be random and uniquely generated by backend, otherwise you'll have a security issue as I can use endlessly a stolen nonce signed by another user. | |
| Oct 25, 2021 at 15:36 | comment | added | 0xD1x0n | So it is considered unsecure using the same string on the front and back end instead of randomly generating it ? | |
| Oct 25, 2021 at 13:27 | comment | added | 70ny |
nonce is a random string to sign that is generated from the backend and sent to the frontend to sign. Signature is the output of a sign operation, and in our case, is generated using a wallet manager such as Metamask. These are not just web3-related concepts. I suggest you to read more about this topic, for example stackoverflow.com/questions/4751172/…
|
|
| Oct 25, 2021 at 2:09 | comment | added | 0xD1x0n | What is the difference between signature and nonce on the back end? where did signature come from?? | |
| Jun 10, 2021 at 15:32 | review | First posts | |||
| Jun 11, 2021 at 2:44 | |||||
| Jun 10, 2021 at 15:26 | history | answered | 70ny | CC BY-SA 4.0 |