-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
Bolt 12 support #103
Comments
Concept ACK |
Fwiw, I actually received a donation this way: https://twitter.com/rusty_twit/status/1420565586552057862 |
@Sjors Can you open a PR with those properties added for your profile? I can take care of displaying that info then :) |
@dennisreimann thanks! Done in #104 |
Nice! A distinction between fiat and lightning could make sense, maybe just add $ and a lightning bolt. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to support BOLT 12 offers - for single as well as recurring - I suggest adding one or two fields to the JSON:
bolt12_single
bolt12_recurring
The best practice then would be to create two offers, without an amount. Like so in c-lightning:
The site could then display these somewhere (as plain text for now, QR when mobile wallets support it).
On the donator side IIUC they use
lightning-cli createinvoicerequest [bolt12]
. This method is as yet undocumented, so yolo. I assume it returns an invoice that you then pay.There's some discussion about making this flow more automated: lightning/bolts#798 (comment)
Initially perhaps
bolt12_single
is a good start, since recurring payments are very tedious. But they would be really awesome once there.The text was updated successfully, but these errors were encountered: