CryptoServers

Bitcoin VPS 主机—— 以 BTC 支付,无 KYC

A Bitcoin VPS is a virtual private server you can buy with on-chain BTC or a Lightning invoice — no card, no PayPal, no payment processor in the loop. Cryptoservers issues a fresh deposit address per invoice (BIP-32 HD), absorbs the network fee, and provisions your VM on the first confirmation (~10 minutes on Bitcoin mainnet). Five tiers from $16.99/mo, four offshore jurisdictions, no KYC.

1 次确认即部署 支持 Lightning 每张账单使用全新地址 No KYC, no logs
Bitcoin VPS hosting — pay in BTC and Lightning

Bitcoin 支付流程 ——六个步骤

From "click deploy" to root SSH on a freshly provisioned VPS, in six discrete steps. Step 4 is on-chain (10 min) for BTC or sub-second for Lightning; everything else is measured in seconds.

  1. 1Pick a plan and select Bitcoin. Five VPS tiers, four offshore regions. The deploy form shows BTC as the first option in the coin selector.
  2. 2已生成全新充值地址。 We derive a new receive address from a BIP-32 HD path on our hot wallet. The address has never been used and will never be reused — no clustering for chain-analysis tools to lock onto.
  3. 3Pay on-chain or via Lightning. For invoices < $200 we also display a BOLT-11 Lightning invoice; pick whichever your wallet supports. Send the exact amount; we absorb the network fee.
  4. 4First confirmation (~10 min on-chain, instant on Lightning). Bitcoin block time averages 10 minutes (Difficulty Adjustment Algorithm targets a 10-minute average). One block is sufficient for VPS-tier amounts. Lightning settles as soon as the HTLC resolves — typically under 5 seconds.
  5. 5编排器部署虚拟机。 In parallel with the broadcast, the orchestrator pre-stages the disk image and the network ACLs. By the time the block confirms, the VM is already booting.
  6. 6SSH 凭据已通过邮件发送。 IPv4, IPv6, root password (or your provided pubkey) and a one-time panel-claim link land in your inbox. Median total time, broadcast to root login, is under twelve minutes for on-chain BTC and under two minutes for Lightning.

BTC、Lightning, 以及其他币种

何时使用哪种支付渠道。我们接受七种币种;以下是 VPS 级别账单手续费、结算时间和隐私属性的平铺对比。

支付渠道 结算 网络手续费 链上隐私 适用场景
BTC on-chain~10 min1–10 sat/vB (we absorb)匿名,公开 UTXO 图任意金额,尤其 > $200
BTC Lightning< 5 s微小路由费(我们承担)链下跳转,来源不上链小额账单,快速迭代
XMR (Monero)~2 min~0.0002 XMRRingCT + 隐身地址(私密)隐私优先买家——请见 /monero-vps/
LTC (Litecoin)~2.5 min< 1 cent匿名,公开账本快速确认,低手续费
ETH~30 s (1 conf)$0.30–$3公开账本,账户模型已在 ETH 生态的买家
DASH~3 s (InstantSend)< 1 cent公开,可选 PrivateSend快速零售式支付
BCH / DOGE~1–10 min< 1 cent匿名,公开账本持有任一币种的买家

In-depth privacy comparison: <a href="/zh/guides/bitcoin-vs-monero-payments/">Bitcoin vs Monero payments</a>.

套餐对照表: Bitcoin 买家

Same five tiers as the main /vps/ page, laid out as a single comparison table for the BTC-paid checkout. Prices quoted in USD, converted to BTC at the spot rate when your invoice is generated.

级别 vCPU RAM NVMe 带宽 价格
入门版
AMD EPYC 7443P
24 GB DDR4 ECC60 GB1 Gbps 不限流量$16.99/mo
成长版
AMD EPYC 7443P
48 GB DDR4 ECC120 GB2.5 Gbps unmetered$26.99/mo
商业版
Intel Xeon Gold 6430
616 GB DDR5 ECC240 GB5 Gbps unmetered$39.99/mo
专业版
Intel Xeon Gold 6430
824 GB DDR5 ECC400 GB5 Gbps unmetered$54.99/mo
扩展版
AMD EPYC 9454P
1232 GB DDR5 ECC640 GB10 Gbps 不限流量$69.00/mo
部署并以 BTC 支付

运行 Bitcoin 节点 在 Bitcoin VPS 上

Sizing for full nodes, pruned nodes and Lightning routing nodes — three different workloads with very different storage and CPU profiles.

完整节点(未裁剪,含 txindex)。 Mainnet plus indexes is approximately 600 GB as of mid-2026, growing roughly 80 GB per year. RAM: 8 GB minimum, 16 GB comfortable for index lookups. CPU: a single fast core (initial block download is mostly serial); ongoing operation is light. Recommended tier: <strong>Pro</strong> (400 GB) if you can prune <code>txindex</code>, otherwise <strong>Scale</strong> (640 GB) — or jump to a small dedicated server. Initial sync from cold takes 8–24 hours on Gen4 NVMe.

裁剪节点。 Bitcoin Core supports pruning the historical block files while keeping a fully validated chainstate. With <code>prune=8000</code> (8 GB block storage) plus a few GB of UTXO set and chainstate, the on-disk footprint sits around 8–12 GB. Recommended tier: <strong>Starter</strong> (60 GB NVMe) is fine. Useful for wallets, mempool monitoring, fee-estimation oracles and personal Lightning nodes.

