From 40800719b43037640a6f3ce22b33f62fceca3af6 Mon Sep 17 00:00:00 2001 From: Thomas Coratger Date: Thu, 24 Oct 2024 11:57:19 +0200 Subject: [PATCH] eips: rm BEACON_CONSENSUS_REORG_UNWIND_DEPTH --- crates/eips/src/merge.rs | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/crates/eips/src/merge.rs b/crates/eips/src/merge.rs index 76fd09d11db..06b6155f3b7 100644 --- a/crates/eips/src/merge.rs +++ b/crates/eips/src/merge.rs @@ -26,16 +26,6 @@ pub const EPOCH_DURATION: Duration = Duration::from_secs(EPOCH_DURATION_SECS); /// The default block nonce in the beacon consensus pub const BEACON_NONCE: u64 = 0u64; -/// The number of blocks to unwind during a reorg that already became a part of canonical chain. -/// -/// In reality, the node can end up in this particular situation very rarely. It would happen only -/// if the node process is abruptly terminated during ongoing reorg and doesn't boot back up for -/// long period of time. -/// -/// Unwind depth of `3` blocks significantly reduces the chance that the reorged block is kept in -/// the database. -pub const BEACON_CONSENSUS_REORG_UNWIND_DEPTH: u64 = 3; - /// Max seconds from current time allowed for blocks, before they're considered future blocks. /// /// This is only used when checking whether or not the timestamp for pre-merge blocks is in the