We've got a new update. We now offer our own Web Console. Open the console and type ssh root@your-server-ip to reach any server you own, right from your browser. No SSH app needed.
A BNB Smart Chain full node is heavy: the vendor guide we checked asks for 16 cores, 64 GB of RAM and about 3 TB of fast SSD. That is dedicated-server work. A full node here is $140 a month, an archive node is $210. Pay in BNB, Bitcoin, Monero or USDT.
Prices are for Romania on a one-month term; a 12-month term takes 50% off.
or $70/mo on a 12-month term (−50%)
A Geth full node needs about 2 to 2.5 TB (the vendor guide recommends 16 cores, 64 GB RAM and 3 TB of SSD). Stripe the four 2 TB drives into one volume.
Configure and orderor $105/mo on a 12-month term (−50%)
An Erigon archive node needs about 4.3 to 6 TB, with 10 TB suggested as headroom. The 16 TB of raw NVMe here covers that.
Configure and orderA 2026 BNB RPC guide lists a full node at 16 cores, 64 GB of RAM and 3 TB of SSD, and an archive node at 16 cores, 128 GB of RAM and 10 TB of NVMe (the 10 TB is headroom; the Erigon baseline is about 4.3 to 6 TB). Geth data for a full node is about 2 to 2.5 TB depending on pruning. NVMe matters: the guide warns that HDDs and network-only volumes fall behind during bursts.
The biggest VPS disk here is 1 TB. A BNB full node does not fit, so the Large dedicated server (four 2 TB NVMe drives, 128 GB ECC) is the smallest build that does. The four drives are striped into one volume. The X-Large (four 4 TB drives) covers an archive node.
From a snapshot, a node can reach usable RPC in hours and be in production inside a day on solid NVMe and network links. A full sync from scratch takes about one to two days; an Erigon archive from scratch about three days, per the same guide. Treat these as planning figures.
Pick the Large dedicated server for a full node, or X-Large for an archive node.
Combine the four NVMe drives into one volume so the chain fits.
Download the BSC release and its mainnet config from the official GitHub repo.
A snapshot gets you to the chain tip in hours instead of days.
Commands assume Ubuntu 22.04 or 24.04 and a root login. Check the drive names with lsblk first: the names below (nvme0n1 to nvme3n1) are examples. This command erases those drives, so run it only on empty ones.
# log in from your computer
ssh root@YOUR_SERVER_IP
# update the system and create a user that will run the node
apt update && apt -y upgrade
adduser --disabled-password --gecos "" bsc
# firewall: SSH first, then only the ports below
ufw allow OpenSSH
ufw enable
ufw allow 30311/tcp
ufw allow 30311/udp # BSC peer port in the current config; confirm in config.tomlapt -y install mdadm
lsblk # find the four empty NVMe drives
mdadm --create /dev/md0 --level=0 --raid-devices=4 /dev/nvme0n1 /dev/nvme1n1 /dev/nvme2n1 /dev/nvme3n1
mkfs.ext4 /dev/md0
mkdir -p /data && mount /dev/md0 /data
echo "$(blkid -s UUID -o export /dev/md0 | grep ^UUID) /data ext4 defaults,noatime 0 2" >> /etc/fstab
chown bsc:bsc /data
df -h /data # should show about 7 TBFind the newest release on the bnb-chain/bsc releases page. It ships the geth_linux binary and a mainnet.zip with config.toml and genesis.json. Replace TAG with that release tag and verify the hashes it lists.
su - bsc
cd /data
TAG=vX.Y.Z # the newest release tag
wget https://github.com/bnb-chain/bsc/releases/download/$TAG/geth_linux
wget https://github.com/bnb-chain/bsc/releases/download/$TAG/mainnet.zip
chmod +x geth_linux && unzip mainnet.zip
mkdir -p node
./geth_linux --datadir node init genesis.json
exitSyncing from block zero takes days. The BNB Chain team publishes snapshots; follow the current instructions in the BNB Chain docs, extract the snapshot into /data/node/geth, then start the node. Keep the RPC bound to localhost.
[Unit]
Description=BNB Smart Chain node
After=network-online.target
Wants=network-online.target
[Service]
User=bsc
WorkingDirectory=/data
ExecStart=/data/geth_linux --config /data/config.toml --datadir /data/node --cache 16000 --http --http.addr 127.0.0.1 --http.port 8545 --http.api eth,net,web3
Restart=on-failure
LimitNOFILE=1048576
TimeoutStopSec=600
[Install]
WantedBy=multi-user.targetsystemctl daemon-reload
systemctl enable --now bsc
journalctl -u bsc -f
# false means it has caught up; otherwise you get the sync progress
curl -s -H 'Content-Type: application/json' \
--data '{"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":1}' http://127.0.0.1:8545
curl -s -H 'Content-Type: application/json' \
--data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' http://127.0.0.1:8545A Geth full node uses about 2 to 2.5 TB depending on pruning, and the vendor guide recommends 3 TB of SSD for headroom. An Erigon archive node uses about 4.3 to 6 TB, with 10 TB suggested as headroom.
Not a full node. The largest VPS disk here is 1 TB. Use a dedicated server: the Large for a full node, the X-Large for an archive node.
From a snapshot, hours to reach usable RPC and about a day to settle on good NVMe. A full sync from scratch is about one to two days, per a 2026 guide. These are planning figures.
JSON-RPC is on 8545 and must stay private. The peer port is set in config.toml (30311 in the current mainnet config; confirm in yours).
No. You create an account with a generated login, top up with crypto and deploy. See no-KYC VPS hosting. You stay responsible for what you run, under our terms.
Checked 20 October 2026. Chain sizes and software requirements change, so confirm against the source before you order.
Pick a server, pay in crypto, log in as root. No ID, no card.
