Reconfigure spending tracks on Kusama

[adamsteeber]

These reconfigurations are what many believe is the first step in changing the paradigm of Treasury spending. Discussion can be found here: https://forum.polkadot.network/t/kusama-treasury-follow-up-analysis-continued-budgeting-incompetence.

This will change the following parameters:

Track	Spend Limit	Max Deciding	Min Approval	Preparation Period	Confirmation Period	Decision Period
Small Tipper	No Change	200 -> 6	No Change	1 mins -> 3 hrs	No Change	No Change
Big Tipper	No Change	100 -> 3	No Change	10 mins -> 6 hrs	No Change	No Change
Small Spender	333 KSM -> 100 KSM	50 -> 7	No Change	4 hrs -> 24 hrs	No Change	No Change
Medium Spender	3,333 KSM -> 1,250 KSM	50 -> 2	No Change	4 hrs -> 24 hrs	No Change	No Change
Big Spender	33,333 KSM -> 2,500 KSM	50 -> 1	50% -> 66%	4 hrs -> 24 hrs	48 hrs -> 24 hrs	No Change
Treasurer	No Change	No Change	50% -> 66%	2 hrs -> 48 hrs	3 hrs -> 48 hrs	14 days -> 28 days

This pull request coincides with referendum 235 on Kusama which implements these changes in v9430. Should that referendum pass, this can be merged into v1.0.0 to ensure these changes persist.

[ggwpez]

bot fmt

[command-bot]

@ggwpez https://gitlab.parity.io/parity/mirrors/polkadot/-/jobs/3187226 was started for your command "$PIPELINE_SCRIPTS_DIR/commands/fmt/fmt.sh". Check out https://gitlab.parity.io/parity/mirrors/polkadot/-/pipelines?page=1&scope=all&username=group_605_bot to know what else is being executed currently.

Comment bot cancel 24-2439d4a6-4bf7-4434-a661-627836c6fef0 to cancel this command or bot cancel to cancel all commands in this pull request.

[command-bot]

@ggwpez Command "$PIPELINE_SCRIPTS_DIR/commands/fmt/fmt.sh" has finished. Result: https://gitlab.parity.io/parity/mirrors/polkadot/-/jobs/3187226 has finished. If any artifacts were generated, you can download them from https://gitlab.parity.io/parity/mirrors/polkadot/-/jobs/3187226/artifacts/download.

[Polkadot-Forum]

This pull request has been mentioned on Polkadot Forum. There might be relevant details there:

https://forum.polkadot.network/t/kusama-treasury-follow-up-analysis-continued-budgeting-incompetence/3143/20

[ggwpez]

My approval is not count anyway since its a runtime file, but it looks fine to me from a technical perspective.

[ggwpez]

It probably still makes sense to open an RFC here https://github.com/polkadot-fellows/RFCs to get an on-chain support signal.
That should help to clear out doubts about the exact values and open the way to having it uncontroversial merged.

[bkchr]

@adamsteeber as @ggwpez already said, this should be included in a RFC. As there is already this RFC open: polkadot-fellows/RFCs#20 I would please ask you to add your feedback there and then it can probably directly be integrated in this RFC.

I'm going to close this pr, just to clean up the list of prs.