candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Unbrick Council collective

Unlock manager account

On chain democracy proposal

Title not edited.

Deploy migration runtime

- The proposal aimed to increase the active collator set size to 16.
- A runtime upgrade to Zeitgeist v0.3.6 changed function indices in the parachain-staking pallet.
- Before the upgrade, the function selector for `setTotalSelected` was `0x6e06`.
- After the upgrade, `setBlocksPerRound` took the `0x6e06` selector, and `setTotalSelected` became `0x6e04`.
- The proposal initially intended to invoke `setTotalSelected`.
- After the upgrade, it would instead invoke `setBlocksPerRound`.
- The proposal should be rejected due to this change.

Increase active collator set to 16

Increase active collator set size to 32

Authorize runtime upgrade to v0.3.8

Increase active collator set size to 28

Increase active collator set size to 24

Authorize runtime upgrade to v0.3.7

Increase active collator set size to 20

- The proposal aimed to increase the active collator set size to 16.
- It was linked to a runtime upgrade to Zeitgeist v0.3.6 (`spec_version 40`).
- The parachain-staking pallet changed function indices after the upgrade.
- Before the upgrade, the function selector for `setTotalSelected` was `0x6e06`.
- After the upgrade, `setBlocksPerRound` took `0x6e06`, and `setTotalSelected` became `0x6e04`.
- The proposal originally intended to invoke `setTotalSelected`.
- After the upgrade, it would invoke `setBlocksPerRound` instead.
- The proposal should be rejected due to this change.

### Summary of Referendum 7 Failure

- **Referendum 7** was passed by both the Council and the community.
- The referendum was supposed to execute after a certain block number.
- The code checked if the target block number (`when`) was in the past or not.
- The target block number was set to **0**, which failed the check.
- A target block number of **1** would have allowed the referendum to execute in the next block.
- The author is proposing the same motion again to the Council.
- The goal is to get the motion into the referenda queue again for execution.

Proposal to gradually increase the number of validators

On chain council motion

- **Motion 25** proposes increasing the number of validator slots by 1 every era (14,400 blocks) for 100 eras.
- The motion will be voted on in the referenda queue if approved by the council.
- Voting will last for approximately 7 days after the Technical Committee (TC) fast-tracks the process.
- Councillors can verify the presage hash [here](https://polkadot.polkassembly.io/post/93#3baa6f49-06c7-4d47-9cb8-44bd19f789d6).
- Comments and questions are welcome.
- Original proposal details can be found [here](https://polkadot.polkassembly.io/post/93).

A proposal to gradually increase the number of validators

- A referendum to open a channel to HydraDX was passed.
- The XCM message was sent and executed.
- The channel wasn't opened due to insufficient funds.
- The funds have now been added to the account.
- The XCM message can be sent again to open the channel.

Init HRMP open channel request to HydraDX

### Summary

- **Collator Activity**: Collators will be determined every 2 hours instead of every 4 minutes.
- **Reward Calculation**: Rewards will be calculated and paid out every 2 hours.
- **Resource Efficiency**: This change will free up resources for more transactions.
- **Bond Changes**: Decreasing bonds or leaving the candidate set will take 4 hours instead of 4 minutes.
- **Active Collator Set**: Increasing the blocks per round is necessary to expand the active collator set.
- **Decision Basis**: The 2-hour interval was chosen based on Moonriver's example, which uses a similar system.

Democracy Referenda