Extend Current LP7 Crowdloans

### Polkadot and Statemint Upgrade Summary

- **Polkadot Upgrade**: Polkadot will be upgraded to version **v9170**, addressing block time issues and enabling a new feature that removes the strict maximum count for nominators.
- **Statemint Upgrade**: Statemint will be upgraded to version **v700**, improving NFT class management and enabling full use of HRMP channels with other parachains.
- **Security Enhancements**: The upgrade includes fixes for issues found by independent auditors, preparing Statemint for asset and NFT creation.
- **Council Motion**: A council motion will authorize the upgrade, with a specific call hash and encoded call for the XCM (Cross-Consensus Message) process.
- **Community Vote**: The proposal will be voted on by the community after approval by the council.
- **Resources**: Detailed information about the upgrades, including release notes and runtime changes, can be found in the provided links.

Polkadot Runtime Upgrade to v9170 and Statemint Runtime Upgrade to v700

### Summary of the Proposal

- The proposal aims to temporarily increase the nomination limit to 160 DOTs, similar to [motion 157](https://polkadot.polkassembly.io/motion/157).
- This change allows the `chill_other` transaction to be used, helping to manage the number of nominators.
- The previous proposal had a major flaw: it used PLANKs instead of DOTs, the smallest unit of the DOT currency.
- The correct value for the minimum nominator bond should be `1600,000,000,000` PLANKs.
- The call data and hash for the correct proposal are provided.
- This change is necessary to keep the nomination ecosystem active while waiting for the next runtime upgrade.

Polkadot’s Update to 160 DOTs as minimum nomination limit: A follow-up proposal fixing a unit mistake

- Polkadot planned to remove the 120 DOTs nomination limit with the 0.9.16 upgrade.
- The 0.9.16 upgrade was delayed on Polkadot due to issues on Kusama.
- The number of nominators in Polkadot reached the 22,500 limit.
- A temporary increase to 160 DOTs is proposed to manage the nomination limit.
- This change allows the `chill_other` transaction to reduce the number of nominators.
- The proposal aims to keep the nomination ecosystem active while waiting for the 0.9.16 upgrade.
- The call hash and call data for the proposal are provided.
- The preimage for the proposal has been submitted.

Polkadot’s Update to 160 DOTs as minimum nomination limit: The Reason

### Polkadot Runtime Upgrade Proposal

- **Version**: v9151
- **Purpose**: Upgrade Polkadot's runtime
- **Changes**: Includes runtime cleanup and fixes, such as fixing locked deposits for council voters
- **Proposal Hash**: `0xc0d644131338cbf809cdb03afe0f7e1660b228e18011087858828ced4365d82e`
- **Verification**: Use `srtool` to check the proposal hash
- **Voting**: Vote at your convenience to upgrade as soon as possible
- **Next Steps**: Prepare for the next runtime upgrade

Polkadot Runtime Upgrade to v9151

### Polkadot Runtime Upgrade v9150

- **Proposal**: Vote on upgrading Polkadot Runtime to v9150.
- **Details**: Includes runtime cleanup and fixes, such as addressing locked deposits in council voters and Nicks pallet.
- **Hash**: `0x960d3ad3f42eb41ab2131e1561dd8cc20f87585e37d2d1b02525578204f11d4b`
- **Verification**: Use `srtool` to check the proposal hash.
- **Vote Recommendation**: Initially, vote to upgrade as soon as possible.
- **Update**: Advise voting `Nay` on Referendum 49 due to missing companion changes for Polkadot.
- **Kusama**: Likely to propose an additional runtime upgrade to revert the issue.
- **Mainnet**: Avoid risks until the issue is resolved.

Runtime v9150 on Polkadot Network

Redspot v0.1, applied by Patract Labs

- Shell upgraded Statemint to use new keys, but there was a key type mismatch.
- Aura uses sr25519 keys, but Statemint's keys were ed25519.
- A temporary fix was made by creating a new runtime to allow ed25519 keys in Aura.
- This fix will let validators check collator signatures.
- Once blocks are produced, Aura will switch back to sr25519 keys.
- The call hash for this change is `0x0e21b5233c7591ee89eca0cae71cf9a9a4c45fe2393075ab33361a673f5d322d`.
- The preimage for this change is shown in the image link.

Fix Statemint - Aura Key Scheme

- This is a follow-up to Referendum 46, which failed due to no default XCM version set in Polkadot.
- A protection was added to prevent the Relay Chain from sending messages without a safe version, after a previous vulnerability.
- This is the first cross-chain interaction for Polkadot, so the version was not initialized.
- The new batch includes the same two calls as Referendum 46, plus an additional call to set the default XCM version to 2.
- The images show the details of the calls and the XCM version setting.

Upgrade Shell to Statemint (with XCM Fix)

### Summary of Scheduled Transactions

1. **Two Transactions**: Two transactions are scheduled to ensure `set_storage` happens before the upgrade authorization.
2. **Set Storage**: The first transaction sets storage keys in Shell for Statemint's "genesis".
   - Includes setting Aura collators and `SafeXcmVersion` to `2`.
3. **Authorize Upgrade**: The second transaction authorizes the upgrade to Statemint.
   - Once authorized, the runtime can be submitted for upgrade.
4. **Shell Constructions**: Both transactions are constructed on Shell and dispatched via XCM from the Relay Chain.
5. **Polkadot Proposal**: The proposal schedules these messages to dispatch from Polkadot to Shell, ensuring they are processed separately.
6. **Call Hash**: The call hash for the proposal is `0xa6830793b6a3473f66fbd7305a9e330dd2dd688df0e8fcbd0c9ff08d28040a34`.

Upgrade Shell to Statemint

### Polkadot Runtime Upgrade Proposal (v9140)

- **Proposal**: Upgrade Polkadot Runtime to version 9140.
- **Purpose**: Disable xcm teleports and reserve transfers.
- **Reason**: Prerequisite for upgrading Shell to Statemint on the network.
- **Proposal Hash**: `0x317c7862dc523bd083e4dd6545079bdc18058f561bada9e5e5646935b1cc04af`
- **Details**: Release notes and changes are available [here](https://github.com/paritytech/polkadot/releases/tag/v0.9.14).
- **Verification**: Users can check the proposal hash using srtool.
- **Vote**: Please vote at your convenience.
- **Note**: This is a runtime-only release.

Runtime v9140 on Polkadot Network

### Summary of Proposal

- **Token Registration**: BNC native token (Bifrost on Kusama) will be registered as xcBNC on Moonriver.
- **Details**:
  - Multilocation: `{ "parents": 1, "interior": {"X2": [ { "Parachain": 2001 }, { "GeneralKey": "0x0001" }]}}`
  - Decimals: 12
  - Name: xcBNC
  - Symbol: xcBNC
- **Fee**: Initial fee is set at 35230000000000 units per second, based on the KSM/BNC price ratio.
- **Proposal**: Proposal #15 with hash `0x389689c01cc484fa3860ff93a138f0f283611243e1c6b80d3c49f25b129999fb`.
- **Technical Steps**:
  - Register the asset using `assetManager.registerAsset`.
  - Set the fee using `assetManager.setAssetUnitsPerSecond`.
  - Store a revert code using `system.setStorage` for smart contract interaction.
- **Asset ID**: xcBNC will have the asset ID `42109858202732255156900361585267092733`.
- **XC-20 Address**: The XC-20 address will be `0xFffFFFfF1FAE104Dc4C134306bCA8e2E1990aCfd`.

Register Bifrost (on Kusama) native token as xcBNC on Moonriver

Increase active collator set size to 28

### Polkadot Runtime Upgrade Proposal

- **Proposal**: Upgrade Polkadot Runtime to version 9122.
- **Purpose**: Supports the first auctions and crowdloans on the Polkadot Network.
- **Hash**: `0x0f598b97de6adfb2c5edffb7e8e5aed6408d29382a9de372ed229391a20c4a86`.
- **Verification**: Use srtool to check the proposal hash.
- **Release Type**: Runtime-only; no node upgrades required.
- **No Binaries**: No new binaries, packages, or Docker images created.
- **Voting**: Vote at your convenience.
- **Details**: Full release notes and changes are available [here](https://github.com/paritytech/polkadot/releases/tag/v0.9.12-1).

Runtime v9122 on Polkadot Network

Proposal to Onboard Shell on Polkadot

### 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.

Proposal for First Parachain Auctions on Polkadot

Authorize runtime upgrade to v0.3.9

- 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

Align existential deposits of foreign assets with ZTG #16

### 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

### Advisory Committee Prime Member Election

- **Purpose**: Elect the first prime member of the Advisory Committee.
- **Role**: Oversees market approvals, registrar regulations, and enforces community guidelines.
- **Decentralization Goal**: Aim to include more community members.
- **Recent Change**: Since version 0.3.9, a single vote no longer approves markets.
- **Prime Member Role**: Resolves abstentions at the end of proposal durations.
- **Internal Vote**: Current advisors have voted internally.
- **Public Scrutiny**: Proposal aims to make this decision transparent.
- **Links**: Internal voting details are available on Subscan.

Elect first prime member of the Advisory Committee - public proposal #13

### 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).

Democracy Referenda