-
Notifications
You must be signed in to change notification settings - Fork 168
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
Use ERC-681 #103
Comments
Hi @ligi! Unfortunately I don't think ERC-681 can work for us:
I think ERC-681 is great, but I also think it solves a different problem, that is to present a payment request to a device that is online, can fetch things from the blockchain and broadcast a transaction itself. This is not the problem Signer is trying to solve. I'll close this issue, but I'm also open for a discussion around a new ERC that would standardize the behavior of the Signer. I want to pen a proposal for it, if you have any suggestions on feedback for that feel free to comment here or reach out to me by other means. Cheers! |
Actually, I had to re-read the issue. You mean just using ERC-681 format just for the address QR code? That's quite easy I think, sorry about it :). |
@maciejhirsz yes exactly - thanks. Making an ERC for the other QR-code would also be really great - but you are right 681 is not really made for this. |
In the new version account QR code now yields address in the ERC-681 format. |
Hi,
it would be great if the parity-signer could use ERC-681 in this screen:
This would help interoperability. If you are really against using ERC-681 here - please at least consider prefixing with 0x. Currently there is no context at all - at least some context would be good ;-)
The text was updated successfully, but these errors were encountered: