> It seems to me that most users will not have nearly the same output of
"around 1 BTC"
While that would be true out of context, it depends on how you interpret it
and they interpret it really broadly: " One input might be 0.03771049 BCH;
the next might be 0.24881232 BCH, etc. "
> anyway if you
Ggood morning Antoine, and list,
> * nLocktime/nSequence
> ...
> * weird watermark (LN commitment tx obfuscated commitment number)
> ...
> LN (cooperative case):
I notice your post puts little spotlight on unilateral cases.
A thing to note, is that we only use `nSequence` and the weird
Good morning waxwing,
> ‐‐‐ Original Message ‐‐‐
> On Friday, 21 February 2020 22:17, Antoine Riard via bitcoin-dev
> bitcoin-dev@lists.linuxfoundation.org wrote:
>
> > How can a Bitcoin tranaction leak protocol usage ?
> >
> > - the output type (p2sh, p2wsh, ...)
> > - the spending
‐‐‐ Original Message ‐‐‐
On Friday, 21 February 2020 22:17, Antoine Riard via bitcoin-dev
wrote:
> How can a Bitcoin tranaction leak protocol usage ?
> * the output type (p2sh, p2wsh, ...)
> * the spending policy (2-of-3 multisig, timelock, hashlock,...)
> * outputs ordering (BIP69)
> *
