Isolated by family
Each blockchain family has its own isolated circuits. Prices and swaps have their own too. All EVM networks count as one family.
Tor wallet
Balances, prices, swaps and broadcasts all leave through an embedded Tor client. You install nothing extra and set nothing up. If Tor is not ready, Kyro stops.
The client
Kyro embeds Arti, the Tor client from The Tor Project. It starts in the background when the app opens, and the wallet shows its state.
Circuits
A server or an exit relay cannot link your Bitcoin lookup to your Solana lookup through the circuit, because they never share one.
Each blockchain family has its own isolated circuits. Prices and swaps have their own too. All EVM networks count as one family.
Bitcoin lookups go to mempool’s onion service. No exit relay is involved, so no relay sees the hostname or the volume.
A stream refused by a closed circuit is retried on a new one. A refusal on one family no longer moves the others. It never falls back to clear.
Who sees what
In Tor mode, the default. This table comes from the network document in the repo, which lists every server by name.
| Party | Sees | Does not see |
|---|---|---|
| Your internet provider | That you use Tor | The hosts you reach, your addresses, your amounts |
| First relay | Your IP address | The destination and the request |
| Middle relay | Two other relays | You, and the request |
| Exit relay | The hostname and the volume | You, and the content (TLS runs up to the server) |
| Blockchain server | The addresses and transactions requested, from a Tor exit | Your IP address |
| Monero node | Blocks downloaded and transactions you publish | Your IP, your addresses, your view key |
| Price server (CoinGecko) | The coins and currency requested | Your IP address, your addresses |
| Swap provider | Tokens, amounts and the recipient address | Your IP address |
With Tor off, every server sees your IP address and your internet provider sees the hosts. Privacy policy
Fails closed
If Tor is not ready within 60 seconds, the request fails with TOR_UNAVAILABLE. Nothing goes out in the clear, and there is no automatic fallback.
Leaving Tor is your decision. Kyro asks in a native system window drawn outside the interface, so a compromised page cannot turn Tor off without you.
Limits
Tor is one layer. It hides your network location. These things stay true with it on.
The server you query sees the addresses and transactions you ask about. To avoid that, use your own node.
Most chains publish every transfer. Tor hides your IP, and your addresses remain linked to each other on chain when you link them.
Swap APIs see the tokens, amounts and recipient. Exolix sees your source and destination addresses, so it can link those two accounts.
The signed update check and the anonymous weekly count. Both go over Tor and both can be turned off.
Questions
No. Kyro embeds its own Tor client, Arti, from The Tor Project. It starts in the background when the app opens.
Yes. It is your choice in Settings, confirmed in a native system window, so a compromised interface cannot switch it off for you. In clear mode, servers see your IP address.
No. Tor hides who is asking. It does not hide what is asked: the server you query still sees the addresses and transactions you look up, and public blockchains stay public.
Requests take three relays instead of a direct path, and some servers refuse some exit relays. Kyro retries on a new circuit, and each blockchain shows as soon as it answers.
Paste plain bridge lines in Settings, under Privacy. Kyro then connects only through them and stays offline if none answers. obfs4 and other disguised bridges do not work yet, so a censor that inspects traffic can still block a plain bridge.
Yes. When Tor is on, your custom servers use the isolated circuits of their own blockchain family.
The problem in plain words: your IP and your addresses in the same log line.
A desktop Monero wallet that scans blocks on your machine.
Tor covers the network. This covers the vault and the signature.
Version 1.0.7 · Free · Windows, macOS and Linux