lnproxy

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

Public Key

npub1ufdgkgz3qg4q37taye75hxwal3gq5zl7zjd97ec7gmmja84rdmyspmzcue

NIP-05 Address

_@lnproxy.org

NIP-57 Address

lnproxy@npub.cash

Profile Code

nprofile1qqswyk5typgsy2sgl97jvl2tn8wlc5q2p0lpfxjlvu0ydaewn63kajgpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqlvxtsh

Publishing to

nostr.bitcoiner.social

Author Public Key

npub1ufdgkgz3qg4q37taye75hxwal3gq5zl7zjd97ec7gmmja84rdmyspmzcue

Show more details

Last Notes

2024-06-27 14:50:06

- reply

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

2024-05-23 21:57:23

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

- 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

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

2024-01-13 05:48:35

- reply

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

2024-01-13 05:47:46

- reply

2024-01-13 05:47:10

- reply

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

2024-01-13 05:42:38

- reply

If you want to run your own relay you will need
- an lnd node
- a handful of channels with some inbound and outbound liquidity
- the lnproxy-relay binary
But if you just want your invoices wrapped, feel free to use any of the relays on https://lnproxy.org

2023-11-19 23:06:37

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-11-08 20:57:23

- reply

I think the way mutiny does it is pretty light. They have a rapid gossip sync service for users and apparently even do a little probing to clean it up. That means that the full Lightning client on the wallet side can be pretty light weight (no need to listen to gossip or check onchain etc.) with minimal trust assumptions.
@npub1mut…23vg thoughts?

2023-11-07 22:05:46

respect to whoever is requesting proxy invoices with a negative routing budget lol

2023-09-13 22:21:09

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

2023-08-06 13:49:40

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-06-30 15:34:56

- reply

This would be awesome. Things like lnproxy are really not great for tiny payments like zaps since it doubles your routing costs.

2023-06-27 22:01:51

- 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

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

$ 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

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

- 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

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

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

2023-06-04 17:09:19

- reply

🤯

2023-06-01 00:57:30

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

- 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:04:12

- reply

Better tooling for scid_alias will make unannounced channels much better too

2023-05-30 04:03:24

- reply

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

2023-05-30 03:55:53

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 16:08:14

- reply

Yes, very exciting to see some wild invoices advertising this

2023-05-28 15:53:03

- reply

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

2023-05-28 15:49:12

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

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

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-15 13:12:13

- reply

🎉

2023-05-15 13:09:45

- reply

This is an excellent idea. It also improves the privacy for the seller.
But running a local http server just to wrap an invoice is probably overkill. I reorged the code so that you can import lnproxy as a library and use it in whatever application you want. The code for a basic relay server implementation is a good example of what an application would look like: https://github.com/lnproxy/lnproxy/blob/refactor/relay/main.go

2023-05-12 18:59:44

- reply

Cool! For those curious about how the lightning part works, it just spins up a legend.lnbits.com wallet for you.

2023-05-03 21:50:32

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-05-03 21:35:49

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-28 13:17:52

- reply

🤔

2023-04-27 18:26:57

- reply

Back online!

2023-04-27 16:14:23

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

- reply

amazing!

2023-04-23 13:47:27

- reply

I think @npub1u8l…turz had a working prototype of something like this.

2023-04-23 13:46:02

- reply

I also tried that briefly and it sounds like a had a similar experience. Having to route twice makes it hard for small payments like zaps.
Anything less than ~1,000 sats will have a lot of failures.

2023-04-23 13:44:43

- reply

Awesome!
Tagging @npub1qgw…7y7n

2023-04-11 13:25:02

- reply

Why indeed, we should bug him to get on nostr.

2023-04-05 16:39:52

- reply

Congrats boys!
Very much looking forward to seeing what you bring into the world.

2023-03-21 14:31:07

- reply

Got hacked bruh, sorry

2023-03-21 14:05:40

- reply

