lnproxy

Speaking of routing fees, they wont show up in `lncli feereport` but you can copy paste the payment hashes from the logs to a script like this to see how much you made:
```
lnproxy$ cat ./proxyfee
#!/bin/sh
{
lncli trackpayment --json $1 | jq -r '(.value_msat | tonumber) + (.fee_msat | tonumber)'
lncli lookupinvoice $1 | jq -r '.amt_paid_msat'
} |
awk '
NR == 1 {paid=$1 ; printf "paid: %0.0f\n", $1/1000}
NR == 2 {got=$1 ; printf " got: %0.0f\n", $1/1000}
END {printf "diff: %0.0f\n", (got - paid)/1000}
'
```
Run with `./proxyfee <payment hash>`

2025-05-27 15:21:46 UTC

Disclaimer: lnproxy.org now defaults to selecting a random relay from the centralized list you can find on github (one day we will query nostr for relay ads).
It's good time to post "running lnproxy-relay" and start collecting some some routing fees.

2025-05-18 01:31:47 UTC

An anon contributor helped me with some updates to the frontend at lnproxy.org.
The idea is that we want to foster an eco-system with multiple relays, so now the page shows the relay you're connectiong to more prominently. The default is still set to the realy hosted at lnproxy.org but it's much easier now to pick an alternative relay.
I'd like to eventually move to the cashu-mint-style model of fetching relays from announcements published to nostr, but since the current front end has been up for years with a couple real uses, I don't want to change the trust model until that's ready. It will add some friction to the UI, you'll be forced to pick a relay before wrapping an invoice, but it will be worth it to improve decentralization.

2025-04-17 15:48:58 UTC

- reply

🫂

2025-04-16 17:39:55 UTC

- reply

Always could use more. How much for a 0.05 bitcoin channel?

2025-04-16 13:24:26 UTC

OK, I guess I'll go with old reliable lnbig
pretty based that they still have a banner for adopting bitcoin 2021 on their site
#nevent1q…xt29

2025-04-16 03:32:05 UTC

Node is finally back up, who wants to sell me some inbound

2025-03-25 17:51:20 UTC

um
`lncli getrecovery info` is going backwards. am I cooked?

2025-01-22 17:13:21 UTC

- reply

simplex, just saw your message 🤝

2025-01-17 18:58:51 UTC

- reply

Part of this was a known issue with LND (your intuition was spot-on @npub186t…59su)
If you want to see which inflight payments are actually stuck you can do something like this:
lncli listpayments --include_incomplete |
jq -r '
.payments |
.[]
| select(.status == "IN_FLIGHT") |
[.payment_hash, .value_msat, ([.htlcs | .[] | select(.status == "IN_FLIGHT") | .route.total_time_lock ] | max)] |
@tsv
'
Then check that the max route.total_time_lock is in the future

2025-01-17 18:52:11 UTC

- reply

Issue resolved, back to normal
#nevent1q…hlj9

2025-01-16 16:40:33 UTC

Turning off new requests for the lnproxy relay hosted at lnproxy.org for a bit
Too many stuck payments, and I don't want this much in limbo. Funds are safe and wrapped invoices that have already been created will still work, but the relay will reject new requests to wrap invoices until the current batch of stuck payments is resolved.
We need PTLCs for stuckless payments asap.

2025-01-15 14:41:57 UTC

- reply

hard to say..
could evenbe the destination holding up my liquidity

2025-01-14 19:00:26 UTC

- reply

2025-01-14 18:59:53 UTC

- reply

If it's because your node is down it's not really a stuck payment

2025-01-14 18:58:49 UTC

- reply

Stuck payments are caused by other nodes in the route, so not relevant but, LND.

2025-01-14 13:18:11 UTC

Is anyone else getting more stuck payments on the lightning network recently?

2024-12-25 19:41:25 UTC

- reply

Yes, spinning up new nodes for privacy is a very good option. Better in lots of ways. But requires onchain transactions so could get expensive.

2024-12-25 19:33:24 UTC

- reply

Nothing has 100% success on lightning 😅
But your point is very good. Adding an lnproxy shunt to your route will decrease the success rate significantly. But you just need to keep trying / play with the routing fees and it will work eventually. Plus, no custodial risk.

2024-12-25 19:31:34 UTC

- reply

Exactly

2024-12-24 17:26:14 UTC

- reply

