From 15c19fc51db17412784c7c61525cf29db0040b0b Mon Sep 17 00:00:00 2001 From: Paolo La Camera Date: Tue, 17 Jun 2025 10:35:29 +0200 Subject: [PATCH] staking-async runtime: extended duration of the signed phase For the staking-async test runtime, extended the duration of the signed phase from 2 to 4 minutes, in order to give enough time to the staking miner to mine, submit the score and all pages during the signed phase itself. While testing on CI / locally for a 32-page solution, the miner ends up submitting pages pretty close to the end of the signed phase itself. Whereas this is a valuable scenario to test to prove miner's robustness, in the main happy path we want the miner to have enough time to submit the whole solution and to be able to handle a re-tx if one/N pages fail to be submitted still within the same Signed phase cycle. --- substrate/frame/staking-async/runtimes/parachain/src/staking.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/substrate/frame/staking-async/runtimes/parachain/src/staking.rs b/substrate/frame/staking-async/runtimes/parachain/src/staking.rs index 22bea0850f008..ec7eb3752098e 100644 --- a/substrate/frame/staking-async/runtimes/parachain/src/staking.rs +++ b/substrate/frame/staking-async/runtimes/parachain/src/staking.rs @@ -31,7 +31,7 @@ use sp_runtime::{ use xcm::latest::prelude::*; parameter_types! { - pub storage SignedPhase: u32 = 2 * MINUTES; + pub storage SignedPhase: u32 = 4 * MINUTES; pub storage UnsignedPhase: u32 = MINUTES; pub storage SignedValidationPhase: u32 = Pages::get(); // allow to verify just a solution