Wasabi client server

[ghost]

Current problem

Wasabi Wallet can only sign a CoinJoin if the computer is online, connected to the internet, and with the wallet password in memory. Privacy is optimized, when the computer does not turn off at all, as any downtime means a lower potential privacy.

Currently, Wasabi is mainly a desktop application, and thus runs on machines that are frequently turned off, reducing the time where CoinJoins can happen, and thus reducing the possible privacy benefit.

Leaving a desktop / laptop running constantly is not optimal, a headless server is much more suitable for this. The downside of course, that such a server cannot [easily] display the GUI of the application.

Proposed solution

How about, enabling a enabling Wasabi to run smoothly on headless servers?

On the server:

• Install Wasabi under-the-hood-magic [no GUI]
• Be reachable through Tor onion
• Create wallet with hot private keys on server

On the client:

• Install only Wasabi GUI
• Connect client GUI to hidden service
• No heavy computation
• Tell server what to do
• No Bitcoin private keys, only access credential to server

Why it's useful

• Higher potential privacy, as it can coinjoin all the time
• PayJoin will not fail because of downtime
• Transaction batching in low fee environment
• True Light client feel, as all computation is on server, the client GUI should be snappy
• Wasabi on mobile becomes achievable

Why now?

Wasabi 2.0 [hopefully] includes automated CoinJoin in the background + transaction batching + payments inside CoinJoin. These features excel if the user is always online.

Similar project

Sifir || Cyphernode

[BTCparadigm]

This discussion is now locked, as feature/enhancement requests are being moved to the Issues tab for further processing. Please use #9794 for future comments regarding this.
Thank you for your understanding.