-
Notifications
You must be signed in to change notification settings - Fork 19.5k
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
Can bad blocks stop synchronization from working? #29685
Comments
No, geth should be capable to identify the bad block, throw it away and follow the chain guided by the consensus client.
Are you running some Non-Pos network? IIRC, this kind of error shouldn't show up after switching to Proof-of-stake |
I am using Clique PoA(Proof-of-Athuority) Consensus algorithm.
…On Tue, Apr 30, 2024, 13:15 rjl493456442 ***@***.***> wrote:
bad blocks stop synchronization from working
No, geth should be capable to identify the bad block, throw it away and
follow the chain guided by the consensus client.
no peers available or all tried for download
Are you running some Non-Pos network? IIRC, this kind of error shouldn't
show up after switching to Proof-of-stake
—
Reply to this email directly, view it on GitHub
<#29685 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALDJT4QOQLYX7M7DF7AFSATY75HLTAVCNFSM6AAAAABG7UO2VGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBUGY3TKMRZGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Which network you are trying to sync. Keep in mind that Rinkeby and Goerli has been deprecated. |
@rjl493456442 I am using Clique PoA(Proof-of-Athuority) Consensus algorithm. |
I encountered these errors during synchronization:
However, after some time(approximately 20 hours), the new node started working fine,
The text was updated successfully, but these errors were encountered: