📅 Original date posted:2018-10-08
📝 Original message:
Resending due to ML bugs....
On a related note, it would be nice to get some clarity on appropriate
usage of the r= field here.
The way I had implemented it initially was that if an invoice had an r=
field any publicly-discovered last-hop routes would be ignored as the r=
data is most likely more up-to-date than any public route rumor information.
However, if it's only used as a hint and only one or two out of
potentially many channels are included in it, that may make little sense.
Not really sure what the appropriate guidance should be, probably
something like SHOULD prefer to use invoice-r=-provided-hints over
publicly-discovered routes however MAY use other last-hops in case a
substantially better route is known?
Matt
On 09/19/18 22:10, Rusty Russell wrote:
> Hi all,
>
> I'm considering a change to c-lightning, where `invoice` would
> automatically append an 'r' field for a channel which has sufficient
> *incoming* capacity for the amount (using a weighted probability across
> our peers).
>
> This isn't quite what 'r' was for, but it would be a useful
> hint for payment routing and also potentially for establishing an
> initial channel. This is an issue for the Blockstream Store which
> deliberately doesn't advertize an address any more to avoid
> centralization.
>
> Thoughts welcome!
> Rusty.
> _______________________________________________
> Lightning-dev mailing list
> Lightning-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
>
Matt Corallo [ARCHIVE] /
npub1e4…jxmcu
2023-06-09 12:51:32
in reply to nevent1q…w8px
Author Public Key
npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcuPublished at
2023-06-09 12:51:32Event JSON
{
"id": "ae9458eb7e30e84041835986b42f302adad8a195bf472a50125d07ecbbf5f04a",
"pubkey": "cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba",
"created_at": 1686315092,
"kind": 1,
"tags": [
[
"e",
"34f972ce1f660f3d3f1ba8a09ccfbd7c4d82ba2dba504bf244e97255e67fae9d",
"",
"root"
],
[
"e",
"24edc90326be7851c72acc598b9ca350fca7f77d43fafca37cd37bf1a075b8d6",
"",
"reply"
],
[
"p",
"208e7a4699791a0264a0298ffa60456c51ac8d8992096a1b67389965eccc82ff"
]
],
"content": "📅 Original date posted:2018-10-08\n📝 Original message:\nResending due to ML bugs....\n\nOn a related note, it would be nice to get some clarity on appropriate\nusage of the r= field here.\nThe way I had implemented it initially was that if an invoice had an r=\nfield any publicly-discovered last-hop routes would be ignored as the r=\ndata is most likely more up-to-date than any public route rumor information.\nHowever, if it's only used as a hint and only one or two out of\npotentially many channels are included in it, that may make little sense.\n\nNot really sure what the appropriate guidance should be, probably\nsomething like SHOULD prefer to use invoice-r=-provided-hints over\npublicly-discovered routes however MAY use other last-hops in case a\nsubstantially better route is known?\n\nMatt\n\nOn 09/19/18 22:10, Rusty Russell wrote:\n\u003e Hi all,\n\u003e \n\u003e I'm considering a change to c-lightning, where `invoice` would\n\u003e automatically append an 'r' field for a channel which has sufficient\n\u003e *incoming* capacity for the amount (using a weighted probability across\n\u003e our peers).\n\u003e \n\u003e This isn't quite what 'r' was for, but it would be a useful\n\u003e hint for payment routing and also potentially for establishing an\n\u003e initial channel. This is an issue for the Blockstream Store which\n\u003e deliberately doesn't advertize an address any more to avoid\n\u003e centralization.\n\u003e \n\u003e Thoughts welcome!\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",
"sig": "e6f3470ca630473b0b3dd9529dc551cd9537ee9946bc24433a96cf588609e550ce3c7bba2905342f4e6d008f7a11f874be0429e28f165bbd9472becdbff6d474"
}