š
Original date posted:2019-01-21
š Original message:
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 <rusty at rustcorp.com.au> wrote:
> Francis Pouliot <francis at satoshiportal.com> 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. He will go in his wallet and type msatoshi, description.
>> 4. It's likey he won't pay too much attention, make a typo in
>> description, leave it blank, write his own description, etc.
>> 5. When my app tries to pay, we of course have to decode his bolt11
>> first.
>> 6. We have to have some logic that will compare the "h" or "d" that we
>> instructed him to create and the "h" or "d" that we got from the
decoded
>> bolt 11 (which is an extra hassle for devs)
>> 7. In the cases there they are not the same, we need to instruct the
>> user to create a new bolt 11 invoice because the one he created was
not
>> correct.
>
> Yes, there's a missing "give me an invoice" API for this kind of push
> payment. yalls.org has the same problem: there's a clumsy API where you
> give them an invoice and it pays it if you have that much.
>
> lninv: URL? Description, min and max amounts, submission URL? Ideally
> the browser would reach out to the wallet to get an invoice and do the
> submission itself (preserving sessions, cookies, etc) but I'm not sure
> how that part of the stack works?
>
> There was talk of something similar in Adelaide, but I hadn't
> appreciated the concrete problem at the time :(
>
> Cheers,
> Rusty.
> _______________________________________________
> Lightning-dev mailing list
> Lightning-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20190121/3b8879a1/attachment.html>;
Giovanni P [ARCHIVE] /
npub128ā¦8za72
2023-06-09 12:53:58
in reply to nevent1qā¦c4wg
Author Public Key
npub128eajqln247s6ucvlgmgdu6v82zcthcl2e6d8rxw5arvxuej42qsf8za72Seen on
wss://relay.nostr.bandPublished at
2023-06-09 12:53:58Event JSON
{
"id": "774ca95bc7df6a53d01c703a425fbdfd8cb5f10a4ae2f92ab156bd9797c58e7b",
"pubkey": "51f3d903f3557d0d730cfa3686f34c3a8585df1f5674d38ccea746c37332aa81",
"created_at": 1686315238,
"kind": 1,
"tags": [
[
"e",
"519a7a8c86eac72a23dc644543eb562443536845963ecffa2a6e73592013b70b",
"",
"root"
],
[
"e",
"66501bd17afd854ce473503e33787d8757814a6933e798e037899a1469a13b99",
"",
"reply"
],
[
"p",
"13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425"
]
],
"content": "š
Original date posted:2019-01-21\nš Original message:\nWhat about this?\nhttps://github.com/btcontract/lnurl-rfc/blob/master/spec.md#2-withdrawing-funds-from-a-service\n\nOn Monday, January 21, 2019, Rusty Russell \u003crusty at rustcorp.com.au\u003e wrote:\n\u003e Francis Pouliot \u003cfrancis at satoshiportal.com\u003e writes:\n\u003e\u003e Here is how I picture the ux issues taking place.\n\u003e\u003e\n\u003e\u003e 1. User goes on my app to buy Bitcoin with fiat, and opts to be paid\nout\n\u003e\u003e via LN rather than on-chain BTC.\n\u003e\u003e 2. My app will tell him: \"make an invoice with the following:\nmsatoshi,\n\u003e\u003e description.\n\u003e\u003e 3. He will go in his wallet and type msatoshi, description.\n\u003e\u003e 4. It's likey he won't pay too much attention, make a typo in\n\u003e\u003e description, leave it blank, write his own description, etc.\n\u003e\u003e 5. When my app tries to pay, we of course have to decode his bolt11\n\u003e\u003e first.\n\u003e\u003e 6. We have to have some logic that will compare the \"h\" or \"d\" that we\n\u003e\u003e instructed him to create and the \"h\" or \"d\" that we got from the\ndecoded\n\u003e\u003e bolt 11 (which is an extra hassle for devs)\n\u003e\u003e 7. In the cases there they are not the same, we need to instruct the\n\u003e\u003e user to create a new bolt 11 invoice because the one he created was\nnot\n\u003e\u003e correct.\n\u003e\n\u003e Yes, there's a missing \"give me an invoice\" API for this kind of push\n\u003e payment. yalls.org has the same problem: there's a clumsy API where you\n\u003e give them an invoice and it pays it if you have that much.\n\u003e\n\u003e lninv: URL? Description, min and max amounts, submission URL? Ideally\n\u003e the browser would reach out to the wallet to get an invoice and do the\n\u003e submission itself (preserving sessions, cookies, etc) but I'm not sure\n\u003e how that part of the stack works?\n\u003e\n\u003e There was talk of something similar in Adelaide, but I hadn't\n\u003e appreciated the concrete problem at the time :(\n\u003e\n\u003e Cheers,\n\u003e Rusty.\n\u003e _______________________________________________\n\u003e Lightning-dev mailing list\n\u003e Lightning-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20190121/3b8879a1/attachment.html\u003e",
"sig": "51b079969067b39c4ffac89c7e86f3bab68f5aaee1fafe2ba61fa73cec2a069e0a272dff8489ba4a2d873cc42adaf4ba6c32521a8151f25f4d58080502d357b1"
}