### Polkadot Runtime Upgrade Proposal (v9370)

- **Purpose**: Upgrade Polkadot to runtime version 9370.
- **Key Changes**:
  - Improved contract address derivation.
  - Fixes for fast-unstake for accounts with slashing.
  - NFTs 2.0 update.
  - Scheduler agenda cleanup migration.
  - Update of weights to version 0.9.37.
- **Status**: Submitted as an external motion, pending Council approval and community referendum.
- **Voting**: Community members can vote after Council approval.

Runtime Release v9370 for Polkadot

Unbrick Zeitgeist Parachain

### Bittensor Project Proposal Summary

- **Issue**: Bittensor used the wrong para ID (2096) in its genesis WASM during Auction #36.
- **Problem**: The chain cannot produce blocks with the incorrect para ID.
- **Solution**: Propose to update the genesis head from 2096 to 2097 using `forceSetCurrentHead`.
- **Proposal Hash**: 0x457da305f86a09bad84a8c557bb89628b9b39707819df0b12458d84a255d6354
- **Status**: Preimage submitted.

Update genesis state WASM to 2097 

### Parachains v9370 Release Summary

- **Release Version**: v9370
- **Main Update**: Adds OpenGov origins to Statemine.
- **Corresponding Relay Chain**: Updates align with v9370 Relay Chain runtimes.
- **Statemint Upgrade**: Authorized upgrade with hash `0x01029985e134020e8a1e2e211afcd5ac9ec6a2fd21dfb5e1c39b3b670f4415e90406`.
- **Collectives Upgrade**: Authorized upgrade with hash `0x0102dcc6cda49b51efbe0fd184b974074d1258ca9f15b9fccfedc35b7dee6e1ab9e9`.
- **Polkadot Transaction**: Transaction sent with details in hash `0x1a0008630001000100a10f0204060202286bee8801029985e134020e8a1e2e211afcd5ac9ec6a2fd21dfb5e1c39b3b670f4415e90406630001000100a50f0204060202286bee880102dcc6cda49b51efbe0fd184b974074d1258ca9f15b9fccfedc35b7dee6e1ab9e9`.
- **Proposal Hash**: `0x75df893fe3cd4e5960179865bef1291225df793082a46e721a786b3ce463471a`.

Upgrade System Parachains to v9370

### Zeitgeist Parachain Fix Proposal

- **Issue**: Zeitgeist's parachain on Polkadot and Kusama couldn't produce blocks due to a ParaId mismatch.
- **Cause**: The runtime used a different ParaId than the one for the parachain auction.
- **Remedy**: Update the chainspec to use the correct ParaId (2092) and provide a new runtime.
- **Council Proposal**: Request for the Technical Council to fast-track the proposal as a technical fix.
- **Proof of Authenticity**: The manager of ParaId 2092 provided a signed statement approving the fix.
- **Community Decision**: If approved by the Council, the community will vote on the proposal in the referenda queue.
- **Note**: This proposal aims to fix the issue faster than a previous proposal (Referendum 103) that has a longer enactment period.

### Polkadot Upgrade Proposal (v9360)

- **Purpose**: Upgrade Polkadot to version 0.9.36.
- **System.setCode Hash**: `0x5f48aacbbd94a881a3ce5a496e1d852f21cffe33d1f7592023f2140254683d20`
- **Runtime Changes**:
  - Store last min-active-bond on-chain.
  - Automatic withdraw_unbonded upon unbond.
  - Warn on missing pallet::call_index.
- **Misc Changes**:
  - Use log_target in consensus-related crates.
  - Fix wrong rate limit and add logs.
  - Update weights for version 0.9.36.
- **Process**: Requires approval by the Polkadot Council and community vote.

Runtime Release v9360 for Polkadot (replacing motion 333 due to length issues)

### Summary of Proposal

