  ┌─────────────────────────────────────────────────────────┐
  │   ─┐ ┬┌┬┐┬─┐┬ ┬┌─┐┌─┐┌┬┐                                │
  │   ┌┴┬┘│││├┬┘├─┤│ │└─┐ │                                 │
  │   ┴ └─┴ ┴┴└─┴ ┴└─┘└─┘ ┴                                 │
  └─────────────────────────────────────────────────────────┘

[$ ] XMRHost — no-KYC offshore hosting :: Tor, I2P, Lokinet :: XMR / BTC / Lightning / LTC / ETH / USDT

// privacy infrastructure for operators who already speak the protocol — Iceland and Romania, no KYC, multi-crypto billing, hardened by default.

// no KYC · no DMCA-format takedowns processed · no informal data-disclosure requests honored · court orders only, via counsel

uname -a

Linux node-01 6.6.32-grsec #1 SMP PREEMPT_DYNAMIC x86_64 GNU/Linux

cat /etc/xmrhost/release

xmrhost-infra 0.1 :: no-kyc-crypto :: iceland|romania

xmrhost-cli provision --type vps-2 --location is

[ok] node provisioned in 47s

$ ls -la /

// pick a tree to descend into. each row is a real path on this site.

────────────────────────────────────────────────────────────────

drwxr-xr-x ops infra 17 2026-05-06 node/

// vps, dedicated, gpu, plus tor / i2p / lokinet — provisioning catalog

drwxr-xr-x ops docs -- 2026-05-06 docs/

// the manual — provision a hidden service, harden sshd, ksp kernel checklist

drwxr-xr-x ops notes -- 2026-05-06 notes/

// post-incident write-ups, threat-model essays, RFC-cited deep dives

-rw-r--r-- ops policy 14k 2026-05-06 why-monero

// the brand stance: BTC for offshore privacy infra is a threat-model bug

────────────────────────────────────────────────────────────────

$ xmrhost-cli list --short

// a representative slice — full catalog at /node

slug type spec $/mo notes

vps-2 vps 2c 4GBDDR4ECC $16 Workhorse offshore VPS for small projects. tor-1 tor-hidden-service 1c 2GBDDR4 $20 Pre-configured v3 onion-only hosting on a hardened tor.conf — 1 vCPU, 2 GB RAM. i2p-1 i2p-node 1c 2GBDDR4 $16 Non-exit I2P router or floodfill node with monitoring and bandwidth ledger. lokinet-1 lokinet-exit 2c 4GBDDR4 $27 Oxen-network exit node with the staking-required wallet integration.

17 total entries across 6 categories. no-kyc crypto billing (xmr / btc / lightning / ltc / eth / usdt) — see /payments.

$ grep -ri 'why monero is recommended' /etc/xmrhost

// /etc/xmrhost/policy.d/payments.md

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. /payments is the one-pager covering the actual checkout.

# tldr
xmr           = recommended (no chain-analytics surface)
btc, ltn, ltc = supported (chain-analytics surface; pay from a clean wallet)
eth, usdt     = supported (transparent ledger; convenient for stablecoin holders)
card2crypto   = not offered (KYC-equivalent on the funding side)
cash-by-mail  = case-by-case, contact /contact

$ ls /usr/share/doc/xmrhost

// curated index of the strategic surfaces. not a sitemap; /sitemap.xml is.