Phoenix has become the go-to wallet for me and many others. The new splicing feature makes things a lot easier to manage, but i am a little concerned that 'only one channel ever' may result in a much bigger privacy risk.

Lightning as-is does have better sender privacy than receiver privacy, but, in this one channel model, if a snooper finds it once, they'll unambiguously (pre-taproot) be able to keep track of it through splices.

The more basic point is not dependent on splicing: Phoenix being your only channel counterparty is another big privacy tradeoff.

Reply to this note

Please Login to reply.

Discussion

Have you tried nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 embedded node w/ Olympus LSP?

No, seems interesting.

It’s really good. Startup times are a little slow but it’s running LND on device, and does all pathfinding on device as well.

And if you have channels to the LSP, all generated invoices by default (but can be disabled) are wrapped to provide better privacy by not exposing your nodes pub key to the payer.

And there’s lots more coming. Evan is cooking up some next level stuff.

I have heard people mention the possibility of combining splices and conjoins. With taproot you could increase your channel privacy onchain if some of the inputs and outputs to the splice were not controlled by your wallet or LSP.

If those coinjoin inputs paid some of the common tx fees for the splice it would even be economically beneficial for the channel parties to facilitate it.

Do you think there could be some useful mashup between LSPs and joinmarkets via splices?