What about this? https://github.com/btcontract/lnurl-rfc/blob/master/spec.md#2-withdrawing-funds-from-a-service On Monday, January 21, 2019, Rusty Russell wrote: > Francis Pouliot writes: >> Here is how I picture the ux issues taking place. >> >>1. User goes on my app to buy Bitcoin with
Francis Pouliot writes: > Here is how I picture the ux issues taking place. > >1. User goes on my app to buy Bitcoin with fiat, and opts to be paid out >via LN rather than on-chain BTC. >2. My app will tell him: "make an invoice with the following: msatoshi, >description. >3.
Francis I have seen you ask around for this. c or h are mandatory on a protocol level but I would never enforce business decisions based on their content. The same way as you would not ask a customer to plainly add his customer number in a Bitcoin transaction... Instead, you give him a unique
It isn't mandatory. It can be left blank, none of the existing wallets require users to input a description when they make an invoice. On Mon, Jan 14, 2019, 3:28 PM Francis Pouliot I'm currently in the process of building the Lightning Network payout > feature which will allow users to purchase
I'm currently in the process of building the Lightning Network payout feature which will allow users to purchase bitcoins with fiat and have the coins sent to the via LN rather than on-chain. The main issue I'm facing is ensuring that recipients generate the correct Bolt11 invoice. Having the "d"