📅 Original date posted:2018-11-15
📝 Original message:
Good morning Rusty,
> I want to propose a method of having reusable BOLT11 "offers" which
> provide almost-spontaneous payments as well as not requiring generating
> a BOLT11 invoice for each potential sale.
Suggest making a new BOLT document.
This would be basically a new BOLT for how to generate a BOLT11 invoice.
I suggest also to use instead the term "BOLT15 advertisement".
>
> The return lightning message
Will this be a new message that fails the HTLC, or will we reuse `update_fail_htlc` to return the data as an error?
>would contain a new bolt11 invoice (perhaps
> we optimize some fields by copying from the bolt11 offer if they don't
> appear?)
Would this require some kind of canonical ordering for tagged fields in the generated bolt11 invoice?
For t-l-v there is proposal for types to have an absolute order (from lowest-numbered to highest-numbered), which would be useful for such cases where we want to only give unique parts of something.
Bolt11 invoices have a signature so the order of the tagged fields matters.
Regards,
ZmnSCPxj
ZmnSCPxj [ARCHIVE] /
npub1g5…3ms3l
2023-06-09 12:52:51
in reply to nevent1q…uck2
Author Public Key
npub1g5zswf6y48f7fy90jf3tlcuwdmjn8znhzaa4vkmtxaeskca8hpss23ms3lPublished at
2023-06-09 12:52:51Event JSON
{
"id": "4567f5bcc04b951b17cacfc8a2f98e35a77e217329520eea1c4a39c81904826e",
"pubkey": "4505072744a9d3e490af9262bfe38e6ee5338a77177b565b6b37730b63a7b861",
"created_at": 1686315171,
"kind": 1,
"tags": [
[
"e",
"f52ed755f445a0de1c13cc6ab6ec7060fe02d8d163c9cb6cd3cc24885062d6a0",
"",
"root"
],
[
"e",
"e4c6673d746e1ecef145edf0ef45e5fde89b849543b1e1e26fa95193f314ab20",
"",
"reply"
],
[
"p",
"4505072744a9d3e490af9262bfe38e6ee5338a77177b565b6b37730b63a7b861"
]
],
"content": "📅 Original date posted:2018-11-15\n📝 Original message:\nGood morning Rusty,\n\n\u003e I want to propose a method of having reusable BOLT11 \"offers\" which\n\u003e provide almost-spontaneous payments as well as not requiring generating\n\u003e a BOLT11 invoice for each potential sale.\n\nSuggest making a new BOLT document.\nThis would be basically a new BOLT for how to generate a BOLT11 invoice.\nI suggest also to use instead the term \"BOLT15 advertisement\".\n\n\u003e\n\u003e The return lightning message\n\nWill this be a new message that fails the HTLC, or will we reuse `update_fail_htlc` to return the data as an error?\n\n\u003ewould contain a new bolt11 invoice (perhaps\n\u003e we optimize some fields by copying from the bolt11 offer if they don't\n\u003e appear?)\n\nWould this require some kind of canonical ordering for tagged fields in the generated bolt11 invoice?\nFor t-l-v there is proposal for types to have an absolute order (from lowest-numbered to highest-numbered), which would be useful for such cases where we want to only give unique parts of something.\nBolt11 invoices have a signature so the order of the tagged fields matters.\n\nRegards,\nZmnSCPxj",
"sig": "9777fb3af4f3f375d29657fc610ee842230de6163f0e8bab21ec081d39e9e2f293b16c9708098a27cfbcce2b8fcd60b4df8b43cee9c625ebbc831c0c8a884bca"
}