that doesn't matter. you can give lnproxy a blinded invoice, that it can parse and lnproxy will give you an unblinded bolt11 invoice

2024-12-23 19:53:23 UTC

- reply

It's up to the user to use a blinded invoice.

2024-12-23 19:07:04 UTC

The biggest limitation of using lnproxy as a tool to receive payments to your own node privately, was the fact that the relay would learn your node id.
If you run LND, the issue is now solved: the latest version of lnproxy supports blinded paths. Try it today.
https://github.com/lnproxy/lnproxy-relay/commit/f5670e7dc23ff95e37453a39985b80983c2b9ca6

2024-11-26 20:28:04 UTC

- reply

That's where the lnproxy bit is important. Try it yourself:
- make a blinded bolt11 invoices from your lnd, zeuz, or blixt node
- go to https://lnproxy.org and paste it in
- get a standard (unblinded) bolt11 invoice any wallet can pay
since the payment hash is the same on both invoices you can be certain that the lnproxy relay will have to forward the funds to you but it can't learn about your node because your invoice was blinded.

2024-11-25 21:57:04 UTC

- reply

It's not about merging anything unfortunately. Bolt12 is incredibly complex and no one has an implementation for LND, I'm sure if someone else did the implementation work, lightninglabs would merge it. What people are upset about is that lightning labs is not implementing it fast enough.

2024-11-19 00:27:02 UTC

- reply

LND merged blinded paths, but afaik doesn't pay bolt12 offers yet

2024-11-19 00:12:30 UTC

Blinded paths are the solution to lightning receiver privacy, but today many wallets can't pay bolt12 offers or bolt11 invoices with blinded paths.
If you're running lnd you can use `lncli addinvoice 1000 --blind` then wrap the invoice with lnproxy and get a private invoice that any wallet can pay.
I need to figure out lndk to make this possible for bolt12 offers too..

2024-11-01 00:26:33 UTC

- reply

Makes sense, thanks.

2024-10-31 22:14:12 UTC

- reply

What if instead, the "to restart" bit just prints on exit?
You'd have to catch unix signals too

2024-10-31 22:12:59 UTC

@npub180c…h6w6
`nak bunker` is awesome but I have one pretty big issue with it:
the `bunker: bunker://` magic string is right under the `to restart: nak bunker --sec 0000` command
seems like this might lead to people accidentally pasting their private key into web forms that ask for the bunker string...

2024-10-21 15:57:58 UTC

If you're the hero who just tried to wrap a blinded path invoice at lnproxy.org
try again, should accept your invoice now

2024-10-21 15:17:35 UTC

- reply

Some clients parse this note and just show you a little bolt11 pay button, but if were using gossip, you would see a bizzarely long invoice string.
#nevent1q…t3wl

2024-10-21 15:16:04 UTC

- reply

Makes sense, Iexepct only the latest LND can decode these.
Though, it should be possible to make some kind of little tool to transform these into something CLN can understand..

2024-10-21 07:52:42 UTC

