To implement a coinjoins protocol you must first understand Joinmarket and the risks it mitigates.
- You do not need a complex privacy scheme at the network level because there is no centralized coordinator, you are the coordinator or someone else is the coordinator.
- Likewise you don't have tagging problems for the same reason as above.
The only problem with Joinmarket is knowing how to use it to mitigate other privacy risks and the best way is:
- Run as maker until the last mix and freeze the coins, when you go to use it run a coinjoin as payment, this way you have run both taker and maker role mitigating the risks of using both separately and also you have run enough mixes that you will be free being a maker and you will only pay for the last one and also avoid the famous “sudoku” for being taker only once with unmixed coins.
On the other hand, nostr:npub1v6qjdzkwgaydgxjvlnq7vsqxlwf4h0p4j7pt8ktprajd28r82tvs54nzyr does understand how joinmarket works and the risks it mitigates so I think #joinstr is a substantial advance and I am sorry that the community is not supporting it enough, one of the main advantages of joinstr over joinmarket is its collaborative nature that makes it cheaper for everyone, there is no extra cost, everyone benefits from the coinjoin and pay the transaction equally.
And it is so easy to implement that I can think of thousands of solutions, such as creating automatic pools in the wallets to anonymize by default without user interaction.
‚Easy to implement‘ 😉
A few days ago I recommended joinstr as an option next to Joinmarket/Jam to a friend.
He did not even managed to be successful in downloading (and installing as plugin in Electrum) it from gitlab.
That is what devs should have in mind. Clueless users.
Give them a download-button and a start-button. Then it is finally easy to implement and use. And then the support and the users will come.
Easy to implement I mean the protocol as it is really very simple, it would be easy to implement for example in Sparrow.
Regarding the UX there is only one person working.
It's a pity that a protocol like joinstr doesn't have more repercussion and others can implement them or help in the UX.
Unfortunately I'm not good at implementing nice GUIs, I'm from the old terminal school.
i think it's great that you guys are discussing this topic in my perception simple counjoins are dead for now
I don‘t think so and I still recommended JoinMarket to many.
Joinmarket is still working as usual, before wasabi or samourai it was already there and after these they are still working 🤷♂️
Buy a nostr:nprofile1qqs9df4h2deu3aae83fmet5xmrlm4w5l9gdnsy3q2n7dklem7ezmwfcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz3rhwvaz7tekd3jks6rev3ehyargv9nk66tnxe6h2dn5w43kuerk0fmnwcm4vfc8z6mgweu8j7fhdfhkjmmrxs6k66mnwg6x2cty9ehku6t0dchsz9mhwden5te0wfjkccte9ehx7um5wghxjmnxduhs5nd6j2 server and run JAM. Conjoins are alive and well
Electrum plugin is not updated since months. I was working on mobile apps.
Things would get better with time. Need more contributors.
I would like to at least be helpful with testing.
The first thing that happens when opening: Android APK: Joinstr wants to control OpenVPN and intercept all network traffic‘
Normal uneducated people (like me) would not trust this as they do not understand enough and might think this setting messes up their phone VPN settings.
It will be fixed in the next version. Tor will also be added for users that do not want to use VPN.
