pull down to refresh

A private lightning channel where the channel is opened using P2TR transaction can't be ID'd via block chain info as a lightning channel open, correct ?

If the private channel is cooperatively closed using the Taproot key path, it won't be known as a channel open. But if the channel is force closed using the Taproot script path, it will reveal the 2 of 2 multisig.

So, if you were to only open a private channel or two with P2TR...even if people see your public node ID when you receive sats to it, they can't easily associate the on-chain btc with your lightning node ?

Receiver privacy is dependent on Blinded Paths/BOLT12. If you use a nonblinded BOLT11 invoice, your channel's UTXO is revealed to the sender, even if it is a private channel.

@DarthCoin correct me if I'm wrong on either point.

On point 1 you are right, force closed channels are a pain.
Second point: are you afraid of who is sending you money or somebody in the middle? in 99.9*9% cases is supposed to know who is sending you money. Let's not be so paranoical.

As a general rule for a merchant that want to have more privacy for his node, I wrote this guide: https://darth-coin.github.io/merchants/operating-ln-as-merchant-en.html

Using decoy (disposable) public nodes is a simple and easy way. Also if you are good with managing the liquidity, you can take some advantage and earn some fees.

reply
52 sats \ 4 replies \ @Kruw 11 Jul
Second point: are you afraid of who is sending you money or somebody in the middle? in 99.9*9% cases is supposed to know who is sending you money. Let's not be so paranoical.

I disagree, your transaction counterparty is more of a threat to you than third parties. I don't want my neighbor to be able to search my on chain history just because I sold him some eggs or mowed his lawn.

reply

Please do that on your own payments.
Pay yourself and then try to trace it back as if you were a random payer, starting from a meaningless LN invoice.
Let me know if you find your "stash".

As I said many times here: use the damn 3 levels stash - vaults, cache, spending. Compartmentalize everything and use decoys.

reply
102 sats \ 2 replies \ @Kruw 11 Jul
Pay yourself and then try to trace it back as if you were a random payer, starting from a meaningless LN invoice.
Let me know if you find your "stash".

?... There's literally no ambiguity whatsoever with regular BOLT11 privacy. Your UTXO is shared with the sender, it's completely transparent:

If you use a nonblinded BOLT11 invoice, your channel's UTXO is revealed to the sender, even if it is a private channel.
reply

Yeah so? Don't tell me that your node have only one channel and your entire stash sits on a single UTXO.

Through that single UTXO you are passing by infinite amount of sats. That UTXO will reveal the final amount only when the channel is closed. And that is also valid if the payer have a direct channel with you, otherwise is almost impossible to find out.

Good luck finding my other stash from a meaningless UTXO that is from a channel in continuous movement.

Please do the test on yourself: send from your public node to another private node, using 2-3 hops. Then just by paying that invoice, find the real balance on the receiver UTXO, with the channel still open.

reply

I never used the word "stash"?... Not sure why you are attacking a strawman.

reply
If the private channel is cooperatively closed using the Taproot key path, it won't be known as a channel open.

It's not obvious at least. But transactions for taproot channels have distinct characteristics compared to transactions made by lnd's wallet (and probably other LN implementations). So an adversary may still be able to detect that by heuristics.

reply
2 sats \ 1 reply \ @Kruw 10 Jul

Thanks. Can you be more specific about these distinct characteristics? Fingerprints like locktime, version, & RBF flag should be able to be fixed, right?

reply

Yeah, locktime is one of them. Taproot channels set nLockTime=0, which a bunch of stuff doesn't do.

reply

thanks for this reply. I was not aware you can determine the on chain utxo just based on the invoice ( knew the node public id was exposed). is that just the channel receiving the SATs or all utxos on your lightning node?

reply