This is a bolt11 invoice:
lnbc10u1pn3vpuhpp5ldhkcf7q3a3e5m80297parad2uq83670ctxq6lvd9y06hq7pe6nqdqqxqyz5vq5jjqqqqqqqqqqphzqgrqqqqqqqqqqzycqqqqqppxy70sqqqqq76neyv28gaglvrkusydz5mfu55pm57w96lkm5n7xrec892mncdnypsxhj07sv0ez642nzanm4xvwtvyfaag2dry5wge0r3zqpt5g2mls3xgkettxwtv433m4dxy4nus09edwkylkvcl7edkd34g4ne04pt6aez0l25w2uq6ln9k77k22g8feuenaqrhn054l67e4837qrl524vvfpdpem6tygnqvhvnex8se2g9p4py6k3rts3d94alhrlrvnsg74jw38sgqkq50d9q3d9pq38c3rrq0spn4xw8p674rgd0kmht6nltr59a2rpwqcprl2auctege5r9anf9ehghxq22ckxnuxayw5np4dqrggz4tzxf7wwktzms2p4vrjn5q4d8wt3352684yvwzq09yarnzgp5ssdn7cc3g2upq4npc608zkg2fzsd25q0efazun9fcfyjqaq35mpwx0ffgn8reggyk0xejm4nlq8w0u92em7v9v2fzn0shw46yap2zj94962gfghawq5m60khc323gt5hh3dmpnlec5jhqqqq3xgqqqzyjqv0qqqqqqqqqqqqzqqqqqq0zescsqqqqqumus7xu37ysshz7ajjrfgkrqyhkxpdgqpuyfec8dr87zle0djr7vps8pjw7qjlm68mtp7e3yvxee4y5xrgjhhyf2fxhlphpckrvevh50u0g6teqtkn87gvcy4k0eug2jcjw5urelljtt4a79dn5aqlt73lark04trlv0xr4ualhplajw4drp5xp3wqw22828zpsfff2ww5yk4n7vl5rlctupanfgpcqal0c2v2rquz2g9l0u2wtetakrh3mdmgl9eau85jwevqdljaf76xp5kmrgezu9ze2y05crup2tgzqcem6f8qhpxuajtqe3wr70fq4nyryr2tw9jr2jnnyjdrqy49lke5scnwz9wlwc649hv6e8gdv93a42dgeepfnzswqt9md2skggn0ag8ujhl6alsdm9rqrstwcxz6gzwprst0jwv4pztpy3jyua3pg639y3csqxjx9u6pd83787hfdke9z4dp399k0lkg6vc20gh6c6nmprzlqhklptfa8k7ul9fa2ulq5w03dja0gtdnvtu6fuqnvywrp88qnuc5jjqqqqqqqqqqqqxqgrqqqqqqqqqqzycqqqqqppxy70sqqqqq4amdcwjnux7wksgl86k8e55jtauajwcua9vpdggcjpujszhuhltqpsyct9s5zfy5slfty2hkdaszypydzx6yn0vjx2xhnqlzqh0hq5nn4jgkgw9k4j5lh2940r2uvzerkty4jj3dcctcj8gsda9fea0wn232qkxzumnfqkhkjt26xdykq224ntsh83d09le7ma36wehk94qx3xcjtwzha29ts0qgnr37r69d9ymt55n2j6kf594jxglznr29vdf4ffsr50s7yqg33363tkh5q6kcpwdecx7qqkfy2ycxpeax9rulxr7849mwfsfzpddlx34uz8tzjkkgny6az4gmunzsat56hrc97nd6ae0eul03xgj25j2lf7nvzka0s32q57zwyeeskeufhkx6gmlzd4yv5vtq57dpr6s6yey4wxeas28r4qz3zjqwy7s9p0vhh6pkz79qmz4tf99gwfespt9hjfqrkpk264ndlsn84653lvddxr76lkae2wfxj8axa9574fxrnl6z9ayu3v6lrup70nkkrwkedvhs9p4yqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqpq9qgqnyskrsakqpth7t5e07sm74agj8sp2yam3qdyamcack339phlx8tpah8nsnt8jqss8r7qxne3q6z04ca5wp4fh78jys8j6agk65nscgqqne07ut
Can anyone figure out the destination the payment?

2024-10-16 21:28:11 UTC

- reply

🫡 looking forward to this

2024-10-14 20:42:25 UTC

@npub1yxp…399s very curious about this:
https://github.com/supertestnet/papa-swap

2024-10-14 20:18:08 UTC

- reply

Further digging, shows that there is definitely a lightning node relaying in between:
https://github.com/supertestnet/weld

2024-10-14 19:48:34 UTC

- reply

Very cool!
Does anyone know if there an explainer for how this works somwhere?
#nevent1q…a9zm

2024-10-14 14:04:28 UTC

- reply

I think it should be possible, but some wallets cannot pay to blinded bolt 11 invoices

2024-10-14 14:02:59 UTC

- reply

LND can do both directions

2024-10-14 10:19:09 UTC

- reply

bolt 11 blinded paths are amazing
#nevent1q…2l84

2024-10-14 10:16:00 UTC

If you run lnd you and you're on the latest version you can now have pretty good receiver privacy with:
lncli addinvoice --blind
* also lnproxy now supports wrapping bolt 11 invoices with blinded paths

2024-10-14 10:14:05 UTC

- reply

interesting

2024-06-27 14:50:06 UTC

- reply

Still functional, just a blip! Thanks for alerting me.

2024-05-23 21:57:23 UTC

Payments to the original invoice for users of the demo lnproxy relay have been failing for a couple weeks. (Though with lnproxy your funds are never at risk, if the payment to the original invoice fails the payment to the proxy invoice has to be canceled).
Testing a fix now, give it a try if your proxy payments have been failing lately.

2024-05-10 15:05:32 UTC

