Pretty accurate. Need to take into account whether the channel gets force closed, whether Taproot is used, whether SCID aliases are used, and what other info the attacker observes passively
I also found that by bolt11 implementation theres also correlation of channel id (and short channel id) and the funding tx.
And by bolt11, the short channel id is added to the invoice. So, as I understood, even with unannoinced channels in wallet like phoenix, the utxo is leaked by default with bolt11 invoices (not with bolt12 reusable invoice).
Zeus embedded lnd for example has an option to wrap invoices and permit to receive payments with bolt11 invoices that dont leaks channel-ids and node-id to the payer.
Also zeus is adding blinding paths, the same trick used in bolt12 to make bolt11 invoices private.
nostr:nprofile1qqsrf5h4ya83jk8u6t9jgc76h6kalz3plp9vusjpm2ygqgalqhxgp9gpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qzrthwden5te0dehhxtnvdakqz8thwden5te0dehhxarj94c82c3wwajkcmr0wfjx2u3wdejhgjaa6xr have I understood how things works or I'm missing something here? Its really possible to find the funding tx when exposing the channel-id in unannounced channels?
Discussion
🏛️💜