Yes, very good point!
lnproxy is potentially risky software. I've been running it for almost a year without losing any funds but it's still possible there are bugs (why I don't keep more than a few thousand on the node). Would rather have some more technical people give it a go first. Then I'll release binaries for different OSs and architectures. Images for node distributions only once it's been vetted to death.

2023-03-20 14:35:49

Running an lnproxy relay is a privacy upgrade for any node runner. Gives you additional plausible deniability; adds some meaningful distraction traffic; and, if you configure high proxy routing fees, even provides you some no-KYC sats.
Everyone should be doing it. To add your server to the list on https://lnproxy.org today, submit a PR to change: https://github.com/lnproxy/lnproxy-webui2/blob/30050e577a8707248f7d4edf234e3489d3641595/index.html#L70

2023-03-16 15:15:13

- reply

based

2023-03-16 15:14:44

- reply

🥲

2023-03-15 14:07:17

- reply

Is this the monero guy's new shitcoin?

2023-03-15 03:57:54

- reply

lmao

2023-03-15 03:57:22

- reply

Police can force you to face unlock. They can't force you to remember your password if you happened to forget it ;).
Don't use biometrics.

2023-03-12 23:01:57

- reply

One of my favorite podcasts

2023-03-12 12:25:05

https://lnprox.org is finally back online with a *big* update:
- Change the description of your wrapped invoice
- Use any lnproxy relay
- Browser side js verifies proper payment hashes (download of a copy of the site so you know I can't do anything evil here)
- New spec driven API https://github.com/lnproxy/spec
- Nicer fonts
The node is new (had to run recovery from an SCB on the previous one and am happy to say it worked!) and has very few channels so payments will fail a lot. Open a channel!

2023-02-15 16:04:24

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

:( 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-02-13 19:36:22

Back online!
Apologies for the downtime. The server hosting the lightning node needed some love.

2023-02-13 02:12:21

https://lnproxy.org is still down. I think there's a compatibility issue between openbsd 7.2 and lnd. If anyone has got this combination running please reach out.

2023-02-11 17:11:02

- reply

Still working on it. Running your own server is hard but imo it's the only way to protect your privacy.

2023-02-10 22:20:01

lnproxy is going down for maintenance
(will only be about an hour)

2023-02-10 19:24:47

- reply

https://lists.suckless.org/dev/1609/30507.html

2023-02-09 00:28:38

😂 damn
/// Lightning TLV uses a custom variable-length integer called `BigSize`. It is similar to Bitcoin's
/// variable-length integers except that it is serialized in big-endian instead of little-endian.
///
/// Like Bitcoin's variable-length integer, it exhibits ambiguity in that certain values can be
/// encoded in several different ways, which we must check for at deserialization-time. Thus, if
/// you're looking for an example of a variable-length integer to use for your own project, move
/// along, this is a rather poor design.
https://github.com/lightningdevkit/rust-lightning/blob/e0a0add9fe0b239f8a5176ab62e7ba3cb4f541ca/lightning/src/util/ser.rs#L322

2023-02-04 20:31:24

- reply

Thanks, lnd.conf updated. I guess it'll have to wait to take effect until the next time the node goes down. (Trying to keep my uptime as high as possible).

2023-02-04 02:24:27

- reply

$ rcctl check lnd
lnd(failed)

2023-02-04 02:23:17

- reply

Thank you

2023-02-04 02:23:08

- reply

The process just died

2023-02-04 02:20:21

My lnd node just crashed. Weird thing is, there's nothing out of place in .lnd/logs/bitcoin/mainnet/lnd.log
Anyone ever experienced this?

2023-02-03 15:26:26

- reply

Apologies if you've ran into issues with lnproxy in the past few days. This error keeps popping up and the default behavior on my server is to shut everything down in such cases (in case funds are at risk).

2023-02-03 15:24:46

Has anyone ran into `local error: tls: bad record MAC` when using LNDs REST API?

2023-01-29 23:33:28

Trying snort.social

2023-01-29 21:35:54

#[1]

2023-01-22 03:57:25

plz help
https://user-images.githubusercontent.com/109770337/213899872-d15d474b-efaf-48db-8c7a-756309ceb239.png

2023-01-20 05:12:35

Bitcoiners like odell@werunbtc.com and nvk@nvk.org keep finding reasons to loudly declare that Drivechains "are never going to happen"
I don't know what will happen (these influencers don't either), but I will do whatever I can (which is not much) to help make them happen. If you care about bitcoin privacy, or scaling, or innovation, or base layer ossification, or futarchy, I urge you to please read everything you can on https://drivechain.xyz
Think for yourself, no one knows what will or wont happen. It's up to us to make Bitcoin succeed.

2023-01-13 21:16:34

OK, figured it out. acme-client couldn't talk to Let's Encrypt because my DNS resolver was misconfigured. #[0]

2023-01-13 17:34:07

Debugging issue with tls cert on https://lnproxy.org
Please use tor hidden service until it's fixed:
rdq6tvulanl7aqtupmoboyk2z3suzkdwurejwyjyjf4itr3zhxrm2lad.onion

2023-01-08 16:38:41

- reply

That would be great. I'll DM you.

2023-01-08 16:05:57

- reply

William was one of the first people to know anything about lnproxy. First reply to my intro post, back in the day when you could post in the global feed and expect everyone to see it.
Good times.

2023-01-08 02:31:32

#[1]

2023-01-07 23:23:29

- reply

Very cool question. I think that yes, if you ran the lnproxy relay you'd be able to know when invoices were settled. It would also give your users some receiver privacy.
This is very interesting, I'll send you a DM and maybe I can help you get started running a relay server.

2023-01-05 23:33:20

- reply

I have no idea, haha. Changed all of them at once but check my profile.

2023-01-05 23:30:26

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

2023-01-05 23:25:19

Whoa, added some new relays and the difference is night and day. I see some of my original follows still using the relays that were around pre-jack. Upgrade, it's worth it.

2022-12-05 15:21:06

Back online 🎉 #[0]

2022-12-05 14:36:20

lnproxy is currently offline. something caused my node to crash last night, investigating.

2022-11-30 04:42:20

- reply

Also intrigued by what's outside "the box" here.
Blockchain -> Lightning -> Drivechains?

2022-11-29 23:59:50

- reply

"perfectly private" is an interesting choice of words, the statement is true but obvious. Lightning can't be "perfectly private" just like tor can't. But it can be private enough and that's what we should be working too.

2022-11-29 23:54:57

"...maybe we never get perfectly private payment channel receiving, that could just not be in the scope of how this technology works and we could go outside of the box for that solution. I think that's a realization that people eventually had about the Blockchain, there was a lot of both wide-eyed dreaming and nasty political fighting that of course the Blockchain could handle small payments, but ultimately these claims ran up against logical limitations and that is how the Lightning Network was born."
🤔
Good thing you can *already* get some privacy with lnproxy.

2022-11-25 23:56:45

What lightning wallets generate invoices with feature flags:
- 149 "unknown"
- 49 "payment-metadata"
- 39 "unknown"
?

2022-11-22 16:17:34

- reply

You just got probed smh

2022-11-16 05:06:44

https://lnproxy.org/assets/meme.jpg
Hanging out with bitcoiners while trying to maintain opsec

2022-11-16 04:45:51

- reply

And thank you so much for paying attention to my < 10 follower twitter account so early on, really gave a nice push to keep working on the project.

2022-11-16 04:44:49

- reply

oh and here's the source -> https://github.com/lnproxy
You might be interested in -> https://github.com/lnproxy/lnproxy-cli
It was inspired by your elegant cli, but includes some additional local validations so that the whole process is a little more trustless

2022-11-16 04:40:10

- reply

--routing_msat lets you pick the routing budget. When you use the "poor man's rendevouz" you need to pre-pay the routing fee so that the proxy will be able to get the payment to its destination. I have a default routing budget but you probably know more about the destination than I do so sometimes it makes more sense to set the budget explicitly (for example some wallets, may charge unusually high routing fees).

2022-11-12 05:21:10

New damus.io/web design feels goood

2022-11-04 05:06:26

👀
https://lnproxy.org/assets/preview.gif

2022-11-02 14:31:42

- reply

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

2022-11-01 01:30:35

- reply

#[1]

2022-10-31 21:35:29

- reply

Then I've messed something up, looking into it