It is also possible to reuse fidelity bonds if some joinmarket makers want to provide liquidity in joinstr, not necessary though: https://uncensoredtech.substack.com/p/market-makers-in-joinstr
1. Protocol supports VPN and Tor. It's not necessary to use Tor. You can check the kotlin implementation for VPN usage.
2. Joinstr protocol will use AUT-CT for sybil resistance: https://github.com/AdamISZ/aut-ct?tab=readme-ov-file#worked-example
If you read the NIP for joinstr you will realize that new keys are generated for each event and pool messages use encrypted channel (shared key).
Nostr identity is never linked to coinjoin in the protocol.
Discussion
No replies yet.