Is there a program for testing / benchmarking relays? I've been working on a boltdb backend for github.com/fiatjaf/relayer and I want to see how it stacks up agains the sqls.
More improvements to payment reliability for lnproxy relays: routing budget and cltv delta are now estimated intelligently using the routing graph ( https://github.com/lnproxy/lnproxy/commit/6bcc8dd495d8f6c4bb4a2690e7526c9ff55cba8d ).
Please test and report any issues.
cat manifest-6bcc8dd.txt
d61d059252761a611cd5ebfedecc89746c5ad241448d4806d20a6406bb501613 lnproxy-http-relay-openbsd-amd64-6bcc8dd
889b7536b2bd1332e48fe003b5eba6e130cf94bab51b4d1b2e50f976612992ef lnproxy-http-relay-linux-amd64-6bcc8dd
1af53cb479acd904f8c6130aedaa3b4bedb77e3689a8476b0ceabc67b73c00a1 lnproxy-http-relay-darwin-amd64-6bcc8dd
More improvements to payment reliability for lnproxy relays: routing budget and cltv delta are now estimated intelligently using the routing graph ( https://github.com/lnproxy/lnproxy/commit/6bcc8dd495d8f6c4bb4a2690e7526c9ff55cba8d ).
Please test and report any issues.
Increased the balance on the https://lnproxy.org/spec relay. If you've been trying to use lnproxy for large payments, it will be more reliable now.
👀
One of the downsides of having only unannounced channels is that routing through public channels give you a lot of plausible deniability when making or receiving payments. Your counter parties can't know if it's you or just someone routing through you.
Since lnproxy works just as well with private channels (the wrapped invoice will just have routing hints), running an lnproxy relay restores this plausible deniability (as well as giving you some potential routing revenue).
Even nodes not running relays benefit, since your counter party now has to assume that it's possible you're running an lnproxy relay they don't know about.
Anyone can run an lnproxy relay and you don't have to trust them with your money.
To make this clearer, I've remove a "feature": lnproxy will no longer accept zero-amount invoices. Only invoices with amounts can be relayed trustlessly.
To whoever is trying to wrap non-mainnet invoices on lnproxy.org, getting a signet / testnet node is still on the todo list, sorry for the inconvenience.
lnproxy will be offline for a bit while lnd 16.1 starts up. Seems to be very slow when the back end node has a small mempool.
I was just kidding
The handful of people that were using lnproxy don't really have an alternative while my server is down, so if you're running this on #raspiblitz let me know and I'll add some links to your server on http://lnproxy.org let's give these people access to privacy on lightning.
@#[0]
:( lnproxy is down while I figure one heck an issue with lnd on openbsd 7.2. Never seen anything like it.
Please reach out if you're running or are willing to run a relay in the meantime. Would be good to point the webui somewhere while I fix this.
Apologies to everyone that was using my relay. It will be back as soon as possible, but it may take a few more days.
Nope, it works as expected with Zeus backed by LND.
Then I've messed something up, looking into it
I mean, does it actually make invoices that are valid for 52 years or did I fudge up the parsing / invoice expiry math?