After the migration to Polkadot succeeded, the migration runtime has to be superseded by a production runtime again, that removes the adjustments necessary for the migration and unlocks the business logic again. More information at https://github.com/zeitgeistpm/zeitgeist/releases/tag/v0.3.8-polkadot

Deploy post-migration production runtime

This is a duplicate of https://zeitgeist.subsquare.io/democracy/referendum/19, please reject.

Unlock manager account

To be able to migrate to Polkadot, some changes to the runtime are necessary. The referendum dispatches a call to authorized the runtime mentioned within the following release: https://github.com/zeitgeistpm/zeitgeist/releases/tag/v0.3.8-polkadot-migration

Deploy migration runtime

To be able to recover the parachain in case of failure during the migration to Polkadot, the manager account has to be unlocked.

Unlock parachain manager account

Adheres to https://zeitgeist.subsquare.io/post/2

Increase active collator set size to 32

More information about the changes at https://github.com/zeitgeistpm/zeitgeist/releases/tag/v0.3.8

Authorize runtime upgrade to v0.3.8

Increase active collator set size to 28

Untitled - public proposal #7

Increase active collator set size to 24

More information about the changes at https://github.com/zeitgeistpm/zeitgeist/releases/tag/v0.3.7

Authorize runtime upgrade to v0.3.7

Increase active collator set size to 20

This proposal was intended to increase the active collator set size to 16, however:

After the runtime upgrade to Zeitgeist v0.3.6 (`spec_version 40`) the parachain-staking pallet (that is eventually invoked by the proposed call here) changed the function indices within the pallet. The function selector for `setTotalSelected` was `0x6e06` before, after the runtime upgrade `setBlocksPerRound` became `0x6e06` and `setTotalSelected` now has the function selector `0x6e04`. Consequently, before the runtime upgrade this proposal was about creating a simple majority vote to invoke `setTotalSelected`, but after the runtime upgrade it became `setBlocksPerRound`.

Please reject this proposal.

- A proposal was made to increase the active collator set size to 16.
- However, after an upgrade, the function indices in the pallet changed.
- This means that the function selector for `setTotalSelected` changed to `0x6e04`.
- The proposal was originally about creating a simple majority vote to invoke `setTotalSelected`.
- But after the upgrade, it became about `setBlocksPerRound`.

Increase active collator set to 16

Increase active collator set size to 16

More information about the changes at https://github.com/zeitgeistpm/zeitgeist/releases/tag/v0.3.6

Authorize Zeitgeist runtime v0.3.6 upgrade

Reopened since https://zeitgeist.subsquare.io/council/motion/1149052_0xce21327662586f820b749ad4804a1f6f19ae73370a239ffba03819fd7a3ec551 expired with an insufficient amount of votes.

This motion increases the active collator set size to 12, i.e. every round (currently approximately 2 hours) the top 12 collators by total stake (self stake + delegated stake) will be selected as block authors during the next round.

Zeitgeist would like to increase the collator set size during the course of time to achieve more robustness and decentralization in the network. The increments should happen in small steps to ensure, that the network is capable of handling addition collators without experiencing drawbacks.


- Zeitgeist is a network that needs collators to create blocks.
- A motion was made to increase the number of active collators from 10 to 12.
- This means that the top 12 collators by total stake will be selected to create blocks.
- Zeitgeist wants to increase the collator set size gradually to make the network stronger and more decentralized.
- This will be done in small steps to make sure the network can handle the additional collators without any problems.

Increase active collator set size to 12 - motion #8

More information about the changes at https://github.com/zeitgeistpm/zeitgeist/releases/tag/v0.3.5

Authorize Zeitgeist runtime v0.3.5 upgrade

Untitled - public proposal #1

If this change is applied, the collators that are active will be determined about every 2 hours (`600 blocks * 12 sec/block = 2 hours`). In addition, reward calculation and payouts will also be done every 2 hours. Those two processes are very intense operations that the chain has to execute currently every 4 minutes, so making this change will unlock many resources for transactions. Other side effects are that decreasing the bonds or leaving the candidate set will increase to 4 hours. 
Changing the blocks per round to higher value is also mandatory to increase the active collator set size.
We decided to go with 2 hours based on the example of Moonriver, a parachain on Kusama whose organization created the *parachain-staking* pallet that is handling the `blocksPerRound` value.

- SubSquare is making a change to how often collators are determined and rewards are calculated.
- This change will happen every 2 hours instead of every 4 minutes, which will free up resources for transactions.
- Leaving the candidate set will take longer, now 4 hours instead of less time.
- They are also increasing the active collator set size by changing the blocks per round to a higher value.
- They got the idea for this change from a parachain on Kusama called Moonriver.

Democracy Referenda