event
event copied to clipboard
c-lightning-REST: bolt12 support
https://github.com/Ride-The-Lightning/c-lightning-REST/blob/243494f4e75d9098e8b36c5fa4a9d5a545130654/controllers/offers.js
Could be a good reference: https://github.com/Ride-The-Lightning/RTL/pull/834
There is a lot of extra user benefits that BOLT12 can offer, should we just start with simply being able to generate one and later expand on all the different functionalities like subscriptions, sending invoices etc.?
Out the gate we'll let users generate offers and subscriptions with all of the params you can use on c-lightning via CLI today as c-lightning-REST has exposed them. We'll also have support to pay them and return paid and generated invoices in Activity.
We just won't have the subscription management pane set up. At the very least we need to try to encourage the implementations to do the storage of subscriptions on their layer. It would be a poor experience having one set of subscriptions in RtL, for example, and another in Zeus.
Moved below content from issue https://github.com/ZeusLN/zeus/issues/526 which was a duplicate of this.
https://github.com/Ride-The-Lightning/c-lightning-REST/pull/67/files
@kaloudis The biggest issue is that c-lightning doesn't currently store your subscriptions, it has to be handled at the app layer. This could be annoying if you are using multiple interfaces to manage your node, eg. Zeus + RtL
@tukac I can't connect to REST even after RTL is stopped and c-lightning restarted (using same REST port as RTL). I tried http+onion, https+onion and https+clearnet (my c-lightning uses both) but no success. What is correct approach?
edit: useful feature would be QR code scanner as option to enter text in fields, text scanner is sweet though :)
The easiest place to start might be to just scan and pay them.
Ideally it should also warn the user that experimental-offers
is not enabled, if they scan a bolt12 invoice.
Work is underway here: https://github.com/ZeusLN/zeus/pull/994
Got a great foundation but there's still a bunch left to do. Tried to document it all in the TODO list
Definitely interested in the blinded paths portion of BOLT12. Also, would like to use the refund/withdrawal offers to make a lightning version of the Bitcoin Fluid Dispenser (http://andyschroder.com/BitcoinFluidDispenser/2.3/) and a non-micropayments version of Distributed Charge (http://andyschroder.com/DistributedCharge/).
Would be awesome to “just” pay a bolt12 offer as an intermediate step