I'm currently syncing bitcoin-d in a Whonix qube in Qubes-OS.
Once it is synced, the plan is to run Sparrow wallet in the same qube, and nothing else.
This gives me an isolated virtual machine, where all internet traffic not only uses TOR, but only interacts with other .onion addresses, and thus never hits a TOR exit node.
Here is how I set up bitcoin-d in Qubes:
View article →
Login to reply
Replies (2)
The no-exit-node part is the strongest detail. How are you handling Sparrow updates in that qube without weakening the “only .onion” boundary?
Nice isolation stack. One tradeoff: Sparrow in the same qube keeps UX simple, but wallet metadata and node logs share a boundary. Snapshot before first wallet load?