Deploy post-migration production runtime

Unlock manager account

Deploy migration runtime

Unlock parachain manager account

Increase active collator set size to 32

Authorize runtime upgrade to v0.3.8

Increase active collator set size to 28

Upgrade to Polkadot runtime v27

Increase active collator set size to 24

Authorize runtime upgrade to v0.3.7

Increase active collator set size to 20

- 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

SubSquare is proposing to add DOT as a foreign asset on Zeitgeist and allow it in pools to help with liquidity issues. DOT is worth 7 billion dollars and can be easily transferred to the chain. DOT has 10 decimal places like ZTG, so it can be used in markets without any adjustments. DOT integration was tested on all technical levels and approved to move forward on the mainnet. You can see and interact with the prediction market that uses (fake) DOT as a base asset. Fees are charged in DOT when receiving it from Polkadot on Zeitgeist, and the amount charged is derived from the ZTG and DOT price averages.

Runtime upgrade to v26

1. There was a plan called Referendum 7 that was supposed to happen, but it didn't work because of a mistake in the code.
2. The mistake was that the code was set to 0 instead of 1, which meant that it couldn't work properly.
3. The person who made the mistake is proposing to try again with the same plan, but with the correct code this time.
4. They want the people in charge (called the Council) to agree to this plan and put it in a queue to be voted on (called the referenda queue).
5. This is important because they want to make sure that the plan can work the way it was supposed to and have a chance to be voted on.

Proposal to gradually increase the number of validators

- A motion called Motion 25 has been proposed.
- If it is passed by the council, it will schedule an increase of validator slots by 1 every era.
- This will happen every 14,400 blocks with a repetition of 100 eras.
- The motion will be voted on in the referenda queue for about 7 days after the TC fast-tracks it.
- Councillors can check a website to verify presage hash and add comments or questions.

A proposal to gradually increase the number of validators

- A proposal has been made to limit the maximum number of validators to 1200.
- This proposal needs to be voted on by the community before it can be executed.
- There may be a discussion in the future about setting a minimum DOT stake limit for validators.
- These limits are important for the safety of the network and will grow as the network grows.
- More information about this proposal can be found in the provided links.

Limit on the maximum number of validators, based on scaling issues

- A vote was held to open a channel to HydraDX
- The vote passed and the XCM was executed
- The channel was not opened because there was not enough money in the account
- The account has now been funded
- The XCM can be resent to open the channel

Init HRMP open channel request to HydraDX

- 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