Skip to content

Conversation

@ppolewicz
Copy link
Collaborator

The prompt was:

make a sudo-only hyperparameter for the delay before calling start call which is hardcoded to 50400 or 7*7200 currently

This commit converts the hardcoded DurationOfStartCall constant (50400
blocks, or ~7 days) into a runtime-configurable hyperparameter called
StartCallDelay that can be modified via sudo extrinsic.

Changes:

  • Added StartCallDelay storage value with DefaultStartCallDelay type_value
  • Renamed DurationOfStartCall config constant to InitialStartCallDelay
  • Added StartCallDelaySet event for hyperparameter updates
  • Added get_start_call_delay() and set_start_call_delay() functions
  • Added sudo_set_start_call_delay() extrinsic in admin-utils (call_index 84)
  • Updated subnet.rs to read from storage instead of config constant
  • Updated runtime constant from DurationOfStartCall to InitialStartCallDelay
  • Updated all mock files and test usages to use new parameter name
  • Updated benchmarks and tests to use StartCallDelay::<T>::get()

The delay can now be modified at runtime via the sudo_set_start_call_delay()
extrinsic without requiring a runtime upgrade, providing more flexibility
for network governance.

Users can read the current value through:

  • Direct storage queries via state_getStorage RPC call
  • The get_start_call_delay() getter function for internal use
  • Client libraries (polkadot-js, subxt) which auto-generate storage accessors

Prompt: "make a sudo-only hyperparameter for the delay before calling
start call which is hardcoded to 50400 or 7*7200 currently"

This commit converts the hardcoded DurationOfStartCall constant (50400
blocks, or ~7 days) into a runtime-configurable hyperparameter called
StartCallDelay that can be modified via sudo extrinsic.

Changes:
- Added StartCallDelay storage value with DefaultStartCallDelay type_value
- Renamed DurationOfStartCall config constant to InitialStartCallDelay
- Added StartCallDelaySet event for hyperparameter updates
- Added get_start_call_delay() and set_start_call_delay() functions
- Added sudo_set_start_call_delay() extrinsic in admin-utils (call_index 84)
- Updated subnet.rs to read from storage instead of config constant
- Updated runtime constant from DurationOfStartCall to InitialStartCallDelay
- Updated all mock files and test usages to use new parameter name
- Updated benchmarks and tests to use StartCallDelay::<T>::get()

The delay can now be modified at runtime via the sudo_set_start_call_delay()
extrinsic without requiring a runtime upgrade, providing more flexibility
for network governance.

Users can read the current value through:
- Direct storage queries via state_getStorage RPC call
- The get_start_call_delay() getter function for internal use
- Client libraries (polkadot-js, subxt) which auto-generate storage accessors
Added test_sudo_set_start_call_delay_permissions_and_zero_delay which:

1. Verifies permission checking - non-root accounts cannot set the delay
2. Creates a subnet
3. Attempts to start it immediately - FAILS (delay not passed)
4. Sets delay to zero via sudo_set_start_call_delay()
5. Verifies StartCallDelaySet event is emitted
6. Attempts to start the same subnet again - SUCCEEDS (delay now zero)
7. Attempts to start it a third time - FAILS (already started)

This test validates the key scenario: a subnet that couldn't be started
due to the delay can be started after reducing the delay to zero, proving
the hyperparameter change takes immediate effect. The test calls start_call
three times to thoroughly verify the state transitions and confirms the
proper event is emitted when the delay is changed.
@ppolewicz ppolewicz added the enhancement New feature or request label Dec 22, 2025
Copy link
Contributor

@open-junius open-junius left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Just need bump the runtime version "spec_version: 365".
and inform Roman there is a broken e2e test.

@thewhaleking
Copy link
Contributor

Looks good to me. Just need bump the runtime version "spec_version: 365". and inform Roman there is a broken e2e test.

@basfroman for awareness

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants