And I noticed you didn't comment on the protocol centralization risk.

What if WoS decided to deploy their own new bolt that would break cashu (just an example, substitute by any other feature you cherish)?

I saw that some weeks ago you complained Blockstream broke lnurl on CLN. Luckily, they are just a software provider, not a custodial service provider, so people can just use different LN software.

Reply to this note

Please Login to reply.

Discussion

I could've forked CLN (others already did) to make it work again. I don't get the Cashu bolt reference.

My point is that you couldn't do that if WoS was behind the change. If they controlled 99% of LN transaction volume, your fork would be incompatible with most of the network.

The same way google can just make any change to web standards they want and if Firefox doesn't follow, most websites don't work on it. By adsorbing most market share, they essentially control an open protocol.

Such a thing is only possible with big custodial operators.

They can't control 99% of LN volume. That wouldn't be LN.

That's where I disagree. Im afraid that's where we are headed 😔.

Maybe not 99% on their own, but if they buddy up with alby, strike and cashapp, they get close to it.

I don't get it. Just spin up a LN node with Phoenix and you're ok. Why would that ever be not an option.

Just spin up your own mail server and send an email to a gmail account....

Oh wait, it went to spam, or worse, it wasn't even delivered and was just filtered out.

How do you filter out LN payments?

If you are a custodian, you have unlimited power to censor.

It's a small step for them to just generate invoices to pre-approved compatible wallets.

No you don't, that's not how LN works.

In LN the receiver doesn't know the origin of a payment. Either you accept LN payments or you don't. You can't discriminate (based on sender).

gulag is internet prison !