pull down to refresh

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.

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