-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Too many P2P connections from old Geth/Erigon version. #2638
Comments
so it's because of this rule
https://github.com/bnb-chain/bsc/blob/develop/core/forkid/forkid.go#L191 |
checked, agree with @MatusKysel , obey rule #2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The latest BSC hardfork is Tycho&Haber, which is supported by
But I noticed that my nodes are connected with lots of old Geth/Erigon release, especially Geth-v1.3.13, Erigon-v1.2.5. These old version does not support the latest hard fork, and they are supposed to be rejected due to mismatch forkid.
I dumped my connected peers for reference: peers_0808.log
This issue happens in Erigon client as well, I think it is not expected, create this issue to track
Steps to reproduce the behaviour
Just set up a BSC full node either with Geth-v1.4.12+ or Erigon-v1.2.12+.
After a while, dump your connected peers by:
./bsc --exec "admin.peers" attach geth.ipc > peers.log
Backtrace
NA
The text was updated successfully, but these errors were encountered: