📅 Original date posted:2022-05-17
📝 Original message:
Three small updates:
1)
The most recent version of lnd-manageJ now also considers channels that
charge a base fee. In order to make this work, the worst-case scenario
is assumed (which is: a channel is used for the smallest possible amount)
and the fee rate used for the route computation is adjusted accordingly.
With the default settings (quantization 10,000sat), a channel charging a
base fee of Xsat and a fee rate of Yppm is considered with a virtual fee
rate of (Y+X*100)ppm.
This penalty is linear in the quantization amount, i.e. if you use a
quantization of 100,000sat, a base fee of Xsat only results in a
penalty of X*10ppm.
2)
I added a Dockerfile that should help with experiments.
https://github.com/C-Otto/lnd-manageJ/blob/fix-5746/Dockerfile
The only interesting requirement is that your lnd needs to be patched:
https://github.com/lightningnetwork/lnd/pull/6545
You can tweak the lnd-manageJ.conf (as demonstrated in lines 10-12), see
https://github.com/C-Otto/lnd-manageJ/blob/main/PickhardtPayments.md for
the available options.
As I was unable to figure out how to avoid TLS issues with gRPC, you
need to use "--network host" if you run lnd on localhost.
The docker image boots PostgreSQL on the default port 5432, so make sure
it is available and not in use by your host.
For your experiments please take into account that lnd-manageJ needs to
request the LN graph from lnd, which takes a few seconds. This graph is
cached for up to two minutes and, if used, refreshed before it times out.
As such, please issue a test payment (to request the graph) before
measuring the time it takes to send out any real payment.
3)
Route/hop hints provided in the payment request are now considered so that
private/virtual channels are used for the route computation. This only
works for "route hints" which contain a single hop (which should be
fine?). Each "hint" channel is added with a capacity of 50 BTC and the
algorithm is made to believe that 100% of that is available. This "known
liquidity" is not shown in the streaming NDJSON output you get via HTTP,
though, which is just a display issue which doesn't affect the route
computation.
Happy hacking,
Carsten
--
Dr. Carsten Otto
carsten at c-otto.de
https://c-otto.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20220517/6f893265/attachment.sig>;
Carsten Otto [ARCHIVE] /
npub13f…tgaqs
2023-06-09 13:06:04
in reply to nevent1q…h4ws
Author Public Key
npub13fccestrh5xf26m53n73xn5yly9z040a4n9vq30mernkj0cqszuq9tgaqsPublished at
2023-06-09 13:06:04Event JSON
{
"id": "4beccb8bf8eab7a2cd801049c5ab0a161de28e2e3f47c24ac68954ee10829889",
"pubkey": "8a718cc163bd0c956b748cfd134e84f90a27d5fdaccac045fbc8e7693f0080b8",
"created_at": 1686315964,
"kind": 1,
"tags": [
[
"e",
"8965b7a716192a7f5f8fc807387d903333f8cde5f07b362c599acf5e6453e4da",
"",
"root"
],
[
"e",
"a885388e3e4eb2cf0367aae9215a2c307f96c58fb76a285e78bd756c806df4b1",
"",
"reply"
],
[
"p",
"c63608dc19ce2134984435af610a341a43574cc779b5797fcd53139408fdcd40"
]
],
"content": "📅 Original date posted:2022-05-17\n📝 Original message:\nThree small updates:\n\n1)\nThe most recent version of lnd-manageJ now also considers channels that\ncharge a base fee. In order to make this work, the worst-case scenario\nis assumed (which is: a channel is used for the smallest possible amount)\nand the fee rate used for the route computation is adjusted accordingly.\n\nWith the default settings (quantization 10,000sat), a channel charging a\nbase fee of Xsat and a fee rate of Yppm is considered with a virtual fee\nrate of (Y+X*100)ppm.\n\nThis penalty is linear in the quantization amount, i.e. if you use a\nquantization of 100,000sat, a base fee of Xsat only results in a\npenalty of X*10ppm.\n\n2)\nI added a Dockerfile that should help with experiments.\nhttps://github.com/C-Otto/lnd-manageJ/blob/fix-5746/Dockerfile\n\nThe only interesting requirement is that your lnd needs to be patched:\nhttps://github.com/lightningnetwork/lnd/pull/6545\n\nYou can tweak the lnd-manageJ.conf (as demonstrated in lines 10-12), see\nhttps://github.com/C-Otto/lnd-manageJ/blob/main/PickhardtPayments.md for\nthe available options.\n\nAs I was unable to figure out how to avoid TLS issues with gRPC, you\nneed to use \"--network host\" if you run lnd on localhost.\n\nThe docker image boots PostgreSQL on the default port 5432, so make sure\nit is available and not in use by your host.\n\nFor your experiments please take into account that lnd-manageJ needs to\nrequest the LN graph from lnd, which takes a few seconds. This graph is\ncached for up to two minutes and, if used, refreshed before it times out.\nAs such, please issue a test payment (to request the graph) before\nmeasuring the time it takes to send out any real payment.\n\n3)\nRoute/hop hints provided in the payment request are now considered so that\nprivate/virtual channels are used for the route computation. This only\nworks for \"route hints\" which contain a single hop (which should be\nfine?). Each \"hint\" channel is added with a capacity of 50 BTC and the\nalgorithm is made to believe that 100% of that is available. This \"known\nliquidity\" is not shown in the streaming NDJSON output you get via HTTP,\nthough, which is just a display issue which doesn't affect the route\ncomputation.\n\nHappy hacking,\nCarsten\n-- \nDr. Carsten Otto\ncarsten at c-otto.de\nhttps://c-otto.de\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 195 bytes\nDesc: not available\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20220517/6f893265/attachment.sig\u003e",
"sig": "314bfa5afb8edf8c3400dc06e0917542246240a9bb406ec247d95a6fc0a2ec01b01ef68948c0fad3e58efa02ac2d823a7600f5a932755cd0bf417ebe3b9ece52"
}