- **Objective**: Enable pre-checking for runtime upgrades on parachains.
- **Process**: Validators must compile and approve the new runtime before it can be used.
- **Benefit**: Reduces the risk of failures and unjustified slashes.
- **Testing**: Successfully tested on Versi, Rococo, and Westend.
- **Requirement**: Parachains need to support `go_ahead_signal`.
- **Call to Enact**: [Link to call](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.dotters.network%2Fpolkadot#/extrinsics/decode/0x332901).
- **Action Needed**: Review and vote on the proposal.

Setting pvfCheckingEnabled In The Configuration To TRUE

### Parachains v9360 Update Summary

- **Release Version**: v9360
- **Relay Chain Updates**: Corresponds to v9360 runtimes.
- **Statemint Changes**:
  - Updates to the Assets pallet.
  - Breaks transaction version; wallets need updates.
- **Collectives Parachain Changes**:
  - Merges Founder/Fellow roles into one "Fellow" role.
  - Removes veto power.
  - Allows Fellows to step down to Ally.
- **Authorize Upgrade Links**:
  - [Statemint](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fstatemint-rpc.polkadot.io#/extrinsics/decode/0x010239127c43fb7051d78dd91eb724b087607cb09bc046824b0d52e0a48981943e68)
  - [Collectives](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpolkadot-collectives-rpc.polkadot.io#/extrinsics/decode/0x0102de7616501046da7138c35e0b4699bf403a09523533f30e0e5180dbb5fb8fec4d)
- **Proposal Hash**: `0xa730cdb8c4b933b9e9ced277e63e79f0f52c0159f78bf60037f6ba312324051f`

Upgrade Polkadot System Parachains v9360

### Bitgreen Parachain Upgrade Summary

- **Upgrade Execution**: The Bitgreen parachain was upgraded from a shell runtime to the latest runtime code at block 191202.
- **New Pallets**: The upgrade introduced new pallets, including `pallet-parachain-staking`, which assigns new validators.
- **Issue**: After the upgrade, new sessions set authorities to an empty set due to missing initial values in `pallet-parachain-staking`.
- **Solution**: The team proposes a technical rollback to resolve the issue.
- **Request**: The proposal is requested to be fast-tracked by the Technical Committee (TC).
- **Past Precedents**: Similar parachain resets have been fast-tracked in the past.
- **Proposal Details**: The proposal hash is `0xfc0c33d0c0ae08d940fddadb11e239710da69b8660eaae7f77ea102a331e4ebe`, and the preimage is submitted.

Unbrick Bitgreen Parachain

### Polkadot Upgrade Proposal Summary

- **Upgrade to v9340**: Polkadot is proposed to upgrade to version 9340.
- **Runtime-only**: This upgrade only affects the runtime, not the node client.
- **Replaces v9320 and v9330**: The new runtime will replace the previous versions.
- **Proposal Hash**: The proposal has a specific hash: `0xace5dccb8eecfab754154a27c370a513d79d4fcda40f5837be1c0f129cdf4726`.
- **Council Approval**: The proposal needs approval from the Polkadot Council and then a community vote.
- **Multisig Calls**: Multisig calls that are not fully signed will not execute after the upgrade.
- **Preimages and Dispatch Queue**: All preimages and the dispatch queue will be cleared, affecting ongoing referenda.
- **Upgrade Date**: If approved, the upgrade is planned for January 14.

Runtime Release v9340 for Polkadot

- **Polkadot Alliance**: A group of seven leading projects on Polkadot (Acala, Astar, Interlay, Kilt, Moonbeam, Phala, and Subscan) have formed to set standards and ethics for open-source development.
- **Purpose**: The Alliance aims to support high development standards and identify bad actors within the Polkadot ecosystem.
- **Membership**: Members are expected to be companies, projects, or networks within the Polkadot ecosystem.
- **Functions**: The Alliance manages membership, publishes rules, and curates an "Unscrupulous List" of harmful websites and accounts.
- **Ranks**: There are two ranks: "Fellow" (with voting rights) and "Ally" (without voting rights).
- **Joining**: New members can join by depositing 1,000 DOT or being nominated by a Fellow.
- **Promotion**: Allies can be promoted to Fellows if they meet criteria like significant code contributions or educational efforts.

The Seeding of the Polkadot Alliance: Fighting for an open source culture and open collaboration that benefits the Polkadot ecosystem

On chain council motion

### Kapex Parachain Issue Summary

1. **Introduction**: The Kapex Parachain on Polkadot has been producing blocks but cannot be upgraded due to a coding error.

2. **Audit Findings**: A security audit by SRLabs found illegal code in the Transaction Payment Pallet, which was adapted from the standard version.

3. **Upgrade Failure**: The illegal code prevents the parachain from being upgraded, as it is called during the upgrade process.

4. **XCM Vulnerability**: The parachain also cannot fix a security vulnerability discovered in September.

5. **Fix Attempts**: Efforts were made to fix the issue without involving the Council and Referendum process, with help from Kilt.io and Parity teams.

6. **Testing the Fix**: The fix was tested on development and staging networks, upgrading versions from `v1.2.0` to `v1.3.0`.

7. **Production Preparation**: Steps were taken to prepare for the production fix, including updating the chainspec and creating a new docker image.

8. **Referendum Needed**: The community's support is needed to pass a referendum to fix the issue and allow the distribution of Crowdloan funds.

Kapex Parachain - Validation Code Substitution to fix broken upgrade mechanism and permit XCM Security Vulnerability upgrade.

- Proposal hash: `0x98b3a8aa425c1e1ca5cd96d1b8f3491233b0745575e648a8c5497e83cec76f16`
- Aim: Increase the limit of nomination pools from 64 to 128 in Polkadot.
- Initial limit: Set at 64 to prevent risks during launch.
- Current status: Everything is working as expected.
- Next steps: If the Council approves, the community will vote in the referenda queue.
- Decision: Final decision will be made by the community.

Increasing Max Number of Nomination Pools

Upgrade Statemint to v9330

### Proposal Summary

- **Purpose**: Cancel the upgrade of Polkadot Runtime to v9320.
- **Reason**: A new code check in the scheduler pallet prevents the `set_code` function from working correctly.
- **Code Change**: The check ensures that scheduled calls do not exceed the block's weight limit.
- **Issue**: The `set_code` function is annotated to use the maximum block weight, causing it to fail the check.
- **Solution**: A new proposal will be submitted to fix this issue.
- **Proposal Hash**: `0x88998cf7535c1f22d62849be8464fdc38fe46c0a46dc943ec56c91ef6592ec65`
- **Process**: The proposal needs approval from the Council and then a community vote.

Cancel the upgrade of Polkadot Runtime to v9320

### Summary

- A proposal to upgrade Polkadot's runtime to v9320 was submitted but will fail due to a code change in the scheduler pallet.
- The scheduler now checks if a scheduled call exceeds the block's remaining weight, which causes the `set_code` call to always fail.
- An external motion (306) has been opened to cancel this proposal.
- A new proposal with the correct call will be submitted soon.
- The proposal includes various updates and fixes, such as removing contracts RPCs, adapting to weightv2, and improving documentation visibility.
- The proposal hash is `0xbd78d3542767047aba0babb8c8825a5799e3ef54a21193ffe24b98eb4f895162`.
- After Council approval, the community will vote on the proposal in the referenda queue.

[PLEASE REJECT] Runtime v9320 Upgrade On Polkadot

### Tether's USDT on Polkadot

- **USDT Registration**: Tether registered USDT on Polkadot's Statemint with asset ID `1984`.
- **Governance Request**: Tether is asking Polkadot governance to make USDT sufficient for paying transaction fees and account creation without needing DOT.
- **Statemint Assets**: On Statemint, assets can be Sufficient or Non-Sufficient. Sufficient assets can create accounts without needing DOT.
- **Proposal Benefits**: This proposal would make it easier for users to hold USDT on Polkadot, boosting the ecosystem and increasing transactions, especially in DeFi.
- **Call on Statemint**: The encoded call and call hash are provided for the proposal.
- **Call on Relay Chain**: The call hash and call data for the relay chain are also provided.

Proposal for USDT Token Sufficiency on Statemint

- The proposal aims to avoid a situation where no one can change or set nominations due to the high number of nominators.
- It targets to outstrip Referendum 86, which is currently up for community vote and sets higher nomination minimum bond limits.
- The new motion suggests shorter voting and enactment periods compared to Referendum 86.
- If approved and fast-tracked, this proposal would make Referendum 86 redundant.
- Along with updating staking configurations, this proposal would cancel Referendum 86.
- The importance of higher nomination minimum bond limits is discussed in an initial post.
- The proposal is crucial as the number of nominators is close to reaching 50,000.

Redefining Slightly Nomination Minimum Bond Limits and Removing Max Number of Nominators (replacing Referendum 86)

### Summary of Polkadot Staking Changes

1. **Nomination Pools**: Polkadot is introducing nomination pools to simplify staking for DOT holders.
2. **Current System**: Nominators currently need at least 10 DOTs and compete within a limit of 50,000 to be in the top 22,500 for staking rewards.
3. **Active vs. Waiting**: Nominators are either active (in the top 22,500) or waiting.
4. **Goal**: Encourage waiting nominators to join pools and prevent new waiting nominators.
5. **Proposed Change**: Increase the minimum nomination limit to 100 DOTs to discourage waiting nominators.
6. **Buffer**: Keeping a buffer of waiting nominators is beneficial for economic security.
7. **Immediate Action**: Reject nominations with less than 50 DOTs, directing them to join pools.
8. **Original Discussion**: For more details, see the [original post](https://polkadot.polkassembly.io/post/1224).

Proposal: Slightly higher nomination limits

- **Gossamer** is a Polkadot host written in Go, designed to build and run nodes for blockchain protocols compatible with the Polkadot ecosystem.
- The proposal seeks funding for further development of Gossamer over a 12-month period.
- The project has already received initial support from the Web3 Foundation Grants Program.
- The main goal is to enhance client diversity within the Polkadot ecosystem.
- The proposal includes a budget, milestones, and a detailed roadmap.
- It is currently up for vote by the Polkadot Council and, if approved, will be voted on by the community.
- Links to the original Treasury post and discussion are provided for more information.

External Motion: #168 Gossamer Ongoing Development Grant

- The v9320 release of parachains is updated to match the v9320 runtime of the Relay Chain.
- Changes to Assets and Uniques are small.
- "Anonymous" proxy is now called "Pure" proxy.
- There are also some small bug fixes.
- Two examples of actions are "Authorize Upgrade" and "Send from Polkadot."
- A proposal with a hash is submitted for community voting.
- The Polkadot Council will first approve it, then the community will vote.
- Make sure to review and vote on the proposal.

Statemint Runtime Upgrade to v9320

### Summary of the Proposal for Common Good Parachain

- **Purpose**: Add a new "common good" parachain to Polkadot focused on collectives.
- **First Collective**: Likely the Polkadot Alliance, but will support other collectives serving the Polkadot network.
- **Kusama Involvement**: No Kusama counterpart planned; Kusama may join collectives like the Polkadot Alliance.
- **Technical Fellowship**: A group of technical experts contributing to Polkadot, with members deploying code on Kusama first.
- **Proposal Steps**:
  1. Register the parachain with a four-year lease.
  2. Runtime upgrade to the Relay Chain to recognize the parachain.
- **Referenda**: Series of votes on Polkadot for approval by stakeholders.
- **Call Details**: Finalized when Parity publishes the Collectives genesis release and the Technical Committee sets a timeframe.
- **Call Hash**: `0x9ef867bcaaee9750487738c6e6537eb52a3047c7bb2f06eb30dc05073dae90d5`

Polkadot Collectives Common Good Parachain Proposal

### Polkadot Runtime Upgrade Proposal

- **Proposal**: Upgrade Polkadot's runtime to version v9300.
- **Previous Issue**: Motion 286 replaced Motion 285 due to queue limitations.
- **Audits**: Several low-priority audits and trivial changes are pending or completed.
- **Proposal Hash**: `0xf1eeaa09f9a85633cf7f1fa588bf3247a58acf9f4cb3e8e12350833c595bc7d3`
- **Process**: Requires Council vote followed by community referendum.
- **Verification**: Use SRTool to verify the proposal hash.
- **Vote**: Community members should vote at their convenience.

Runtime v9300 Upgrade On Polkadot

**Fix for Referendum 74**

- Fixes a failed execution of Referendum 74.
- Uses a batch of Transact instructions instead of a single batch call.
- Adds a sixth pair with ParaId 2030 (Bifrost).
- Includes a force_transfer of 22 DOT: 20 for the new parachain and 2 for XCM fees.
- Requests fast tracking if it passes the Council.
- The original 5 channel requests remain unchanged.
- The fix should work on the current version of Polkadot.

Democracy Referenda