📅 Original date posted:2020-02-22
📝 Original message:‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, 21 February 2020 22:17, Antoine Riard via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> 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)
> * nLocktime/nSequence
> * RBF-signaling
> * Equal-value outputs
> * weird watermark (LN commitment tx obfuscated commitment number)
> * fees strategy like CPFP
> * in-protocol announcements [0]
>
Good list.
Another one, usually wouldn't be *protocol* as much as wallet leakage, but could be: utxo selection algorithm (which of course may be difficult to deduce, but often, far from impossible).
(Also trivial and increasingly irrelevant, but nVersion).
With regards to coinjoin in this context (I know your points are much broader), my comment is:
For existing protocols (joinmarket's, wasabi's, samourai's), in the equal-outs paradigm, I don't see much that can be done in this area.
But I would ask people to consider CoinJoinXT[1] more seriously in a taproot/schnorr world, since it addresses this exact point. With a short (not cross-block like swaps or LN setup) interaction, participants can arrange the effect of coinjoin without the on-chain watermark of coinjoin (so, steganographic). The taproot/schnorr part is needed there because multisig is required from transaction to transaction in that protocol, so doing it today is less interesting (albeit still interesting).
waxwing
[1] https://joinmarket.me/blog/blog/coinjoinxt/
AdamISZ [ARCHIVE] /
npub1nv…kqw2t
2023-06-07 18:22:57
in reply to nevent1q…sdra
Author Public Key
npub1nv7tjpn2g8tvt8qfq5ccyl00ucfcu98ch998sq4g5xp65vy6fc4sykqw2tPublished at
2023-06-07 18:22:57Event JSON
{
"id": "d8552fe67dd6f61e44c30b168decbc0cbcbf9945c54f82ab89147f70234bb65f",
"pubkey": "9b3cb9066a41d6c59c090531827defe6138e14f8b94a7802a8a183aa309a4e2b",
"created_at": 1686162177,
"kind": 1,
"tags": [
[
"e",
"6e99d759752f94733c8f71ff7a1ae8c6dc22b0d9b53b1c816d6342fb30a84f99",
"",
"root"
],
[
"e",
"22ff25faffc7a969b382b226d26b564ea83033a3310c50f894ad6295bd3fa18d",
"",
"reply"
],
[
"p",
"6485bc56963b51c9043d0855cca9f78fcbd0ce135a195c3f969e18ca54a0d551"
]
],
"content": "📅 Original date posted:2020-02-22\n📝 Original message:‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐\nOn Friday, 21 February 2020 22:17, Antoine Riard via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e How can a Bitcoin tranaction leak protocol usage ?\n\u003e * the output type (p2sh, p2wsh, ...)\n\u003e * the spending policy (2-of-3 multisig, timelock, hashlock,...)\n\u003e * outputs ordering (BIP69)\n\u003e * nLocktime/nSequence\n\u003e * RBF-signaling\n\u003e * Equal-value outputs\n\u003e * weird watermark (LN commitment tx obfuscated commitment number)\n\u003e * fees strategy like CPFP\n\u003e * in-protocol announcements [0]\n\u003e\nGood list.\nAnother one, usually wouldn't be *protocol* as much as wallet leakage, but could be: utxo selection algorithm (which of course may be difficult to deduce, but often, far from impossible).\n(Also trivial and increasingly irrelevant, but nVersion).\n\nWith regards to coinjoin in this context (I know your points are much broader), my comment is:\nFor existing protocols (joinmarket's, wasabi's, samourai's), in the equal-outs paradigm, I don't see much that can be done in this area.\nBut I would ask people to consider CoinJoinXT[1] more seriously in a taproot/schnorr world, since it addresses this exact point. With a short (not cross-block like swaps or LN setup) interaction, participants can arrange the effect of coinjoin without the on-chain watermark of coinjoin (so, steganographic). The taproot/schnorr part is needed there because multisig is required from transaction to transaction in that protocol, so doing it today is less interesting (albeit still interesting).\n\nwaxwing\n\n[1] https://joinmarket.me/blog/blog/coinjoinxt/",
"sig": "5e4135f45d25f1633e1625977973dfcfc3938b39e94dffbe71f67ee3043be2223a0b6d091d83e38611c923a500fa73c61a5e2ef64c99b0954a6bb1b72dad6ced"
}