nimbus-eth2/beacon_chain
Etan Kissling 6f466894ab
answer RequestManager queries from disk if possible (#6109)
When restarting beacon node, orphaned blocks remain in the database but
on startup, only the canonical chain as selected by fork choice loads.
When a new block is discovered that builds on top of an orphaned block,
the orphaned block is re-downloaded using sync/request manager, despite
it already being present on disk. Such queries can be answered locally
to improve discovery speed of alternate forks.
2024-03-21 18:37:31 +01:00
..
2024-03-19 14:22:07 +01:00
2024-03-19 14:22:07 +01:00
2024-03-19 14:22:07 +01:00
2024-03-19 14:22:07 +01:00
2024-03-03 02:04:45 +01:00
2024-01-22 17:34:54 +01:00
2024-01-05 10:08:38 +01:00
2024-02-21 20:06:19 +01:00
2024-02-27 03:24:30 +02:00