question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Chain reorg on every block during sync

See original GitHub issue

Description

Teku is printing a chain reorg on every imported block during sync:


2020-09-10 08:03:17.747 | beaconchain-async-7       | INFO  | RecentChainData                | Chain reorg from ebe498..660c (261915) to 4f042e..da16 (261915). Common ancestor at slot 0
2020-09-10 08:03:17.817 | beaconchain-async-8       | INFO  | RecentChainData                | Chain reorg from 4f042e..da16 (261915) to 21dd54..ddab (261915). Common ancestor at slot 1
2020-09-10 08:03:17.887 | beaconchain-async-7       | INFO  | RecentChainData                | Chain reorg from 21dd54..ddab (261915) to 35b622..1cad (261915). Common ancestor at slot 3
2020-09-10 08:03:17.956 | beaconchain-async-10      | INFO  | RecentChainData                | Chain reorg from 35b622..1cad (261915) to a24292..d7f7 (261915). Common ancestor at slot 4
2020-09-10 08:03:18.011 | beaconchain-async-1       | INFO  | RecentChainData                | Chain reorg from a24292..d7f7 (261915) to d346e6..10cb (261915). Common ancestor at slot 5
2020-09-10 08:03:18.055 | beaconchain-async-9       | INFO  | RecentChainData                | Chain reorg from d346e6..10cb (261915) to 3f1b68..2ce1 (261915). Common ancestor at slot 6
2020-09-10 08:03:18.079 | beaconchain-async-11      | INFO  | RecentChainData                | Chain reorg from 3f1b68..2ce1 (261915) to 76262e..fc76 (261915). Common ancestor at slot 7
2020-09-10 08:03:18.194 | beaconchain-async-3       | INFO  | RecentChainData                | Chain reorg from 76262e..fc76 (261915) to 6f88ad..ebbd (261915). Common ancestor at slot 8
2020-09-10 08:03:18.267 | beaconchain-async-2       | INFO  | RecentChainData                | Chain reorg from 6f88ad..ebbd (261915) to 9a2fef..4eaf (261915). Common ancestor at slot 9
2020-09-10 08:03:18.371 | beaconchain-async-4       | INFO  | RecentChainData                | Chain reorg from 9a2fef..4eaf (261915) to 97b939..f54c (261915). Common ancestor at slot 10
2020-09-10 08:03:18.455 | beaconchain-async-6       | INFO  | RecentChainData                | Chain reorg from 97b939..f54c (261915) to 8f1817..371a (261915). Common ancestor at slot 11
2020-09-10 08:03:18.541 | beaconchain-async-9       | INFO  | RecentChainData                | Chain reorg from 8f1817..371a (261915) to eca78a..1a22 (261915). Common ancestor at slot 12

We need to find a way to be smarter about this.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:13 (13 by maintainers)

github_iconTop GitHub Comments

1reaction
Nashatyrevcommented, Sep 10, 2020

Oh, or do we always have state slot == block slot in the ChainHead ?

1reaction
ajsuttoncommented, Sep 10, 2020

Yeah there’s a couple - https://github.com/PegaSysEng/teku/pull/2769 is the key one but fixes an important bug where we missed reorgs and so wound up not recalculating validator duties when we should have. #2637 is what started it but significantly improves attestation inclusion rates.

https://github.com/PegaSysEng/teku/pull/2670 would fix it but is a bit heavy handed and would lead to attestations that point to and old head in some cases. Not a bad option as a quick fix though.

Read more comments on GitHub >

github_iconTop Results From Across the Web

What is chain reorganization in blockchain technology?
Chain reorganization means that blocks in your node's old longest chain will be deactivated in favor of blocks in the new longest chain....
Read more >
How Does Chain Reorganization Work? - Moralis Academy
In short, chain reorganization is basically when blocks in the old longest chain get deactivated for blocks in the new longest chain.
Read more >
Syncing events on Database - Dealing with blockchain ...
Blockchain reorganization is a game breaking. As a common practice, I know it is suggested to wait for 12 confirmation blocks before syncing....
Read more >
What is a reorg? - Alchemy
A chain reorganization, or “reorg,” occurs when a blockchain produces blocks at the same time, if there is a bug, or due to...
Read more >
Ethereum Reorgs After The Merge - Paradigm
We start syncing from Block 1 with difficulty 100. Block 2a and 3a arrive each with difficulty 100 and we insert them in...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found