BSC Node Deployment
We have faced the task of deploying a full BNB Smart Chain node for production. BSC produces a block every 3 seconds—4 times more frequently than Ethereum. As a result, CPU and I/O load is high, and chaindata size exceeds 3 TB. Without the right node type and server configuration, synchronization can take weeks or never complete. A common mistake is trying to use HDD or a server with insufficient RAM. The node crashes with out-of-memory, and synchronization speed drops to zero. Let's break down how to deploy a node that runs stably without breaking the budget.
How to Choose a BSC Node Type?
BSC offers three node types. The choice depends on your needs:
| Type | Disk Size | Sync Time | Use Case |
|---|---|---|---|
| Full Node (fast sync) | ~1.5 TB | 3–7 days | RPC with historical data |
| Full Node (snap sync) | ~700 GB | 6–24 hours | Fast RPC for dApps |
| Archive Node | 3+ TB | 1–2 weeks | Analytics, full history |
| Validator Node | ~700 GB | 6–24 hours | Staking BNB |
For most tasks (custom RPC, event indexing, contract interaction), a Full Node with snap sync is sufficient. This type takes less space and syncs in hours, not days.
How to Speed Up Synchronization?
Snap sync loads a snapshot of the current state and then catches up with recent blocks. This takes 6–24 hours on NVMe SSD. Downside: the node cannot answer historical eth_call requests—only for recent blocks. If you need full history, use fast sync or archive node.
To speed up synchronization:
- Increase cache: parameter
--cache 16384(minimum 16 GB RAM). - Limit the number of peers:
MaxPeers = 50in configuration. - Ensure bandwidth is at least 100 Mbps and latency to Asian peers is minimal.
Why Snap Sync Over Fast Sync?
Fast sync downloads all blocks from genesis—this can take days. Snap sync uses a state snapshot, reducing time to hours. According to the official BNB Chain documentation, snap sync is 4–5 times faster than fast sync. However, snap sync requires more RAM during snapshot loading.
Server Requirements
Minimum and recommended specifications for Full Node with snap sync:
| Parameter | Minimum | Recommended |
|---|---|---|
| vCPU | 16 | 32+ |
| RAM | 32 GB | 64 GB |
| Disk | 2 TB NVMe SSD | 4 TB NVMe SSD |
| Bandwidth | 100 Mbps | 1 Gbps |
| OS | Ubuntu 22.04 LTS | Ubuntu 24.04 LTS |
HDD is not suitable—BSC produces a block every 3 seconds, requiring fast I/O. Use NVMe SSD, otherwise the node won't keep up.
Installation and Configuration
Install using a precompiled binary from GitHub:
wget https://github.com/bnb-chain/bsc/releases/latest/download/geth_linux chmod +x geth_linux mv geth_linux /usr/local/bin/geth geth version Download genesis and network configuration:
mkdir -p /data/bsc && cd /data/bsc wget https://github.com/bnb-chain/bsc/releases/latest/download/mainnet.zip unzip mainnet.zip geth --datadir /data/bsc init genesis.json Create config.toml with optimizations for snap sync:
[Eth] NetworkId = 56 SyncMode = "snap" PriceLimit = 3000000000 # 3 Gwei min [Node] DataDir = "/data/bsc" HTTPHost = "0.0.0.0" HTTPPort = 8546 HTTPModules = ["eth", "net", "web3", "txpool"] WSHost = "0.0.0.0" WSPort = 8547 [Node.P2P] MaxPeers = 50 Run the node:
geth --config /data/bsc/config.toml --datadir /data/bsc --cache 16384 --syncmode snap --diffsync --snapshot 2>&1 | tee /var/log/bsc-node.log For production, add a systemd unit.
Monitoring and Security
Check synchronization with these commands:
geth attach /data/bsc/geth.ipc --exec "eth.blockNumber" geth attach /data/bsc/geth.ipc --exec "eth.syncing" geth attach /data/bsc/geth.ipc --exec "net.peerCount" P2P ports: 30303/tcp and 30303/udp. Expose RPC only through a reverse proxy with authentication. Use nginx with rate limiting (e.g., 100 requests per second) and firewall for port 8545.
For monitoring, use Grafana + Prometheus with ready-made dashboards. Metrics: sync speed, peer count, resource usage.
Troubleshooting
If synchronization stalls at the same block, check disk space and CPU load. The node may hang due to insufficient RAM. Increase --cache or add swap. If disk is full, delete old snapshots or attach a larger SSD. For peer connection errors, check that port 30303 is open.
What's Included in Turnkey Deployment
We offer a full cycle: server selection based on your load, installation and configuration of the node, monitoring setup (Grafana + Prometheus with ready-made dashboards), nginx reverse proxy with rate limiting, operational documentation, and 30 days of technical support after launch. Contact us for a configuration estimate and pricing.
Stability Guarantee
We guarantee stable node operation. Our engineers have extensive experience in blockchain infrastructure and have launched over 20 nodes across various networks. Get a consultation—we'll help you choose the optimal configuration and deploy a BSC node for your needs.