Lightning node on a stable VPS IP

LND or Core Lightning on an IP that does not rotate. Hosting invoices stay on-chain, not Lightning.

Published 2026-08-30 · Updated 2026-10-21 · BitCloudVPS Editorial

What people actually run

Lightning Labs documentation and Core Lightning need a bitcoind (or an equivalent backend) and an IP that does not rotate. Do not send Lightning to the on-chain BTC invoice address.

Playbook

Limits

A Lightning node is allowed. Attacking peers is not.

Channel state is the real uptime requirement

A Lightning node's hardware needs are modest; its availability needs are not. LND or Core Lightning alongside a pruned bitcoind fits Plus $13.50/mo (4 vCPU, 8 GB ECC, 120 GB NVMe) for a personal node with a handful of channels; a routing node with hundreds of channels wants Business — $30 list, $24 yearly — for 16 GB of RAM and 240 GB of NVMe, because gossip state and channel graphs are RAM-hungry. The bill that matters is downtime: force-close sweeps eat fees when a node vanishes mid-payment, so the value of the hosting is measured in months of uninterrupted process, ECC memory, and NVMe that does not stall fsync on channel.db. Snapshot channel state before every restart and keep a static channel backup off-box — the host cannot do this for you. Unmetered ports matter because gossip and channel updates are constant background traffic. Deploy in 60 seconds

The stable IP problem and paying for the node itself

Peers find your node by URI — pubkey@ip:port — and every IP change orphans the announcement until gossip re-propagates, which costs routing reputation. BitCloudVPS assigns a static IPv4 per VPS plus a /64 IPv6 block, and the IP survives reboots and reinstalls on the same box; PTR is editable from the panel if you want reverse DNS to match a hostname. Payment has a trap worth repeating: the on-chain BTC invoice address does not accept Lightning — settle the hosting in on-chain BTC, USDT across seven networks, or any of the other 17 assets, and keep Lightning for your node's own business. No KYC at checkout, email optional, deploy in about a minute. The honest limit: a VPS routing node shares the hypervisor, and if channel volume becomes serious money, dedicated from $79.50/mo removes the neighbour variable entirely.

Where the limits are (October 2026)

Keep the threat model precise. Anonymous-adjacent hosting removes the host-side identity trail: token-only signup, optional email, no KYC review, crypto invoices that record a txid rather than a name. It does not blind the host to traffic it must carry, it does not make a logged-in panel session anonymous, and it does not protect workloads that identify themselves — an admin login from your home IP defeats the whole design. Exact limits of no-KYC anonymity. OPSEC guide. Full checklist. Payment-side note: chain analysis happens on public blockchains, not at the host. Coin choice and network choice are your OPSEC knobs, and the checkout keeps 19 of them open.