How to Run a New Fullnode with Binance Smart Chain Beta Release

How to Run a New Fullnode with Binance Smart Chain Beta Release

May 11, 2021

Please shut down your current node gracefully kill -TERM $(pgrep geth) and do not delete existing home folder

Download the Beta version of  bsc fullnode

Warning: this is a Beta version, please use with caution

Release page: https://github.com/binance-chain/bsc/releases/tag/v1.1.0-beta

wget  https://github.com/binance-chain/bsc/releases/download/v1.1.0-beta/geth_linux

Download the latest config file

https://github.com/binance-chain/bsc/releases/download/v1.1.0-beta/mainnet.zip

cd /NAME_OF_YOUR_HOME
## Extract the config files
unzip mainnet.zip 

  • Download the chain data snapshot and extract to a new folder

Size: 175G

wget -O  /NAME_OF_YOUR_HOME "https://s3.ap-northeast-1.amazonaws.com/dex-bin.bnbstatic.com/geth.zip?AWSAccessKeyId=AKIAYINE6SBQPUZDDRRO&Expires=1646568179&Signature=DaVl4clXyVS%2F65GEUHTqWOfD2DA%3D"

## Extract the data
unzip geth.zip -d /NAME_OF_YOUR_HOME/node &

  • Start full node

BREAKING CHANGE: Non-EIP155 transactions (i.e. transactions which are not replay-protected) are now rejected by the RPC API. You can disable this restriction using the –rpc.allow-unprotected-txs command-line flag.

Command

geth --config ./config.toml --datadir ./node -unlock {your-validator-address} --password password.txt  --mine  --allow-insecure-unlock  --cache 18000 --rpc.allow-unprotected-txs --txlookuplimit 0  --rpc.allow-unprotected-txs


Error Handling

In case of unexpected cases, you can shut down the v1.1.0 fullnode gracefully kill -TERM $(pgrep geth), then  restart the node v1.0.7 at your previous home folder

geth --config ./config.toml --datadir ./node --pprofaddr 0.0.0.0 --metrics --pprof