Skip to content

fix: DefaultPendingChildKeyCooldown should use prod_or_fast value #2317

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
DanielDerefaka wants to merge 1 commit into
base: main
Choose a base branch
from
+3 −2
Open

fix: DefaultPendingChildKeyCooldown should use prod_or_fast value #2317

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions pallets/subtensor/src/lib.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down