Oddbean new post about | logout
▲ ▼
. | 11 months ago (raw) | root | parent | reply | flag 
 All other coinjoin implementation besides whirlpool are not mathematically deterministic and are currently being demixxed by chain analysis 

the use of op return allows for TxO which ensures fees are paid, acts as a sybil attack defense and creates the unified values 

it isn’t buggy, broken or in need of a fix — people who have never coded a successful coinjoin sure seem to have a lot to say about how they should work
▲ ▼
TheGuySwann | 11 months ago (raw) | root | parent | reply | flag +2 
 Where are you getting the idea that I’ve made any of these arguments. Please stop arguing with me over a conversation you had with someone else.

For one, I don’t know much about the methodology and made no claim to whether it was good/bad or better/worse than anything else. I said the fact that Samourai coinjoins got filtered wasn’t because they were trying to filter coinjoins. Which based one everything we know, is perfectly true.

If their method is better, then that’s cool 👍🏻

As I prefaced all of this, I think it’s a bad way to go about this filtering and the OP_RETURN issue is moot. Luke is just especially stubborn, imo.

On the issue of JPEGS, I think you could safely filter OP_FALSE txs which are necessary to make all the JPEG info specifically meaningless, but still be able to include it. Which, as I understand it, means it can be filtered safely, knowing that none of the Txs with that data mean anything anyway. This filters JPEGS for clients that want to, and shouldn’t drag any privacy tools with it.
▲ ▼
btconboard #LNHANCE or #CTV | 11 months ago (raw) | root | parent | reply | flag 
 Apologies if I misunderstood