📅 Original date posted:2021-09-21
📝 Original message:
On Tue, Sep 21, 2021 at 3:06 PM fiatjaf <fiatjaf at gmail.com> wrote:
> I would say, however, that these are two separate proposals:
>
> 1. implementations should expose a "stateless invoice" API for receiving
> using the payment_secret;
> 2. when sending, implementations should attach a TLV record with encoded
> order details.
>
> Of these, 1 is very simple to do and do not require anyone to cooperate,
> it just works.
>
> 2 requires full network compatibility, so it's harder. But 2 is also very
> much needed otherwise the payee has to keep track of all the invoice ids
> related to the orders they refer to, right?
>
Not completely sure what you mean by full network compatibility, but a
network-wide upgrade including all routing nodes isn't needed. I think to
do it cleanly we need a new tag for bolt11 and node implementations that
carry over the contents of this field to a tlv record. So senders do need
to support this.
> But I think just having 1 already improves the situation a lot, and there
> are application-specific workarounds that can be applied for 2 (having a
> fixed, hardcoded set of possible orders, encoding the order very minimally
> in the payment secret or route hint, storing order details on redis for
> only 3 minutes and using lnurlpay to reduce the delay between invoice
> issuance and user confirmation to zero, and so on).
>
A stateless invoice API would be a great thing to have. I've prototyped
this in lnd and if you implement it so that a regular invoice is inserted
'just in time', it isn't too involved as you say.
Joost
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20210921/e683619e/attachment.html>;
Joost Jager [ARCHIVE] /
npub1as…wfqmx
2023-06-09 13:03:50
in reply to nevent1q…hefm
Author Public Key
npub1aslmpzentw224n3s6yccru4dq2qdlx7rfudfnqevfck637cjt6esswfqmxPublished at
2023-06-09 13:03:50Event JSON
{
"id": "9a983138a728866a6c885b4aa00461636f98efb6b92a81cb0dd6ee58a4d312f8",
"pubkey": "ec3fb08b335b94aace30d13181f2ad0280df9bc34f1a99832c4e2da8fb125eb3",
"created_at": 1686315830,
"kind": 1,
"tags": [
[
"e",
"e4e7ab359e7c5557c58c3d4556f5e2b70b0dd56c221200159af6ed9115c412d1",
"",
"root"
],
[
"e",
"e818ecbaa0dd7b600089af9d0de8ffae0b6d0a0dfc78dc41bf43cf8931705f61",
"",
"reply"
],
[
"p",
"628ddabe0b1ed9de25481d11295311203e45f47e0c59aacd287db3acbd96632c"
]
],
"content": "📅 Original date posted:2021-09-21\n📝 Original message:\nOn Tue, Sep 21, 2021 at 3:06 PM fiatjaf \u003cfiatjaf at gmail.com\u003e wrote:\n\n\u003e I would say, however, that these are two separate proposals:\n\u003e\n\u003e 1. implementations should expose a \"stateless invoice\" API for receiving\n\u003e using the payment_secret;\n\u003e 2. when sending, implementations should attach a TLV record with encoded\n\u003e order details.\n\u003e\n\u003e Of these, 1 is very simple to do and do not require anyone to cooperate,\n\u003e it just works.\n\u003e\n\u003e 2 requires full network compatibility, so it's harder. But 2 is also very\n\u003e much needed otherwise the payee has to keep track of all the invoice ids\n\u003e related to the orders they refer to, right?\n\u003e\n\nNot completely sure what you mean by full network compatibility, but a\nnetwork-wide upgrade including all routing nodes isn't needed. I think to\ndo it cleanly we need a new tag for bolt11 and node implementations that\ncarry over the contents of this field to a tlv record. So senders do need\nto support this.\n\n\n\u003e But I think just having 1 already improves the situation a lot, and there\n\u003e are application-specific workarounds that can be applied for 2 (having a\n\u003e fixed, hardcoded set of possible orders, encoding the order very minimally\n\u003e in the payment secret or route hint, storing order details on redis for\n\u003e only 3 minutes and using lnurlpay to reduce the delay between invoice\n\u003e issuance and user confirmation to zero, and so on).\n\u003e\n\nA stateless invoice API would be a great thing to have. I've prototyped\nthis in lnd and if you implement it so that a regular invoice is inserted\n'just in time', it isn't too involved as you say.\n\nJoost\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20210921/e683619e/attachment.html\u003e",
"sig": "5ff21ce196e5993f519bb5f42cda5e5f3b3e8615e1c9565f11406ca50ed7792b049426808303512ad95c981ca043a0f28115d2ce93e3b2f7fc3eac03e422cdff"
}