From 83ed6d8491ba7951231f696afc35f24783ba8206 Mon Sep 17 00:00:00 2001
From: DanielDerefaka <bryancagedx@gmail.com>
Date: Mon, 22 Dec 2025 17:18:19 +0100
Subject: [PATCH] fix: DefaultPendingChildKeyCooldown should use prod_or_fast
 value

DefaultPendingChildKeyCooldown was returning 0 instead of using the
same value as DefaultPendingCooldown. This causes PendingChildKeyCooldown
to be 0 on fresh chains (like localnet) instead of the expected 7200/15.

Changed to call DefaultPendingCooldown::<T>::get() for consistency.

Fixes #2107
---
 pallets/subtensor/src/lib.rs | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/pallets/subtensor/src/lib.rs b/pallets/subtensor/src/lib.rs
index ef2d44e68b..7d42880a21 100644
--- a/pallets/subtensor/src/lib.rs
+++ b/pallets/subtensor/src/lib.rs
@@ -2359,10 +2359,11 @@ pub mod pallet {
     #[pallet::storage]
     pub type HasMigrationRun<T: Config> = StorageMap<_, Identity, Vec<u8>, bool, ValueQuery>;
 
-    /// Default value for pending childkey cooldown (settable by root, default 0)
+    /// Default value for pending childkey cooldown (settable by root).
+    /// Uses the same value as DefaultPendingCooldown for consistency.
     #[pallet::type_value]
     pub fn DefaultPendingChildKeyCooldown<T: Config>() -> u64 {
-        0
+        DefaultPendingCooldown::<T>::get()
     }
 
     /// Storage value for pending childkey cooldown, settable by root.