RpcNode Toolkit

Home/Networks/BNB Smart Chain

bsc

BNB Smart Chain full node

Run your own BNB Smart Chain full node with BSC Geth — full history, standard eth_* RPC, panel-managed sync.

Install ToolkitOfficial docs

Client

BSC Geth

RPC

Ethereum JSON-RPC (eth_* )

History

Unpruned full history. Synced from eth_syncing, not a light client.

BSC speaks Ethereum JSON-RPC but the client is BSC Geth, not upstream Geth. Toolkit pins the catalog binary, writes a high-load RPC config, and waits on eth_syncing before calling the node Synced.

Mainnet and testnet are first-class environments. Same Add node flow as Ethereum: ports, install, start, then the node page.

Environments

mainnettestnet

Install

  1. On Ubuntu 24.04 LTS:
    bash
    curl -fsSL "https://toolkit.rpcnode.dev/install/agent.sh" | sudo bash
    Supported and recommended: Ubuntu 24.04 LTS (amd64 or arm64). Other operating systems have not been tested.
  2. Panel → Add server (Agent URL + token) → Add node → BNB Smart Chain → mainnet.
  3. Confirm ports, choose install options if this chain has them, install BSC Geth, snapshot if required, start. Watch sync on the node page.

Operate from the panel

After the node is up you manage it in the same UI — Node Config (edit the live files and apply), client updates, restart, logs, public RPC. You do not need SSH to change conf. Install-time choices (snapshot flavor, history window, disk layout) are stored on that node.

FAQ

How do I run a BNB Smart Chain full node?
Install the host agent, add the server, then Add node → BNB Smart Chain. Toolkit provisions BSC Geth.
Can I change the BNB Smart Chain config later?
Yes. Node page → Node Config. Edit and apply; restart from the same page. A different snapshot or history flavor is an Install choice — changing it later usually means wipe and Add node again.
Pruned or light?
Unpruned full history. Synced from eth_syncing, not a light client.
Catalog
/clients/bsc/ · catalog.json

Other networks