Tor & VPN-friendly

The two different things "Tor-friendly" can mean

The phrase carries two claims that operators blur, and only one of them is verifiable:

1. An operator-run onion service. The site itself lives at a *.onion v3 address. Connections are end-to-end encrypted inside the Tor network, and the operator cannot be knocked offline by a regional block [1]. This is infrastructure - it either exists or it does not.
2. Terms that welcome or tolerate anonymity networks. A VPN-friendly clause means you are not breaching terms by connecting from behind a VPN or Tor exit. Tolerated is the middle: not prohibited, not welcomed. Neither tolerated nor silent terms tell you anything about Tor specifically.

No ZEC operator we track currently publishes an onion service, and exactly one documents VPN-friendly terms: Rakebit, whose own homepage states "VPN-friendly by design" (fetched 2026-10-24) [6]. The population contrast is instructive: the multi-coin brands tolerate VPNs (Cloudbet, DuckDice, FortuneJack), one documents friendliness (Rakebit), one prohibits them outright (BC.Game, by terms), while the ZEC-native micro sites that once served this lane have gone dark.

Why ZEC shifts the calculus (a little)

The honest mapping, layer by layer:

• Transparent ZEC without Tor: the operator sees your IP, your account, and the chain shows your address, amount and timing. Maximum exposure.
• Transparent ZEC with Tor: the operator loses your real IP, but the chain still publishes everything. Tor over a transparent deposit is a curtain over a window.
• Shielded ZEC without Tor: the chain leaks nothing about sender, receiver or amount, but the operator still logs your IP and account. For most "I don't want my bank or ISP to see gambling" threat models, this is the main win.
• Shielded ZEC with Tor: both layers covered - the network layer sees only Tor usage; the chain layer sees only that the shielded pool moved.

This is why the Tor hub matters even though the list is empty: the ZEC-native operators who eventually qualify here will need both layers, and the ones who get there first earn the listing.

The threat-model shortlist

• Just hide gambling from my ISP/bank: shielded ZEC + a no-logs VPN is sufficient; Tor is optional [1]. The VPN decision is covered in the VPN and OpSec guide.
• Hide from the operator: shielded deposits, dedicated email, no KYC triggers hit - and check the payout path, because a transparent payout re-identifies you regardless of Tor (shielded hub).
• Hostile local network or jurisdiction: Tor is the tool, but verify the onion address against at least two independent sources before sending anything. Gambling-site onion phishing is rampant precisely because victims have no recourse.
• Avoid operator bans for VPN use: read the terms first. A prohibited-VPN clause (BC.Game [3]) is a withdrawal-voiding clause in practice; tolerated means the reviewer may still ask questions on a large payout.

Why the near-empty state is itself the finding

The RAND Corporation's darknet research found ZEC in under 1% of cryptocurrency mentions despite its privacy credentials [3] - Zcash users historically cluster in wallets and payments, not casinos. The operator side mirrors this: no ZEC casino has invested in onion infrastructure, and VPN terms across the tracked set range from tolerated to prohibited - with a single operator-documented "friendly" (Rakebit, 2026-10-24) [6].

The moment an operator ships a verified onion service, it appears here with the address and a check date [4]. Until then: treat "Tor-friendly" claims without an onion address or quoted terms as marketing, and build your privacy from the two layers you control - the wallet (wallet guide) and the network.