Does Luke Dashjr (npub1lh2…a9nk) understands that op_return is not a part of coinjoin txn? This rant is misleading.
You see it’s not a coinjoin ban.
Tx0 is a prep txn NOT a coinjoin txn.
one needs to understand why it is a prep tx? Unlike a payjoin(stowaway) the purpose of a coinjoin is not to hide the nature of the transaction.
It's a bit like encryption: the objective is not to hide the fact that the text is encrypted, but to make it impossible to understand.
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 your wallet never loses possession of sats.
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 01:00:23
in reply to nevent1q…gxuf
Author Public Key
npub15lmjekxgcl8337n0gnqnrcqatwyv9arhywjkvfh0x0tfjrn2nu2sgz2796Published at
2023-12-09 01:00:23Event JSON
{
"id": "2740f88992cfc14ab3de6404c4c8f16ab3cf78db02ed8bd346b675c0d37be08e",
"pubkey": "a7f72cd8c8c7cf18fa6f44c131e01d5b88c2f47723a56626ef33d6990e6a9f15",
"created_at": 1702083623,
"kind": 1,
"tags": [
[
"e",
"13e2e876a76391b8eeac0e2c8055e4268fbc5d2212dcc6926d017ba95996cd5e",
""
],
[
"e",
"fb1f50ec88908232473c4826f64d44d82889869ac8caf2c02d38f72ea39a75d8"
],
[
"p",
"02d9f5676fffc339ffe94dfab38bebe21ce117c6f1509d9922a82d454f420da2"
],
[
"p",
"fdd5e8f6ae0db817be0b71da20498c1806968d8a6459559c249f322fa73464a7"
],
[
"p",
"21b419102da8fc0ba90484aec934bf55b7abcf75eedb39124e8d75e491f41a5e"
]
],
"content": "Does nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk understands that op_return is not a part of coinjoin txn? This rant is misleading.\n\nYou see it’s not a coinjoin ban. \nTx0 is a prep txn NOT a coinjoin txn. \none needs to understand why it is a prep tx? Unlike a payjoin(stowaway) the purpose of a coinjoin is not to hide the nature of the transaction. \n\nIt's a bit like encryption: the objective is not to hide the fact that the text is encrypted, but to make it impossible to understand.\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. \nthen tx goes to premix/postmix which belongs to your own derivation path your wallet never loses possession of sats.\n\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.\n\nThe use of op return in tx0 resilient to potential coordinator failure and enable decentralization - two things a coordinator database can't solve.",
"sig": "0bd0da920c757ec05c12074425512bcfcd10863b7b6b1b9c167ec168cb1013ca5fd5d4afee3391303a8a64aea313b2326e03e8d350bce6ca0df216bbeb7a2cc9"
}