By the way, if anyone is coming to the Bitcoin Conference in Las Vegas (https://b.tc), nostr:nprofile1qqs936kc97s4k4gqjnmltljgqns0uadh08d77t5mypg3anxkneks37gpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0ds5n22nz and I have a panel where, among other things, we plan to discuss recent advancements in payjoin tech. I hope to see you there!

He also explains why LN Blinder does not actually retain the atomicity of LN payments. I take this as a mild correction, because in my video I say several times that LN Blinder payments *are* atomic. But that's not quite true.

As he points out, it is possible for the sender's computer to crash or his network to go down before he can send the preimage to the recipient. If that happens, and he doesn't know how to (or can't) fix the issue, the recipient won't actually get paid, and the sender will lose money.

A "real" implementation of LN Blinder would need some sort of "retry logic" to mitigate this issue, such that if the sender doesn't get some sort of "acknowledgement" from the recipient that the preimage was received, he keeps retrying til he gets it.

Also, I think it is worth emphasizing that a design goal was to prevent the "proxy" from stealing the sender's funds, and that goal was preserved. Once the proxy settles the sender's payment, he cannot stop the recipient from receiving the money by settling the proxy's payment. That payment is "locked in" due to the way LN works.

This is a great youtube video. Starting at about 20:13, x.com/planb_network explains how lnproxy works and how my new lightning blinder protocol works, and he even wrote his own implementation of both protocols in Polar. Good job Plan ₿ Network!

https://www.youtube.com/live/WA31M6Kmv6Y?t=1513

You can do it on Magma and Lightning Network Plus but I personally avoid using them because they require accounts whereas their competitors don't

I'd like to see an open source alternative to those where you *don't* need an account

Here's a good starting point:

nostr:nevent1qqsyp5xmsp9952f6c05lgc24kyu6pa2xwc5skw7qhszyh55lw2h0sqqpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59upzqhvnjd5jmfjxtw0z522zyd3852t7v6xmzjnz0g2ewqnk2kuk9fljqvzqqqqqqyst7v44

Looking for a cool hackathon project? Grow this list: https://supertestnet.github.io/list-of-channel-sellers/

Make an app for umbrel/start9 where node runners can advertise on nostr that they'll sell/lease you a channel and what rates they charge. Users can then buy a channel from a much bigger list.

nostr:nevent1qqs085eww2384266k9cjxgxnlyx9fjysqjkaacpqfw2pk86n0g0kjpspr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgszrqlfgavys8g0zf8mmy79dn92ghn723wwawx49py0nqjn7jtmjagrqsqqqqqpxrjtaq

The function that caps the supply is called GetBlockSubsidy()

It is currently located at line 1942 of the file validation.cpp:

https://github.com/bitcoin/bitcoin/blob/7710a31f0cb69a04529f39840196826d0b9770ab/src/validation.cpp#L1942

That's what I'm thinking. I believe mutiny wallet creates a new pubkey for every channel it requests, and the transLND project shows that you can spin up new pubkeys on LND and pretend those belong to your node, so I think its possible, at least on lnd

I doubt it. I rushed this project to the "finish line" (by my standards) because I thought of another one and now I'm psyched to do that one

(Hint: it's PTLCs)

So I probably won't do anything further with this one for quite a while

I haven't tested lspub yet but if it's nostr keys are not one time use then that ought to be fixed imo

There's no reason to use your real identity to purchase a channel -- spin up a a fake one for every purchase

Your point about needing a node pubkey anyway is a good one, I will start brainstorming a way to easily use a new node pubkey for every channel too

I think signing in with a node is essentially different from communicating via a randomly generated one-time-use nostr key

By signing in with a node, you can send notifications to my account with confidence that I will see them the next time I log in, and you can log my sessions

With a one-time-use nostr key, if you try to message me, I won't see the messages because I never sign in with that key again, and if you try to log my sessions, you'll only see one session

Oops, I meant "with" not without

I am aware of 7 accountless markets and 3 additional ones that require an account. I list them here:

https://supertestnet.github.io/list-of-channel-sellers/

The more the merrier! The next best thing to a decentralized protocol is a coordinated one without as many independent coordinators as possible

yes, but I think it just generates a keypair for that and then autosigns whatever messages it creates, so the user experiences no friction -- they don't have to copy/paste anything to and from their node, for example

The inventor says otherwise:

nostr:note17m0c9qqz7hvdwvwffu6dfwwk478wd4z3gvzuwmeguyk8v5982u8sflggw5

it does?

It launches a private exchange where you act as an escrow. Users can connect to you and place offers to buy or sell bitcoin. If there is no dispute, they hit a button that causes your node to automatically release the bitcoin to the btc buyer. If there is a dispute, you can talk to both users via encrypted messages to figure out what happened and release the btc to the aggrieved party.

Currently 4 people are running public coordinators and you can try it yourself here [note that you need a tor-compatible browser like Brave]:

http://robodexarjwtfryec556cjdz3dfa7u47saek6lkftnkgshvgg2kcumqd.onion/

You can also watch a demo here:

https://www.youtube.com/watch?v=XW_wzRz_BDI

This deserves more attention, it lowers the barrier for anyone to be an LSP and thus helps make the lightning network more robust:

nostr:nevent1qqsyp5xmsp9952f6c05lgc24kyu6pa2xwc5skw7qhszyh55lw2h0sqqpp4mhxue69uhkummn9ekx7mqzypwe8ymf9knyvku79g55ygmz0g5hue5dk99xy7s4jup8v4dev2nly54xqnp

If you want to start your own bitcoin exchange, is is easier than ever to deploy a robosats coordinator:

https://github.com/RoboSats/robosats-deploy

You can make money, virtue signal, and improve privacy all at once! Consider this a call to action

More instructions here: https://github.com/RoboSats/robosats/blob/main/setup.md