-
Notifications
You must be signed in to change notification settings - Fork 104
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
Feature request: sign and validate #500
Comments
I would like the ability to sign messages as well, this will help decentralize Bitcoin. I have an ASIC (more on the way) and I'd like to mine with Ocean and take advantage of their Lightning payouts. I don't want to setup another Lightning node and would like to use my Phoenix wallet. Ocean's signing scheme requires the signature to be from the child address and not the xpriv/parent key. I believe the signing feature is the only missing piece for Phoenix to be compatible with Ocean LN payouts, as it already supports generating a Bolt12 offer / URI. Can this be made into a high priority request for the sake of decentralized template construction? |
Nvm, it also needs to support a description. |
I would also like to see the feature sign/verify message as it is possible with breez for example. |
De facto requirement for me |
Any updates on this? |
Hello Phoenix/ACINQ
I would like to sign and verify a message using the static on-chain address of my wallet.
Some brokers require by law to sign a message using an on-chain address as their KYC policy. If done, I then can send fiat money directly to this wallet via this broker and Phoenix will add the liquidity to my lightning wallet. Signing a message from the broker once using the static on-chain address and validating a message is a feature I would like to use in Phoenix. Can this be implemented please?
Is there already a workaround to sign a message, like importing in Sparrow/Electrum?
The text was updated successfully, but these errors were encountered: