WabiSabi client alternatives to Wasabi/Ginger wallet

[paid2]

Does anyone know a good (light) client alternative to Wasabi/Ginger that can use WabiSabi coordinators?

I must say I'm rather shocked to not see any effort done from the community in terms of client diversity, given the only clients for WabiSabi standalone coordinators are heavy and resource-hungry Wasabi and its fork Ginger wallet. Even from a decentralization point of view, depending on just one (or two) projects doesn't seem good to me.

For example Joinstr is an Electrum plugin for CoinJoin, you benefit from Electrum's lightness and reliability without the need for a heavy wallet, could it be adjusted to work with WabiSabi given it already supports CoinJoin?
Also for other projects like https://github.com/openoms/joininbox or https://github.com/JoinMarket-Org/joinmarket-clientserver, is there any technical reason why they are never forked to support WabiSabi?

[ABCbits]

I'm not aware of such wallet. In past, some folks developed Chaincase[1] that seen as Wasabi wallet for iOS. Although i don't remember whether it use ZeroLink (CoinJoin protocol used by Wasabi Wallet 1.x) or WabiSabi protocol.

[1] https://chaincase.app/

[Kruw]

For example Joinstr is an Electrum plugin for CoinJoin, you benefit from Electrum's lightness and reliability without the need for a heavy wallet, could it be adjusted to work with WabiSabi given it already supports CoinJoin?

When you use Electrum the light way, you leak all of your addresses to third party servers, which eliminates the privacy you would have gained from coinjoining.

Also for other projects like https://github.com/openoms/joininbox or https://github.com/JoinMarket-Org/joinmarket-clientserver, is there any technical reason why they are never forked to support WabiSabi?

The WabiSabi protocol is meant as a replacement upgrade for the Zerolink protocol, JoinMarket is a unique design that existed before both of these.

[paid2]

When you use Electrum the light way, you leak all of your addresses to third party servers, which eliminates the privacy you would have gained from coinjoining.

I know that someone is already working to make a PR to Electrum to prevent automatic polling of addresses and enable poll control, which might solve the issue (-> it can easily be patched to not leak addresses to third parties), however, it doesn't mean I'm specifically interested for WabiSabi to be implemented in Electrum.

That's not really the heart of the discussion here. Electrum was more an example of how a client can be lightweight and functional, just an example of how an ideal client for WabiSabi could be, not a form of necessary client for WabiSabi.

To be clear, I would like to see it in any lightweight client form.

The WabiSabi protocol is meant as a replacement upgrade for the Zerolink protocol, JoinMarket is a unique design that existed before both of these.

Alright, but my question was, is there any technical reason why they are never forked to support WabiSabi? I don't see how your statement could be used as an answer here.

[katanic97]

-snip

Alright, but my question was, is there any technical reason why they are never forked to support WabiSabi?

I think the reason no one has forked the mcp protocols to work with Wasabi is simply because they don’t go well together. Wasabi is designed for btc's UTXO model, while mcp protocols are based on a completely different model that relies on accounts. Wasabi requires tokens and a lot of other elements that unfortunately aren’t a priority for these projects, as they’re more focused on connecting dApps with wallets rather than on coinjoin and privacy. Honestly,i think it's possible , but i think it would be a huge and demanding task.

[Kruw]

I know that someone is already working to make a PR to Electrum to prevent automatic polling of addresses and enable poll control, which might solve the issue (-> it can easily be patched to not leak addresses to third parties), however, it doesn't mean I'm specifically interested for WabiSabi to be implemented in Electrum.

That's not really the heart of the discussion here. Electrum was more an example of how a client can be lightweight and functional, just an example of how an ideal client for WabiSabi could be, not a form of necessary client for WabiSabi.

To be clear, I would like to see it in any lightweight client form.

To be clear, Electrum stops being a lightweight client once you use it privately since it requires running a full node. Wasabi and Ginger already implement the lightest private sync method available: BIP157/BIP158.

Alright, but my question was, is there any technical reason why they are never forked to support WabiSabi? I don't see how your statement could be used as an answer here.

WabiSabi and Zerolink are coinjoin protocols that involve users connecting to the server of a provider. Instead, JoinMarket users all run their own servers and connect with each other. The benefits of WabiSabi can't be applied in a straightforward way to JoinMarket's alternative architecture.