nostr relay proxy

event page

{"sig":"eb1a77f8a0c6a44d5bb3a39d4e211eb410a4cfbb6a6b59039a720afd49d95839f196cb84b2c9d0a7777c148edaeb92e6208ed56b44e920e4e58c4244f1b10ad9","tags":[],"pubkey":"fcf70a45cfa817eaa813b9ba8a375d713d3169f4a27f3dcac3d49112df67d37e","id":"543e7ad4e70fb335704127058b37e16f507aadb6ce90f4508b9e91b08ee98a38","created_at":1728415129,"kind":1,"content":"About coinjoin coordinators.\n\nThere is a difference to be made between privacy on-chain and privacy at the network level.\n\nEven if you have chain privacy you can tag the addresses with their respective ips and trace the user. Obviously this can only be done by the coordinator.\n\nThis is why Samourai and Whirpool have always sucked.\n\nWhirpool:\n\n- If you used the mobile wallet without your node, the coinjoin was useless because your public keys were exposed to the backend and with them all your past, present and future addresses.\n\n- If you used your own node or sparrow it was also of little use, since both samourai and sparrow reuse the tor circuit, they only generate a new one if you close the application, and therefore the coordinator can tag the incoming and outgoing addresses at the time of registration and ruin the coinjoin. Whirpool has never been zerolink, the coordinator knew everything.\n\nWabisabi:\n\n- It creates new connections for both input and output addresses, so the coordinator sees distinct identities, although I think it has flaws in its design due to the delay. We can consider it to be zerolink, at least they tried and were honest.\n\nJoinmarket:\n\n- Since there is no centralized coordinator it is much less important to create new tor circuits for each connection, still the coordinator (the taker) will know the ips of the incoming and outgoing addresses. I don't know if they are mitigating this in any way.\n\nJoinstr:\n\n- Use Riseup VPN for logging, everyone uses the same VPN, there is no possibility of tagging inbound and outbound addresses across relays.\n\n"}

rendered in 307.507µs