- reply

It's like sending the funds through a lightning custodian so that your robosats counterparty doesn't learn your node id. Except lnproxy is non-custodial so you don't have to worry about your sats getting frozen along the way.

2024-02-27 23:21:02 UTC

https://github.com/lightningnetwork/lnd/issues/8199

2024-01-13 05:48:35 UTC

- reply

It's just a little relay that I'm experimenting on. Nothing malicious there.

2024-01-13 05:47:46 UTC

- reply

2024-01-13 05:47:10 UTC

- reply

Roast me: https://github.com/lnproxy/lnproxy-relay

2023-11-19 23:06:37 UTC

Question from DMs:
Why can't I wrap a zero amount invoice?
Answer:
Because then the lnproxy-relay could accept the payment to the wrapped zero-amount invoice, steal all the money, and pay just 1 sat to the original invoice to get the preimage. I want lnproxy-relays to not be able to steal so that you don't have to worry too much about who's running it.

2023-10-26 00:48:58 UTC

- reply

Check out https://github.com/lnproxy/lnproxy-address
I think what's missing is the option to send funds to an chaumian mint for small amounts (doesn't make sense to pay double routing fees for less than 10,000 sats imo) then auto-withdraw using the lnproxy periodically.

2023-10-26 00:36:55 UTC

- reply

A detailed explanation for this bug:
#nevent1q…qzx9
naddr1qqxnzd3e8qersvpj8yervd3jqgswyk5typgsy2sgl97jvl2tn8wlc5q2p0lpfxjlvu0ydaewn63kajgrqsqqqa2872qwm0

2023-09-17 16:21:32 UTC

- reply

Update: relay is back up for anyone that wants to use it, might be less reliable while I test the fix.
Will write up a full explanation once it's all settled.

2023-09-13 22:59:12 UTC

- reply

Some more details: https://github.com/lnproxy/lnproxy-relay/commit/f8942bb2acef151972688fb0eb9f6f7ec6a4cf7c

2023-09-13 22:21:09 UTC

If you run an lnproxy relay please shut it down ASAP (two SIGINTs with Ctrl-C) and wait for an update.

2023-08-30 18:42:04 UTC

- reply

This should happen

2023-08-26 03:45:58 UTC

- reply

I use bitcoind and lnd on openbsd, happy to share /etc/rc.d scripts with anyone that wants to take nvk's bounty.

2023-08-25 18:42:32 UTC

- reply

#note1tl3…8fd7
This is a very big deal.

2023-08-15 11:53:57 UTC

- reply

🤯

2023-08-14 13:43:01 UTC

- reply

I'm requesting to join the Nostrocket Identity Tree and claiming my permanym: lnproxy

2023-08-11 19:35:49 UTC

- reply

This is awesome

2023-08-11 12:29:19 UTC

- reply

Very cool, going to have too look into this today.
The code is a mess right now, decided to improve the tag indexing last night and haven't gotten it back to a working state yet, but here are the benchmarks: https://gist.github.com/lnproxy/7ac00c17c9b414962d47483461f11f5d

2023-08-09 03:50:54 UTC

Increasing the payment timeout a bit for my lnproxy relay. Seems lnd is having trouble finding good paths to destinations it hasn't interacted with before.
If your payments failed, try again, this will hopefully improve success rates.

2023-08-06 13:54:47 UTC

- reply

Tagging some relay devs @npub1cld…rps5 @npub1yxp…qud4 @npub1qqq…n47m

2023-08-06 13:49:40 UTC

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.

2023-08-02 22:41:18 UTC

- reply

$ curl -H "Accept: application/nostr+json" https://soloco.nl | jq
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 301 100 301 0 0 802 0 --:--:-- --:--:-- --:--:-- 804
{
"contact": "mailto:relay@soloco.nl",
"description": "Largest relay of the Netherlands",
"name": "Soloco",
"pubkey": "9e456e000abdf0ca118f997656326acbff875b25a64bc9c0347eab23926107ab",
"software": "git+https://github.com/hoytech/strfry.git",
"supported_nips": [
1,
2,
4,
9,
11,
12,
16,
20,
22,
28,
33,
40
],
"version": "0.9.3"
}
Care to explain yourself @npub1nez…pxt7 ?

2023-07-25 14:32:54 UTC

- reply

Yes, they've been my offsite backup solution for years.
Good for lnd backups too, just inotify and scp in a shell script.

