ls -la /
Four places to go. Each row is a real path on this site.
- node/ vps, dedicated, gpu, plus tor / i2p / lokinet — provisioning catalog
- docs/ the manual — provision a hidden service, harden sshd, ksp kernel checklist
- notes/ post-incident write-ups, threat-model essays, RFC-cited deep dives
- why-monero the brand stance: BTC for offshore privacy infra is a threat-model bug
popular VPS & server plans
A representative slice of the catalog — 17 plans across 6 categories live at /node.
No-KYC crypto billing — xmr / btc / lightning / ltc / eth / usdt. See /payments.
grep -ri 'why monero is recommended' /etc/xmrcloud
You are buying offshore-jurisdiction hosting because the threat model includes subpoena, civil-discovery process and chain-analytics correlation. Paying with BTC / LTC / ETH / USDT leaves the third surface exposed; paying with XMR closes it at the protocol layer.
The chain-analytics literature is not subtle: Möser-Soska-Christin (FC 2018) on Monero traceability, Meiklejohn et al. (IMC 2013) on BTC clustering, and the EFF/Coin Center filings around the 2024 OFAC Tornado Cash designation are the reading list. /why-monero walks the operator-side mechanics in full and explains why the brand recommends XMR while accepting every standard crypto rail.
Rails, in short: xmr is recommended (no chain-analytics surface); btc, lightning, ltc, eth and usdt are supported (transparent ledger — pay from a clean wallet, convenient if you hold stablecoins); card-to-crypto is not offered (KYC-equivalent on the funding side); cash by mail is case-by-case via /contact. The checkout itself is one page: /payments.