From 4f232cbc27728ecd1b0ea20a6c2d206fed1ee76b Mon Sep 17 00:00:00 2001 From: carllin Date: Tue, 9 Apr 2019 11:45:25 -0700 Subject: [PATCH] Make MAX_RECENT_BLOCKHASHES <= MAX_HASH_AGE_IN_SECONDS (#3679) * Make MAX_RECENT_BLOCKHASHES == MAX_HASH_AGE_IN_SECONDS --- sdk/src/timing.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sdk/src/timing.rs b/sdk/src/timing.rs index bacbc6d2cd..8f3c42c789 100644 --- a/sdk/src/timing.rs +++ b/sdk/src/timing.rs @@ -21,8 +21,8 @@ pub const NUM_CONSECUTIVE_LEADER_SLOTS: u64 = 8; /// not be processed by the network. pub const MAX_HASH_AGE_IN_SECONDS: usize = 120; -pub const MAX_RECENT_BLOCKHASHES: usize = - (NUM_TICKS_PER_SECOND * MAX_HASH_AGE_IN_SECONDS as u64 / DEFAULT_TICKS_PER_SLOT) as usize; +// This must be <= MAX_HASH_AGE_IN_SECONDS, otherwise there's risk for DuplicateSignature errors +pub const MAX_RECENT_BLOCKHASHES: usize = MAX_HASH_AGE_IN_SECONDS; pub fn duration_as_us(d: &Duration) -> u64 { (d.as_secs() * 1000 * 1000) + (u64::from(d.subsec_nanos()) / 1_000)