### Proposal for First Parachain Auctions on Polkadot

- **Purpose**: To schedule the first parachain auctions and get Council approval for a 3-6 month auction schedule.
- **Readiness**: Parity engineering team believes the code for parachains, auctions, and crowdloans is ready for production.
- **First Batch**: 
  - 5 auctions starting on November 11, each lasting 7 days.
  - Auctions will begin every 7 days for lease periods 6-13.
- **Second Batch**: 
  - 6 auctions starting on December 23, each lasting 7 days.
  - Auctions will begin every 14 days for lease periods 7-14.
- **Timing**: Auctions will start around mid-day UTC on November 11.
- **Stability**: Proposes limiting Polkadot parachain slots to 75% of Kusama's to ensure stability.
- **Duration**: Initial schedule will last until early March, with potential updates based on network growth.

proposalHash

votingPeriod

delay

Proposal for First Parachain Auctions on Polkadot

- A proposal to upgrade the Polkadot network to version 9110 was submitted with a compact hash, but it was too large for the network.
- A new motion, **Motion 117**, is now up for vote with a compressed hash to fix this issue.
- The motion aims to upgrade the Polkadot Runtime to version 9110, with details available [here](https://github.com/paritytech/polkadot/releases/tag/v0.9.11).
- The correct hash for the proposal is `0x791e698f3690481e0eb16d35017cf3bb27ec095ec6f27dafd3a230b76dc42f86`.
- Users can verify the proposal hash using `srtool`.
- Voting is open for the Council to decide on the upgrade.

Runtime v9110 on Polkadot Network

### Polkadot Runtime Upgrade Proposal (v9110)

- **Proposal**: Upgrade Polkadot Runtime to version **v9110**.
- **Details**: Release notes, runtime changes, and proposal hash are available [here](https://github.com/paritytech/polkadot/releases/tag/v0.9.11).
- **Hash**: `0xe874dd4219efa603acc0ab24a592d6f1b8553b7aedb196d1ef65fdd7fc3b8fe5`.
- **Verification**: Use `srtool` to check the proposal hash.
- **Importance**: Migrations and changes in v9100 require this upgrade; skipping is not possible.
- **Timing**: If fast-tracked, ensure it follows v9100 on the network and v9110 on Kusama.
- **Action**: Vote at your convenience.

### Polkadot Runtime Upgrade Proposal (v9100)

- **Proposal**: Upgrade Polkadot Runtime to version 9100.
- **Details**: Release notes and changes are available [here](https://github.com/paritytech/polkadot/releases/tag/v0.9.10).
- **Proposal Hash**: `0x8160fd4a5aa5d58491cc8d4f0919780da25feb9ada92c2126b3f1d859800dd81`.
- **Verification**: Use `srtool` to check the proposal hash.
- **Runtime Version**: Uses a non-compressed version.
- **Timing**: Fast-track after Kusama's runtime upgrade.
- **Voting**: Vote at your convenience.

Runtime v9100 on Polkadot Network

### Summary of Staking Proposal

- **Current Issue**: Polkadot has 22,500 nominators, but the staking system prevents more from joining.
- **Proposal Goal**: Increase the minimum bond to allow more nominators to participate in network security.
- **Current Parameters**:
  - Minimum nominator bond: 80 DOT
  - Maximum nominator count: 22,500
- **Proposed Change**: Increase the minimum nominator bond to 120 DOT.
- **Reason**: This change aims to stabilize the network for at least a month.
- **Temporary Solution**: This is a temporary measure to buy time for a more permanent solution.
- **Feedback**: Please share your comments and feedback on the proposal.
- **Voting**: Vote on the proposal at your convenience.

Increasing nominators’ min bond on Polkadot

### Polkadot Runtime Upgrade Proposal (v9090)

- **Proposal**: Upgrade Polkadot Runtime to version 9090.
- **Details**: Release notes and changes are available [here](https://github.com/paritytech/polkadot/releases/tag/v0.9.9).
- **Breaking Change**: Developers should note a significant change in this runtime.
- **Proposal Hash**: `0x6f7f0451388d9053db17c61c67678fdd0d775f9c74dc46ebea565ad0cd52bd6e`.
- **Runtime Type**: Uses a non-compressed runtime.
- **Verification**: Use `srtool` to verify the proposal hash.
- **Vote**: Please vote at your convenience.

Runtime v9090 on Polkadot Network

### Summary of Polkadot Staking Update

1. **Current Situation**: Polkadot has 22,500 nominators, and the staking system is currently at its limit.
2. **Proposed Change**: The team plans to update staking parameters during the next runtime upgrade.
3. **Key Change**: The minimum bond for nominators will increase from 40 DOTs to 80 DOTs.
4. **New Parameter**: A "chill-threshold" of 90% will be introduced, allowing the `chill_other` function to be used only when 90% of the maximum nominator count is reached.
5. **Reasoning**: This change aims to prevent frequent tweaks and provide stability until a more permanent solution is found.
6. **Temporary Measure**: These changes are temporary and focus on maintaining network security and stability.
7. **Feedback**: The community is encouraged to provide comments and feedback on the proposal.
8. **Details**: The preimage and encoded call data for the proposal can be found [here](https://drive.google.com/file/d/1ZdXO1y6_UUlsjaPZgNla6elaMUQgtOxS/view?usp=sharing).

Increasing nominators’ minimum bond on Polkadot

Runtime v9080 on Polkadot Network

- The proposal aims to increase the number of people who can nominate in the Polkadot network.
- Currently, existing nominators cannot change their intentions, but this will be fixed in the next upgrade.
- The new limit will allow up to 22,500 nominators, an increase of 2,500.
- Nominators must have at least 40 DOTs to participate.
- If too many people try to nominate quickly, the stake limit might need to be raised again.
- The changes will be part of the next Polkadot runtime upgrade.
- A preimage of the proposal is available [here](https://drive.google.com/file/d/1Pp8mkUkFCkYiauUAe2RXFBhzk5wgulGV/view?usp=sharing).
- Please vote on the proposal when you can.

Upgrade the nomination limits on Polkadot

- The proposal limits the number of validators to 1200.
- It keeps other parameters the same for nominators.
- The proposal needs approval from the Council and community vote.
- Discussions on minimum DOT stake limits for validators are ongoing.
- These limits aim to ensure network safety and will increase as the network grows.
- The proposal's details can be found in the preimage link.
- Background and scaling issues are explained in the last runtime upgrade post.
- Community members are encouraged to vote on the proposal.

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

### Polkadot Runtime Upgrade Proposal (v9050)

- **Proposal**: Upgrade Polkadot's runtime to version 9050.
- **Purpose**: Address scaling issues in staking.
- **Changes**: Introduce hard limits on the number of nominators, configurable by governance.
- **Details**: Find release notes, runtime changes, and hash [here](https://github.com/paritytech/polkadot/releases/tag/v0.9.5).
- **Previous Discussions**: Available [here](https://matrix.to/#/!OwgojQyBzTlUQGGLhq:matrix.parity.io/$EVsIkHKQaZHNrnOCSrLWwE918yPa3u6srpziFs4usvo?via=matrix.parity.io&via=matrix.org&via=corepaper.org).
- **Staking Election Issues**: Discussed by Wei [here](https://corepaper.org/polkadot/staking/).
- **Blogpost**: Explanation of staking changes [here](https://polkadot.network/polkadot-and-kusama-staking-changes/).
- **Action**: Vote at your earliest convenience!

Runtime v9050 on Polkadot Network

### Summary of the Proposal

- **Issue**: Validator nodes on Polkadot encounter a "allocator failed to allocate memory" error during staking elections.
- **Cause**: The error occurs because the offchain worker thread, running in WASM, has limited memory.
- **Current Solution**: Increase the overall WASM runtime memory pages, affecting both block execution and offchain worker.
- **Expected Impact**: This change is expected to have no notable effect on the main runtime's progress and execution.
- **Memory Allocation**: Memory is allocated in "pages" (called "Heap pages"), with a default of 1024 pages currently used.
- **Temporary Fix**: This proposal is a temporary solution until a permanent fix is implemented.
- **Permanent Fix**: Kian from Parity is working on a long-term solution to separate the memory configurations for the offchain worker and main runtime.
- **Rejection**: The team has decided to reject this proposal as the heap pages increase is included in an upgrade.

Increasing the WASM heap pages.

Runtime v30 on Polkadot

Upgrade of Polkadot runtime to v29

- Proposal 10, a `force_transfer` proposal, is invalid due to changes in Address formats.
- The proposer used the wrong method to submit the proposal.
- Proposal 10 has been replaced with Proposal 11, which is currently up for vote as Referendum 18.
- The proposer requests to cancel Proposal 10 and clean the queue.
- A preimage for canceling Proposal 10 is available [HERE](https://drive.google.com/file/d/1W9v7a6LPvO6MzpCy0VahxtRTxv7swcZi/view?usp=sharing).
- Voting to cancel Proposal 10 will help maintain the proposal queue.

Cancellation of Proposal 10 on Proposals queue

**Polkadot Runtime Upgrade (v28)**

- **Voting:** Motion 62 is up for vote to upgrade Polkadot to version 28.
- **Treasury Tips:** Introduces slashing for treasury tips.
- **Council Governance:** First-time participants can join the Council for free.
- **Treasury Pallet:** Refactored to improve functionality.
- **Validators:** Session keys updated to support parachains.
- **Account Providers:** Reference counting for account existence providers.
- **Multiaddress Format:** Extended format now used in all runtimes.
- **Details:** Full release notes and changes are available [here](https://github.com/paritytech/polkadot/releases/tag/v0.8.28).

Upgrade of Polkadot Runtime to v28

- The proposal suggests a gradual increase in the number of validators in the network.
- It plans to add 1 validator per day for 100 days.
- This will result in a total increase of 100 validators.
- The process can be canceled at any time, allowing the community to review network metrics.
- The goal is to avoid a sudden increase in validators, which could impact the network.
- The proposal follows recommendations from the parachains team.
- A detailed preimage of the proposal can be found [here](https://drive.google.com/file/d/1idocvPtKKMQA36lzG4Upxcb4OXGMUeBW/view?usp=sharing).

Gradual increase in the number of validators

Upgrade to Polkadot runtime v27

### Summary of Polkadot Council Motion 43

- **Issue**: A bug in the Polkadot v26 runtime caused incorrect slashing of candidacy bonds for council members.
- **Fix**: The bug was fixed, and now the council aims to refund those affected.
- **Motion 43**: This motion proposes to reimburse candidates and runners-up who were slashed due to the bug.
- **Verification**: To verify the refund list, check the [gist](https://gist.github.com/kianenigma/93c3a86a72823a3f703c442e00929a0a) generated from a specific code snippet.
- **Process**: The motion uses a `utility.batch` to create a single batch of transfers from the treasury to the affected accounts.
- **Voting**: Councillors are encouraged to vote on the motion. If it passes, the proposal will be voted on by the community.
- **Original Post**: The full details can be found [here](https://polkadot.polkassembly.io/post/165).

Incorrect Slashing on Council Caused by elections-phragmen Pallet Bug

**Motion 38** is about upgrading the runtime to version 26. Here are the main points:

- **Upgrade Priority:** Medium
- **Changes:**
  - Fixes logging of target names with dashes.
  - Stops actively opening old substreams.
  - Marks `queryStorage` and `storagePairs` as unsafe RPC functions.
- **Details:** You can find the full release notes and hash [here](https://github.com/paritytech/polkadot/releases/tag/v0.8.26).

Runtime upgrade to v26

### Summary of Referendum 7 Failure

- **Referendum 7** was passed by both the Council and the community.
- The referendum was supposed to be executed after a certain number of blocks.
- The required number of blocks was set to **0 (zero)**, which caused the referendum to fail.
- The code checks if the target block number is in the past, and **0** failed this check.
- If the number of blocks had been **1**, the referendum would have been executed in the next block.
- The proposer is now **re-proposing** the same motion to the Council.
- The goal is to have the motion passed again and added to the referenda queue.

Proposal to gradually increase the number of validators

- The proposal limits the number of validators to 1200.
- Nominators' parameters remain unchanged (20000/20DOTs).
- It started as an external motion, needing community vote after Council approval.
- Discussions on minimum DOT stake limits for validators are ongoing.
- These limits aim to ensure network safety and will increase with network growth.
- The proposal's preimage is available [here](https://drive.google.com/file/d/1W8J1zSPobzNMSAoAWaSeTWvLRI7QdmwH/view?usp=sharing).
- More context and scaling issues are explained in the [last runtime upgrade post](https://polkadot.polkassembly.io/motion/88).
- Please vote when you can!

- **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 about 7 days after being fast-tracked by the Technical Committee (TC).
- Councillors can verify the presage hash [here](https://polkadot.polkassembly.io/post/93#3baa6f49-06c7-4d47-9cb8-44bd19f789d6).
- Original proposal details are available [here](https://polkadot.polkassembly.io/post/93).

A proposal to gradually increase the number of validators

### Summary of Referendum and XCM Execution

1. **Referendum Passed**: A referendum to open a channel to HydraDX was approved.
2. **XCM Execution**: The XCM message was sent and executed on Polkadot.
3. **Channel Not Opened**: Despite execution, the channel wasn't opened due to insufficient funds in Zeitgeist's sovereign account on Polkadot.
4. **Funding Issue**: The account lacked the necessary funds to reserve for opening the channel.
5. **Solution**: The account has now been appropriately funded.
6. **Next Step**: The XCM message can be resent to open the channel.

Democracy External Proposals