2023-07-25 12:01:29 UTC

- reply

This is a great service. Highly recommend.

2023-07-18 14:14:25 UTC

- reply

Cool 🤩

2023-07-14 23:05:57 UTC

Humbled to be in the company of so many great projects
#nevent1q…xqnr

2023-06-27 22:01:51 UTC

- reply

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

2023-06-27 21:35:41 UTC

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.

2023-06-24 04:12:41 UTC

$ cat manifest-bc6ace3.txt
1e584be3b1bb511bc403ac29f6538b44f7ad2e345fecbc57e06fc4e7f407da5f lnproxy-http-relay-openbsd-amd64-bc6ace3
bb7c800fb30133b40591d0cc7650706ec109252ead57582d883705f50f7a9a5c lnproxy-http-relay-linux-amd64-bc6ace3
5cae1070f9272461790e55ee0594f4792955efeefe17565b916f15a3bb005da4 lnproxy-http-relay-darwin-amd64-bc6ace3

2023-06-23 15:15:22 UTC

The lnproxy.org relay is no longer rejecting invoices with feature flag 151 so if you're an electrum user, give it a try again.

2023-06-18 18:16:49 UTC

- reply

Yup, I need to rework https://github.com/lnproxy/lnproxy-address to work with zaps and then turn it back on.

2023-06-18 15:36:40 UTC

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.

2023-06-06 01:45:19 UTC

👀
https://nostr.build/i/0c707d4b4fd6c5ae2cb8afaf75383909ed0fd17cbd866cf83abbbcbddf263279.jpg

2023-06-04 17:09:19 UTC

- reply

🤯

2023-06-01 00:57:30 UTC

First binary release of the lnproxy http relay
$ cat manifest-ac94e37.txt
ba870f6032055ce02b506aee2226e1df7c0a3395613adc28230e35a1d600fbd5 lnproxy-http-relay-openbsd-amd64-ac94e37
f84048676abbdfb958acc0eba74069085350e032fd9cbea293d71fdc3bbdaabf lnproxy-http-relay-linux-amd64-ac94e37
efd633d91d4e07ffeb67a2d3f6b326a8adc67e69b0c2ed59b056912b20b69805 lnproxy-http-relay-darwin-amd64-ac94e37

2023-05-30 19:35:13 UTC

- reply

Also allowing flag 149 for trampoline routing.
This does seem to be phoenix wallet: https://github.com/ACINQ/eclair/blob/afdaf4619d9510a5f064b9cd9c308ffbf43a4878/eclair-core/src/main/scala/fr/acinq/eclair/Features.scala#L273-L282

2023-05-30 04:03:24 UTC

- reply

Yes exactly. Nice when incremental privacy improvements can be synergistic.

2023-05-30 03:55:53 UTC

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.

2023-05-28 15:53:03 UTC

- reply

Different use cases though, no?
I'm more comfortable with:
Go >> bash, python, perl, javascript, etc.

2023-05-28 15:49:12 UTC

If you've been getting errors about unsupported feature flag 25 (maybe phoenix wallet users?) on lnproxy, try again. The latest commits have a fix to allow invoices with the optional route blinding flag.

2023-05-22 13:22:44 UTC

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.

2023-05-17 17:39:36 UTC

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.

2023-05-03 21:35:49 UTC

Big thanks to @npub1x5n…dkan for finding and fixing a bug in lnproxy today. Payments should fail less often from now on!
The power of open source!

2023-04-27 16:14:23 UTC

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.

2023-04-26 23:17:24 UTC

- reply

amazing!

2023-03-09 16:43:25 UTC

- reply

I was just kidding

2023-03-09 15:59:40 UTC

- reply

Someone give this guy a dumb opinion badge

2023-03-03 21:36:19 UTC

- reply

Yes, actually. Seems the OS bug that was crashing my node has been patched: https://marc.info/?t=166694295600001&r=1&w=2
I will try to revive the node this weekend.

2023-02-15 16:04:24 UTC

- reply

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]

2023-02-15 06:25:41 UTC

:( 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.

2023-01-05 23:30:26 UTC

#[0] What does lnproxy do and who should use it?

2022-11-02 14:31:42 UTC

- reply

Nope, it works as expected with Zeus backed by LND.

2022-11-01 01:30:35 UTC

- reply

#[1]

2022-10-31 21:35:29 UTC

- reply

Then I've messed something up, looking into it