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
Support metamask signatures #6
Comments
With this scheme, signing a transfer would then be as simple as:
Of course, this would be implemented as a coins.metamask_wallet function, so devs need not think about it edit: probably the "from" field could be removed by using ecrecover to get the pubkey |
It's been a long time since this issue was created, but I'm definitely interested in supporting this. I hadn't considered the way you suggest, which is interesting since the Metamask UI will display the data in a user-friendly way. But I think I would lean toward using |
Using metamask ethereum accounts and signatures will be a good form of convenience to accelerate adoption. Metamask has created an arbitrary signature scheme for signing messages, the details are a bit fuzzy for me, but given a lotion light-client app embedded in a browser, it would be convenient to support signatures from metamask. Perhaps this should be a special account type
It seems the signature is a normal secp256k1 signature of the keccak256 hash of the message which is an array of parameters. This seems quite close to the current signature scheme, or?
Details:
https://medium.com/metamask/scaling-web3-with-signtypeddata-91d6efc8b290
https://medium.com/metamask/the-new-secure-way-to-sign-data-in-your-browser-6af9dd2a1527
ethereum/go-ethereum#2940
The text was updated successfully, but these errors were encountered: