It Is not about if you don’t like use another pool. Luke saying his op_return of 42bytes is standard which is a lie. His standard for his specific fork. But in reality this is an attack on the specific implementation of coinjoin because inscriptions that he does t like do not use op_return but instead taproot to do inscriptions etc..
This is an attack on zerolink protocol period.
banning tx0 (and not coinjoin tx, because op_return is not part of coinjoin but rather tx0. 46 vs oceans 42bytes
And transaction zero is what requires in zerolink protocol.
And zerolink protocol breaks all these parameters: deterministic links, unmixed change, mixing with the same participants, mixing with yourself.
Therefore ban is very targeted attack it is even worse because without tx0 one cannot enter whirlpool (coinjoin) and therefore banning a conjoin after all.
Also Tx0 fees are paid to the software publisher, not to the coordinator and no fee is paid during mixing, except fees that paid to miners. then tx goes to premix/postmix which belongs to your own derivation path.
Therefore op_return contains info allowing the server to verify that the fee was actually paid to an address., because sending to whirlpool means sending to your own hardened derivation path that you control. It's an anti-spoofing mechanism. If the fee is not seen in the blockchain then the inputs are not registered. It also allows to not use a static fee for address collection.
The use of op return in tx0 resilient to potential coordinator failure and enable decentralization - two things a coordinator database can't solve.
Kortik 🇦🇲 /
npub15l…z2796
2023-12-09 15:47:52
in reply to nevent1q…jfcy
Author Public Key
npub15lmjekxgcl8337n0gnqnrcqatwyv9arhywjkvfh0x0tfjrn2nu2sgz2796Published at
2023-12-09 15:47:52Event JSON
{
"id": "d46d7860ebd89ee93711427bcb0cb0e92979179f1116c50be590ab7bae4d4f40",
"pubkey": "a7f72cd8c8c7cf18fa6f44c131e01d5b88c2f47723a56626ef33d6990e6a9f15",
"created_at": 1702136872,
"kind": 1,
"tags": [
[
"e",
"4cdf4faec5cd535f9b3f9b6ffbc97913d6f53f58861e8a89d3afcbfd7fcd9f35"
],
[
"p",
"b7b1382ea9bd7b2420eed4db8d8333aa664c7bb7bee2208554a31a6074635e6c"
]
],
"content": "It Is not about if you don’t like use another pool. Luke saying his op_return of 42bytes is standard which is a lie. His standard for his specific fork. But in reality this is an attack on the specific implementation of coinjoin because inscriptions that he does t like do not use op_return but instead taproot to do inscriptions etc..\n\nThis is an attack on zerolink protocol period.\nbanning tx0 (and not coinjoin tx, because op_return is not part of coinjoin but rather tx0. 46 vs oceans 42bytes\nAnd transaction zero is what requires in zerolink protocol. \n\nAnd zerolink protocol breaks all these parameters: deterministic links, unmixed change, mixing with the same participants, mixing with yourself. \n\nTherefore ban is very targeted attack it is even worse because without tx0 one cannot enter whirlpool (coinjoin) and therefore banning a conjoin after all.\n\nAlso Tx0 fees are paid to the software publisher, not to the coordinator and no fee is paid during mixing, except fees that paid to miners. then tx goes to premix/postmix which belongs to your own derivation path. \nTherefore op_return contains info allowing the server to verify that the fee was actually paid to an address., because sending to whirlpool means sending to your own hardened derivation path that you control. It's an anti-spoofing mechanism. If the fee is not seen in the blockchain then the inputs are not registered. It also allows to not use a static fee for address collection.\nThe use of op return in tx0 resilient to potential coordinator failure and enable decentralization - two things a coordinator database can't solve.",
"sig": "e702eeccd24602b619fcd7a6146ea526e01b6e4e28ff8db9d7e1e13b46d0fa31dc2be17040685093345030614332477358de6777d1aaabfc3e1b7df04b5f9e5b"
}