We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There are a few issues/open points with Elements/Liquid signmessage and verifymessage
signmessage
verifymessage
p2pkh
Are we ok with all of the above? or do we we want to change something?
Do we still want to support message signing in Core?
Do we want to extend message signing and verification to non-p2pkh? Do we want to do it outside Core?
FWIW, here is a summary of what some existing wallets implement
Electrum was included in the above table since it was used as a reference to add support for non-p2pkh signing to GDK.
The text was updated successfully, but these errors were encountered:
@LeoComandini Thank you so much for kick starting the discussion here and putting in the effort to create this table. Highly appreciated.
Sorry, something went wrong.
No branches or pull requests
There are a few issues/open points with Elements/Liquid
signmessage
andverifymessage
p2pkh
, see signmessage and signmessagewithprivkey don't work unless the address you use is of type legacy #976Are we ok with all of the above? or do we we want to change something?
Do we still want to support message signing in Core?
Do we want to extend message signing and verification to non-p2pkh? Do we want to do it outside Core?
FWIW, here is a summary of what some existing wallets implement
Electrum was included in the above table since it was used as a reference to add support for non-p2pkh signing to GDK.
The text was updated successfully, but these errors were encountered: