search

bnb-chain / bsc

A BNB Smart Chain client based on the go-ethereum fork
GNU Lesser General Public License v3.0
2.73k stars 1.56k forks source link

BSC light node not working on 1.3.X #2162

Closed mirakrejci2 closed 9 months ago

mirakrejci2 commented 9 months ago

In version 1.2.15, the light node (even though it is an experimental feature) worked without any problems, since 1.3.X, unfortunately, it no longer finds any peers. In the log it says: "Discovery v5 is not initialized". I don't know if it's a bug. Can something be done about it please?

Thanks!

/usr/local/bin/geth --syncmode light --config /etc/bsc/config.toml --datadir /srv/bsc --cache 8000 --rpc.allow-unprotected-txs --history.transactions 0 --http --http.api eth,net,web3,txpool,debug --http.vhosts --ws --ws.api eth,net,web3 --ws.rpcprefix "/" --ws.origins

CocoStarZ commented 9 months ago

Light node has been disabled, please use fast node which would be faster for syncing.

https://docs.bnbchain.org/docs/BSC-fast-node#fast-node-functions

zzzckck commented 9 months ago

In version 1.2.15, the light node (even though it is an experimental feature) worked without any problems, since 1.3.X, unfortunately, it no longer finds any peers. In the log it says: "Discovery v5 is not initialized". I don't know if it's a bug. Can something be done about it please?

Thanks!

/usr/local/bin/geth --syncmode light --config /etc/bsc/config.toml --datadir /srv/bsc --cache 8000 --rpc.allow-unprotected-txs --history.transactions 0 --http --http.api eth,net,web3,txpool,debug --http.vhosts --ws --ws.api eth,net,web3 --ws.rpcprefix "/" --ws.origins

Yea, light node will no longer be supported, refer: https://github.com/bnb-chain/bsc/pull/2098 Why would you need a light node? Is it a must for your business?

mirakrejci2 commented 9 months ago

Thanks for the anwers.

We have two full nodes of our own. We used the Light node as another backup, which is not demanding on storage. What are the storage requirements of a fast node compared to a full node?

zzzckck commented 9 months ago

Thanks for the anwers.

We have two full nodes of our own. We used the Light node as another backup, which is not demanding on storage. What are the storage requirements of a fast node compared to a full node?

The latest compressed fast node provided by 48Club takes 365GB, after uncompress, it would take less then 500GB. Check: https://github.com/48Club/bsc-snapshots

image

But it does not contain the whole historical block, it only keeps the most recent 90000 blocks. If you need the intact historical block, then another 1TB could be needed.

dandavid3000 commented 9 months ago

In version 1.2.15, the light node (even though it is an experimental feature) worked without any problems, since 1.3.X, unfortunately, it no longer finds any peers. In the log it says: "Discovery v5 is not initialized". I don't know if it's a bug. Can something be done about it please? Thanks! /usr/local/bin/geth --syncmode light --config /etc/bsc/config.toml --datadir /srv/bsc --cache 8000 --rpc.allow-unprotected-txs --history.transactions 0 --http --http.api eth,net,web3,txpool,debug --http.vhosts --ws --ws.api eth,net,web3 --ws.rpcprefix "/" --ws.origins

Yea, light node will no longer be supported, refer: #2098 Why would you need a light node? Is it a must for your business?

I'm running 2 nodes. Fast node and light node. It's unfortunate if light node is removed because I always have problem with syncing from BSC even if it's a fast node or full node. It happens all the time the node is out of sync due to some peer problems while with light node I don't have that problem. I've been running bsc node for years. The issue is still persistent.

MatusKysel commented 9 months ago

@dandavid3000 can you be more specific about some peer problems? Light node protocol was deprecated and as it is easier to fix peer problems than maintain another protocol, maybe you should consider to open up new issue describing your problems