BNB Smart Chain

Build web3 dApps effortlessly

BNB 信標鏈

Sunset soon

BNB Chain 生態系的質押與治理層

文件GitHubFaucetStake BNBBscScanBSCTraceDev ToolsLearn more about Fusion文件信標鏈瀏覽器文件GitHubFaucet跨鏈橋GreenfieldScanDCellarDev Tools文件GitHubFaucet跨鏈橋opBNBScanDev Tools文件GitHub

開發人員


Submit dApps

BNB Smart ChainBNB GreenfieldopBNBzkBNBBNB HackBNB Incubation Alliance (BIA)MVB 加速器計畫BNB Chain Grants開始Gas GrantsTVL Incentive ProgramMEME Coins Innovation查看所有計畫

生態系

Staking

Earn BNB and rewards effortlessly

Tokenization Solutions

Get Your Business Into Web3

Native StakingLiquid StakingCompany TokenizationReal World Assets TokenizationNFT Loyalty Program

社群

聯繫我們Get Started
聯繫我們Get Started

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

2021.5.11  •  1 min read
Blog post image.

Why do you need to upgrade?

If you are having trouble running a fullnode on Binance Smart chain mainnet or testnet, it's recommended to upgrade to this version. The new version saves storage usage by at least 50%. After pruning, the storage is around 200G.

May 11, 2021

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

Create a new folder as home folder

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

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  --cache 18000 --rpc.allow-unprotected-txs --txlookuplimit 0 


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

Share