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.
lnproxy
_@lnproxy.org
npub1ufdg...zcue
A simple lightning privacy tool.
https://simplex.chat/contact#/?v=1-4&smp=smp%3A%2F%2FUkMFNAXLXeAAe0beCa4w6X_zp18PwxSaSjY17BKUGXQ%3D%40smp12.simplex.im%2F_58pkdyvJRFpXcXCUf2U5ul70UQKe97T%23%2F%3Fv%3D1-2%26dh%3DMCowBQYDK2VuAyEASSPeBUbI370XzaUEHTpMp_xBYBa9EmZGWuTGuIM7pSQ%253D%26srv%3Die42b5weq7zdkghocs3mgxdjeuycheeqqmksntj57rmejagmg4eor5yd.onion
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.
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
View quoted note →
Node is finally back up, who wants to sell me some inbound
Is anyone else getting more stuck payments on the lightning network recently?
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.

GitHub
support proxy payments to bolt11 invoices with blinded paths · lnproxy/lnproxy-relay@f5670e7
A minimalist lnproxy relay. Contribute to lnproxy/lnproxy-relay development by creating an account on GitHub.
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..
@fiatjaf
`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...
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
If you run an lnproxy relay please shut it down ASAP (two SIGINTs with Ctrl-C) and wait for an update.