Changing the start call delay from 0 to at least 7,200 blocks

[mcjkula]

Is your feature request related to a problem? Please describe.

The problem is that since recently (block #7,430,359 to be exact) the StartCallDelay is set to 0 on mainnet, while it was 50,400 blocks previously. This allows a subnet owner to "start" their subnet immediately while registering the subnet, while no root validator is there to receive the root_alpha (because of not enough time to register themselves and/or CHK).

This has partially enabled an "incident" in SN76 yesterday, where the price has increased up to 100K TAO/ALPHA, as root validators were not registered and thus weren't auto-selling/receiving the root_alpha which could have been sold (this would not have happened with enough time for validators to recognize the change in the subnet and register).

Describe the solution you'd like

I believe that there is no reason to have the delay being set to 0. If anything it should be set to at least 7,200 blocks (the equivalent of 20 tempos), which is the delay of CHK. If not 36,000-50,400 blocks (the equivalent of 5-7 days) considering the time it can take for validators to realize that the subnet was deregistered, to see if there is existing code to run or if they need to run burn code, to register and get their code running.

It very well does make sense to not require the delay for the start call on testnet and/or locally, yet on mainnet that should not be the case as it currently stands.

Describe alternatives you've considered

No response

Additional context

No response

[mcjkula]

There is no code change with that request in mind, what is required is an action by the Triumvirate (sudo) to run the sudoSetStartCallDelay extrinsic with a more reasonable delay than 0.

[dougsillars]

IMO, SN 76 was not in a "stable" position for about 36 hours from registration. I think 2-3 days min.