Zcash Node VPS Hosting

A Zcash full node validates the chain and maintains the witness data necessary for spending shielded notes. The protocol's zero-knowledge proof system (originally Sapling, now expanding to Orchard) is the cryptographic foundation that makes shielded transactions practical. The full node software, zcashd or the newer zebra implementation, downloads the blockchain, validates every block including the zero-knowledge proofs, and exposes RPC for wallet and indexing applications. The validation workload is meaningful but well within reach of a 4 vCPU, 8 GB RAM VPS with NVMe storage.

Storage is the dominant constraint. The Zcash blockchain at current size requires roughly 80 GB to 100 GB of disk, and growth is steady. Operators should provision NVMe-backed storage with at least 200 GB allocated to leave headroom for the witness cache, the RPC log and indexing data if the operator runs lightwalletd or zecwallet-lite-server alongside zcashd. AnubizHost offshore plans use NVMe across the catalog, and the IOPS profile is well above the threshold required for chain validation.

RAM usage is dominated by the UTXO cache and the proof-verification working set. 8 GB is comfortable; 4 GB is the absolute minimum and will produce visible slowdown during initial sync. Operators who plan to run a lightwalletd backend on the same VPS should provision 16 GB to leave room for the indexing layer. CPU usage is dominated by proof verification during sync and during reorg handling; modern Xeon cores handle this comfortably.

Lightwalletd is the backend service that supports light Zcash wallets such as the official mobile wallets and various third-party clients. It maintains a compact representation of the chain that lets wallets sync without downloading the full blockchain. Operating a public lightwalletd backend is a meaningful contribution to network usability because it gives wallet users an alternative to the small set of community-operated backends and improves overall service availability.

The lightwalletd backend reads from zcashd via RPC and produces the compact block representation as it indexes. Initial indexing on a synced node takes several hours and steady-state operation is light on CPU once caught up. The backend exposes a gRPC interface on a fixed port that wallets connect to. Run it behind nginx with TLS termination if you want to expose a clearnet endpoint, or advertise the onion service equivalent for privacy-minded wallet users.

Some operators run a personal-use-only lightwalletd backend that is reachable only over a private VPN or a Tor onion service known to the operator's wallets. This is a sensible setup for users who want to avoid trusting any third-party backend with their wallet's connection metadata. The VPS substrate supports this trivially and the additional latency from routing the wallet through the operator's own backend is small compared to the privacy benefit of removing the third-party backend from the picture entirely.

Zcash operators have a natural affinity for crypto payment, including settling hosting bills directly from a shielded Zcash address. AnubizHost accepts ZEC alongside BTC, ETH, XMR and USDT, and the invoice flow generates a shielded receiving address for ZEC payments where supported. There is no KYC requirement and the billing record contains only the account email and the transaction hash. Operators commonly use a Tutanota or Proton email and a fresh wallet to keep the node disconnected from any real-world identity.

At the hypervisor level we do not retain traffic captures or netflow archives for Zcash node traffic. There is no historical record of which peers the node connected to, what volumes it exchanged or how long it remained connected. The VPS disk image is encrypted at rest on the host node and there is no automatic backup unless the operator opts into the snapshot service. For nodes that hold a hot wallet for payout or staking purposes, operators should additionally encrypt the wallet file with a passphrase that is not stored on the VPS.

Jurisdiction choice for a Zcash full node is straightforward. Any offshore jurisdiction that tolerates cryptocurrency network participation is sufficient. Iceland and Romania are the defaults in our catalog and align with the broader privacy-tools hosting set. Operators who want the strongest separation from EU data frameworks pick Iceland; operators who want low latency to EU wallet users pick Romania. Both are appropriate and both have community precedent for hosting cryptocurrency network infrastructure.