Lightning 路由节点。 Storage is negligible (channel state + gossip is a few hundred MB). RAM around 2–4 GB. CPU light. Bandwidth is the variable: a busy routing node moves a steady 5–20 Mbps of gossip and HTLC traffic. Recommended tier: <strong>Starter</strong> or <strong>Growth</strong>. Pair with a Bitcoin Core full node on the same box (Scale tier) or run the Lightning node alongside a remote Core node (cheaper).

Port hygiene: open <code>8333</code> for inbound P2P (more peers help the network and improve your own gossip), <code>9735</code> for Lightning channel listening if you want inbound channels, and <em>do not</em> expose RPC port <code>8332</code> publicly — bind it to localhost or a Tailscale interface and proxy as needed.

地址重用与 隐私卫生习惯

Bitcoin is pseudonymous, not anonymous. Every transaction is public forever; what you do at the edges (wallet hygiene, address strategy, change handling) determines whether your activity remains a forest of unrelated UTXOs or collapses into one cluster a chain-analysis vendor can sell.

我方:每张账单使用全新地址。 Cryptoservers derives every deposit address from a BIP-32 HD path on a watch-only wallet. We never display the same address twice and we never reuse one across invoices. This means the only thing chain-analysis can correlate from public data is "an unknown wallet sent funds to an unknown address" — neither side's identity is on the chain.

您方:零成本隐私卫生技巧。

  • Use a wallet that supports HD addresses by default (Bitcoin Core, Electrum, Sparrow, Wasabi, Phoenix, Blixt). Avoid wallets that reuse a single deposit address.
  • Send to our address from a UTXO that did not come directly from a KYC exchange withdrawal labelled with your name. If you must use a KYC source, use a coinjoin (Wasabi, JoinMarket) or send via Lightning instead of on-chain.
  • 不要将多张 Cryptoservers 账单的 UTXO 合并到同一退款目标地址。我们将退款到全新地址;您应保持生成的 UTXO 不合并。
  • If you maintain multiple VPS over time, use a separate wallet (or at least a separate account) per VPS — that way the on-chain footprint of your "VPS payments" cannot be linked to the rest of your spending.

Bitcoin Optech publishes excellent ongoing guidance on UTXO management; the bitcoin.it wiki has a long-standing reference on <a href="https://en.bitcoin.it/wiki/Address_reuse" rel="nofollow noopener">why address reuse is harmful</a>. Both worth reading.

Bitcoin VPS 常见问题

Eight questions Bitcoin buyers ask us most.

How long does a Bitcoin payment take to confirm at Cryptoservers?
We deploy on the first network confirmation, which on Bitcoin is on average 10 minutes (one block). The orchestrator pre-stages your VM the moment we see the transaction in our mempool, so by the time the block lands the VPS is already booting. Median time from "broadcast" to "ssh root@" is just under twelve minutes for on-chain BTC. Lightning payments settle in seconds and we deploy as soon as the HTLC resolves.
你们接受 Bitcoin Lightning 吗?
Yes — for invoices under $200 we issue both an on-chain address and a BOLT-11 invoice at checkout. Pick whichever your wallet of choice supports best. Lightning settles in seconds (no on-chain wait), with a tiny routing fee that we absorb. Above $200 we recommend on-chain because Lightning channel capacity along common routes can fragment a large invoice.
Can I run a Bitcoin full node on a Bitcoin VPS?
Yes. The mainnet chain plus indexes is roughly 600 GB as of mid-2026 and growing about 80 GB per year. The Pro tier (400 GB) handles a pruned node comfortably; for an unpruned full node with txindex and addrindex we recommend the Scale tier (640 GB) or a small dedicated server. Lightning routing nodes need negligible storage and run perfectly on Starter or Growth.
Do you reuse Bitcoin deposit addresses between invoices?
No. Every invoice gets a fresh deposit address derived from a BIP-32 HD path on our receive wallet. We never display the same address twice and we never accept a re-payment to a previously-used address — even if you accidentally send to one, the funds will not auto-credit. Address reuse hurts privacy on both sides; we engineer it out.
What if I send the wrong amount of BTC?
Underpayments stay in the invoice as a partial credit; send the difference to the same address within 24 hours and the deploy fires when totals match. Overpayments are credited to your customer record and either applied to the next month or refunded on request to a destination address you supply. Email [email protected] for refund processing — we do not auto-refund because we cannot prove the destination is yours without you telling us.
Do you accept BTC from KYC exchanges?
Yes. From our side an inbound transaction is just a UTXO; we do not cluster sender wallets, we do not cross-reference with chain-analysis vendors, and we do not refuse known-exchange inputs. The privacy property of "your KYC exchange withdrawal that paid for this VPS" is a question for the public chain, not for us — but our records do not enrich it.
Is there a transaction-fee surcharge for paying in Bitcoin?
No. We absorb the network fee on our side. The price you see at checkout is the price we expect to receive net of mempool fees; if the fee market spikes between invoice generation and broadcast and your wallet underpays the network fee, the transaction will simply confirm slower (we wait up to 24 hours for the first confirmation before voiding).
Can I get a refund in Bitcoin to a different address than I paid from?
Yes — refunds within the 7-day money-back window go to whatever destination address you specify, not back to the source UTXO. This is by design: forcing a refund to the source would link our wallet to yours twice and degrade privacy on the chain. Send us a fresh address from a wallet you control and we will pay the refund there.

Pay your VPS in BTC.

Five tiers, four jurisdictions, no KYC, settled on the first confirmation. On-chain or Lightning.