pull down to refresh
64 sats \ 0 replies \ @1440000bytes 8 Nov \ on: Bitcoin Ecosystem Map [October 2024] bitcoin_beginners
Thanks for adding joinstr :)
Obviously, the inputs and outputs must make sense from the privacy standpoint in terms of amounts - there can’t be 0.8 BTC output which would be easily linked to User C. The coordinator’s task would be to identify such cases and reject them.
It is even possible to do it with equal size outputs. No change amounts involved in the coinjoin transaction. No coordinator required.
Joinstr protocol allows users to create pools with custom denominations and number of peers.
In some cases it's better to avoid paying third parties in coinjoin transactions. Payjoin or Octojoin works better in such situations because less or no coordination and transactions look normal.
Joinstr will use aut-ct for sybil resistance. Recently waxwing fixed some things to make python bindings possible and will be added in next release of electrum plugin.
Joinstr actually works and has no directory nodes like joinmarket or fidelity bonds requirement.
Wasabi is the worst possible way to do coinjoin.
Isn't it non-standard to use uncompressed keys in inputs?
Kicking trolls is avoiding DoS attacks but sybil attacks are different in which attackers will participate in each round to deanonymize others.
PR authors are expected to respond to all review comments before merge: https://github.com/bitcoin/bitcoin/blob/2649e655b9203d6d08cb1a26fa4846f2c403b297/CONTRIBUTING.md#address-feedback
Maintainer (achow in this case) should step down if PR really introduced vulnerability
Please join this twitter space in a couple of hours hosted by reardencode to discuss everything related to covenant proposals: https://x.com/i/spaces/1vOxwjDqEaEJB