The proposal aims to upgrade Kusama's runtime to [v9340](https://github.com/paritytech/polkadot/releases/tag/v0.9.34): more information about Gov2 can be found in the release notes.  **Runtime**  \[S\] ✅ audited [#12310](https://github.com/paritytech/substrate/pull/12310) Low - Asset pallet: support repeated destroys to safely destroy large assets  \[S\] ⏳ pending non-critical audit [#12730](https://github.com/paritytech/substrate/pull/12730) Low - Allow alliance fellows to give up voting rights  \[P\] ✅ trivial [#6326](https://github.com/paritytech/polkadot/pull/6326) Low - Add collectives as trusted teleporter  \[P\] ✅ trivial [#6366](https://github.com/paritytech/polkadot/pull/6366) Low - OpenGov: Proxy definitions  \[S\] ✅ trivial [#12808](https://github.com/paritytech/substrate/pull/12808) Low - Bounties use SpendOrigin  \[S\] ✅ trivial [#12610](https://github.com/paritytech/substrate/pull/12610) Low - Non-interactive staking  \[S\] ✅ trivial [#12842](https://github.com/paritytech/substrate/pull/12842) Low - OpenGov: abstentions  \[P\] ✅ trivial [#6390](https://github.com/paritytech/polkadot/pull/6390) Low - Allow Root with OpenGov origins  \[S\] [#12848](https://github.com/paritytech/substrate/pull/12848) Low - Add `with_weight` extrinsic  \[P\] ✅ trivial [#6372](https://github.com/paritytech/polkadot/pull/6372) Low - OpenGov: Kusama tweaks   Proposal hash: `0x0debc0e862468363f53cf1ea4d451ec2fdfc4aeb37a3189354df9597636c55b9`  Note this proposal is submitted with `set_storage` call, not `set_code` call (more info on why `set_code` won't work can be found on [this post](https://polkadot.polkassembly.io/motion/306)).  Preimage:  ![](https://i.ibb.co/bbKw1tx/Screenshot-2022-12-07-at-09-53-08.png)  You can review the hash and changes in the release notes and use `SRTool` to verify the proposal hash - make sure to vote at your convenience! This proposal is submitted as an **external motion**: meaning after the Council vote, the community will need to vote on the proposal in the referenda queue.

proposalHash

votingPeriod

delay

Runtime v9340 Upgrade On Kusama: Fixing OpenGov Parameters and more!

This is a techincal committee proposal whose proposer address (FhLMxxkXxfgRRnv8hyRbNkpUMZ9umASMsRmKpZruVayaqhL) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Fixing the Last Auctions From The Auctions Schedule - Kusama Network

This proposal (hopefully the last one for Council) is now up for vote on Kusama:

With the [v9320 runtime upgrade](https://kusama.subsquare.io/democracy/referendum/244), an issue with migration appeared: the migration did not work for preimages submitted before the upgrade as well as for proposals approved by the community and on dispatch queue. This included:  
- [Genshiro's proposal](https://kusama.subsquare.io/democracy/referendum/246) to swap slots, already approved by the community and on dispatch queue.
- [Kintsugi’s proposal](https://kusama.polkassembly.io/referendum/242) to open an HRMP channel with Statemine, already approved by the community and on dispatch queue.

In order to make sure the approval by the community is held as true, we aim to vote again on these two proposals to have then enacted as decided by the community, in time. For this, the proposal is composed by a `batch` call including: a `forceOpenHrmpChannel` (for Kintsugi and Statemine) with a `forceTransfer` call from treasury to pay for the cost of the channel opening, and a `registrarSwap` call (for Genshiro). We aim to vote this ASAP to pass it to vote. Preimage is submitted. 

- Call hash: `0x83c439b8b621a3507c90c8a3ebd0c4b3d76962f853e1f11858e665aeafaeac14`
- Call data: `0x1804140402006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000b00a0724e18093c07e80300002c080000e8030000009001003c072c080000e8030000e8030000009001004603b2080000e80700004603e8070000b2080000`
- Composition can be found [HERE](https://i.ibb.co/b6VZ48J/Screenshot-2022-11-23-at-15-29-48.png) and [HERE](https://i.ibb.co/pn03Ssm/Screenshot-2022-11-23-at-15-29-56.png).

Please vote at your convenience! This is submitted as an external motion: after Council approval the community will vote on this. 

Fixing the disappeared approved proposals (by the community) on relaychain from Genshiro and Kintsugi

External Motion: Approval of Treasury Proposal 227 - KAGOME C++ implementation

This is a techincal committee proposal whose proposer address (F2i6trfXqFknbgB3d9wcd1X98WWdLLktmFtK8Beud75bjTW) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Statemine Runtime Upgrade to v9320

Un-brick Basilisk via paras.forceSetCurrentCode

Runtime v9320 Upgrade On Kusama Network

Extending Encointer's common good lease by 48 weeks

Taking into account the discussion and aiming to achieve consensus, **an external motion** puts forward the vote for treasury proposal by **Fearless**, focused on a browser extension for Chrome and Mozilla, as well as a desktop application for windows, which includes asset, wallet and network management flows, dApp connector logic support and more. Note that this is **an external motion**, leaving the final decision up for the community vote as a referendum. Further information can be found on the [motion post](https://kusama.polkassembly.io/motion/561). The team is here to answer any questions or comments. 

All info on the treasury proposal can be reviewed below.
______________________________________________________________

### #212 Fearless Wallet Desktop/Browser Plugin Proposal

- Link to the original proposal can be found [HERE](https://kusama.polkassembly.io/treasury/212).

- The discussion on the proposal, DMCA action and open source license of the code can be found [HERE](https://kusama.polkassembly.io/motion/551) and [HERE](https://kusama.polkassembly.io/post/1817) (reason why this proposal is submitted on-chain as an external motion). 

This proposal is focused on:

- A browser extension application for Chrome, all chromium based browsers (that support browser extensions) and Mozilla Firefox. In terms of the proposal, our team will design and develop a Browser extension application with a widget style interface that is compatible with and similar to (some extent) the Fearless Wallet mobile app (iOS/Android).

- A desktop application for Windows, macOS and Linux. Using Electron SDK it is possible to build Desktop apps for various operating systems with little effort. These desktop apps can be built from the same code base as the aforementioned Browser extension.

- Wallet, network and asset management flows. We will cover the most important and necessary flows such as: wallet creation and import, handling many wallets, switching between several networks along with the “All networks” state, The main asset flows such as: send, receive, transaction history, teleport (cross-chain transfer), buy assets for fiat by means of Moonpay and RAMP services will also be covered.

- Settings and chain account management flows. Main wallet flows aside, users need to have tools to manage their wallets, chain accounts, localisation, currencies, nodes, etc. The “Settings” set of features will be a solution to that. More detailed information about the corresponding flows is provided below in Section 3. Feature set of the proposal.

- dApp connector logic support. We will develop a service that will allow a direct connection between the Fearless Wallet (iOS/Android) application and Browser extension to sign all dApp transactions.

The amount requested for the first submission is $268,400.00. The amount in KSM is 6,389.41 taking into account KSM EMA (7) rate provided by Subscan service KSM prices (USD) for October, 3rd. The amount will be recalculated according to the 7 day average KSM rate, using the high and low of the week on Coingecko, at the day of on-chain action after the discussion process ends.

**The 1st milestone includes:**

- Browser extension for Chrome, all chromium based browsers and Mozilla Firefox

- Desktop application for Windows, macOS and Linux

- Wallet, network, and asset management flows

- Settings and chain account management flows

- dApp connector/signer logic support




External motion: Approval of Treasury Proposal 212 - Fearless Wallet Desktop/Browser Plugin Proposal

Runtime v9300 Upgrade On Kusama

Statemine Runtime Upgrade to v9290

Runtime v9291 Upgrade On Kusama

WagMedia Request To Top Up Bounty #12

Statemine Runtime Upgrade to v9271

 [PLEASE REJECT] Kusama Runtime Upgrade to v9290

The proposal (the first step of an experiment ideated by paulo // turboflakes.io) aims to proof governance can control two anon proxies that will then be used to manage treasury funds to participate in two specific nomination pools. These pools will focus on over-accomplished 1kvP validators. 

Please note this motion is the first step for a larger proposal that can be reviewed [HERE](https://kusama.polkassembly.io/post/1633). The proposal aims to enact the following [preimage](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x1802081803000181fd5707c1e314bdccbe80a311121ce074cebdc0dead2bbcb1cb0c127aca5f8e0001544c657373205472757374204d6f72652054727574681803000181a7c6cac2bac3e3fae246e998f1d05eb36aa59c3345fedb09a3828eee7ec762000130457870656374204368616f73) to be executed via Governance, to test control over the accounts mentioned in the post. 

Please review and vote at your convenience! If this motion is approved by Council, the proposal will pass to referenda queue to be voted by the community. 

- Original proposal discussion: [HERE](https://kusama.polkassembly.io/post/1633)
- Overall idea (with 2 steps explained): [HERE](https://hackmd.io/G1xhVuF3TwCo_AxrZQRALw)
- Preimage submission:  [HERE](https://kusama.subscan.io/extrinsic/14361315-5)

Bootstrap ONE-T Nomination Pools: STEP 1 (testing the anon proxies)

Runtime upgrade to 9280

This is a follow-up proposal to motion [#495](https://kusama.polkassembly.io/motion/495), which limited the number of nomination pools to 64 in Kusama (and 16 members per pool) to prevent the spread of a bug regarding the reward payout. [Runtime 9271](https://kusama.subsquare.io/democracy/referendum/225) (enacted in block #14,248,044) contains a fix for this bug, **and the staking team has observed no further issues with nomination pools.**

Therefore, this proposal aims **to lift the limits imposed on the nomination pools by motion 495**: the new limits are 256 total pools and 1024 members per pool. Recall that even these limits are just a safeguard and in practice no limit on the number of pools and members per pool exist. 

Please make sure to review the proposal hash (the construction can be found [here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x290a00000100010000000100040000)) and vote at your convenience! - preimage has already been submitted. 

Update to Nomination Pools on Kusama

Runtime Upgrade to 9271

Statemine Upgrade to Runtime v9270

This is a proposal to extend the lease of Statemine, a common good chain dedicated to balances and fungible and non-fungible assets, by about two more years (16 lease periods).

Besides continuing its role as an entry point into the Kusama network for assets, especially those backed by off-chain reserves, in the next year Statemine will also start taking on more "system level" functionality, namely regarding KSM balances. With the rollout of XCMv3 and additional features like asset locking over XCM, future chains dedicated to subsystems like staking and governance will rely on Statemine to lock KSM for use in other parachains.

While this two-year lease is longer than leases available on auction, it is meant to represent Statemine becoming an extension to the Kusama protocol itself.

Releases are published in the [Cumulus repo](https://github.com/paritytech/cumulus/releases).

If people agree that this proposal as configured is worth a vote, then we will put it to public referendum.

Hash: `0x4272f0f5d52548e488339bf52861af98904a7f7509b5a067c1ba713b4af813e8`

![](https://i.ibb.co/gWw1yHT/Screenshot-2022-08-10-at-08-41-13.png)

Statemine Common Good Lease Renewal

Encointer Runtime Upgrade v8

Parallel-Heiko lease swap before the LP22 ends

Based on community requirements on the [Standard Guidelines to judge Liquidity Treasury Proposals](https://polkadot.polkassembly.io/post/951), this is an **external motion**: meaning it will be voted by council and community in order to be executed succesfully. 

________________________________________________________________________________________________________

In this proposal Equilibrium / Genshiro team aims to attract liquidity into Genshiro’s money market and DEX, incentivise KSM / EQD market liquidity and margin trading, further KSM network effects and benefit ecosystem with a first real margin trading and borrowing use case. Please follow the link below for the original post and proposal details:

Link to the proposal and original discussion post: [HERE](https://kusama.polkassembly.io/post/1630). 

 Liquidity funding proposal for Genshiro Money Market and DEX

Kusama runtime upgrade v9260

Kusama Runtime Upgrade to v9250

Bifrost is equesting a KSM initial liquidity subsidy for their KSM staking liquidity derivative - vKSM. The team aims for this allocation to further improve the incentives for users to nominate and pledge tokens, to provide liquidity for staked KSM and promote the capital utilization of KSM in various defi scenarios and applications and to further improve the incentives for users to nominate and pledge tokens. All info on the initiative based on the Liquidity Standard Guidelines can be found on [the proposal](https://kusama.polkassembly.io/treasury/177): thank you to the community for leaving your feedback! **Please note the motion is an external motion to be voted by Council and after by the community** (I made a mistake on **motion 503**, passing it for Council vote only: please reject that one as this is an error). 

Previous discussion: [https://kusama.polkassembly.io/post/1606](https://kusama.polkassembly.io/post/1606)

Treasury proposal: KSM initial liquidity subsidy for KSM staking liquidity derivative - vKSM

Statemine: Runtime Upgrade on v9230

Changes in Nomination Pools Requested By The Staking Team

Kusama Runtime Upgrade to v9230

 Proposal for RMRK token sufficiency on Statemine: An Amended Proposal (the third time is the charm)

Kusama Runtime Upgrade to v9220

Swap Lease For Shiden (2007 to 2120), At Team’s Request

Kusama Liquidity/Reward/Bridge Subsidy for Stableswap (USDT-USDC-aUSD)

Proposal for USDT token sufficiency on Statemine

Kusama runtime upgrade to version 9200

Swap Leases for Moonriver and Khala

The RMRK team has been at the forefront of NFT innovation for the past year, inspiring both collaborators and clones in and outside of the Dotsama (Polkadot and Kusama) ecosystem.

Based on our growing social media followership and community engagement as well as the number of projects being launched on the current version of RMRK and planned on the new iterations, there is a clear demand for the technology that we are building. Since we started in April 2021:

- 6700 collections live
- Total volume of over 500’000 KSM including secondary sales
- A total of over 30000 unique accounts have listed NFTs on RMRK’s platforms, resulting in current numbers of over 16500 distinct owners of RMRK1 NFTs and over 28500 distinct owners of RMRK2 NFTs: a total of over 35000 currently active collectors

The NFT 2.0 functionality we have pioneered is also seeing heavy use. To date:

- Almost 100’000 multi-resource NFTs have been launched, NFTs that are multiple things at the same time (a song with a visualization, a profile pic with a static output and a composable one, an ebook that has an audio book counterpart).
- Over 50’000 equippable NFTs have been launched, with 50 new equippable collections underway and in active development. These are NFTs that can be placed into other NFTs, but are otherwise stand-alone. They are often cross-collection compatible, ushering in a “global item economy”.

With our EVM and Rust versions in MVP stage, we are on the precipice of being integrated with the majority of the Dotsama ecosystem chains.

Thus far, the technology has been largely independent of [$RMRK token](https://singular.app/tokens) use, allowing free and ungated experimentation, building, and ecosystem expansion for both partners and competitors in any direction they choose - with or without our token, and yet, looking at RMRK token activity, there is a clear community demand for more utility and easier use:

- over 4000 holders on Moonriver, Bifrost, Karura
- over 4300 diverse holders on Statemine alone
- Tens of thousands of holders on Kucoin and Gate.io
- over 11% of all RMRK has been bridged over to Moonriver
- ~35 million USD in weekly volume on Kucoin alone

However, with the soon to be released new utilities of the RMRK token, we are encountering multiple pain points related to the token’s presence on the Statemine common good chain.

Notably, our community are experiencing difficulties with regards to transfers, withdrawals, and trading, and these experiences are not only impacting the use of centralized and decentralized exchanges, but also encumbering the development of our [Skybreach metaverse](https://skybreach.app), the intended crown jewel of our project, and a value add for DotSama.

## The Problem

Statemine is a common good parachain in the Kusama ecosystem intended as a common ledger of basic balances of fungible and non fungible tokens. Minimalism is at its core - it lacks programmability on purpose and serves as a “home” for canonical balances of chain-less tokens like RMRK, or Parity’s company retreat attendance NFTs.

To protect against spam, Statemine uses two methods:

1. It requires a deposit for every new class, a class being a collection of NFTs, or a type of fungible token (e.g. RMRK).
2. It requires an existential deposit of KSM before an account can be “primed” in order to be able to receive any non-KSM tokens on the network.

This means that in order to receive a token on Statemine, an address first needs to have an initial balance of KSM.

With a relatively straightforward implementation of the Teleport function in the default [Polkadot JS UI](https://polkadot.js.org/apps), this is generally not a problem for individual crypto native users. However, it poses an enormous challenge for non-crypto-natives, for multi-signature and hardware-wallet-using investors, and for centralized exchanges. Let’s explore each:

1. Non crypto natives have a hard time navigating the Polkadot JS UI. For these users, the interface is overwhelming and confusing, and no dedicated wallet exists for this particular case of “feeding Statemine accounts with KSM on Kusama'' that would also be usable in other contexts. As such, the only option right now is the admittedly frightening power-user-oriented Polkadot JS UI.
2. Multi-signature accounts and hardware wallets also suffer from a lack of usability in the Dotsama system, and using them for everyday interactions is often quite difficult. n particular, multisigs are only available on Polkadot JS UI and their use often feels like a black box, especially for non-technical users as they need to wrangle terms such as multisig deposit amounts and call data vs call hashes. Ledger has been notoriously slow in implementing timely support for Kusama and Polkadot, and more recently Statemine, which is complicated further by the fact that these applications are, due to the size of the chain metadata, so large that one usually needs to uninstall all but one app on a Ledger Nano S device.
3. Arguably the biggest problem of all which trickles down into all other areas are centralized exchanges. They are used to thinking about token transfers through a different mental (and technical) model, and as such find it odd and surprising that they are unable to programmatically generate an infinite amount of valid deposit addresses for a user. Because of the existential deposit, a user is expected to prime their deposit address from Statemine itself, an operation inaccessible from Kucoin (since sending KSM there means sending it on Kusama) and so users are required to teleport KSM into an address on Statemine. To the average CEX user, this is simply an impossibility. This is admittedly a Kucoin UX problem, but it is not being made easier by the fact that (mostly) throwaway addresses (deposit addresses) need to be continuously topped up, lest their balance go too low to accept new token deposits. Gate.io has the same problem.

All told, the RMRK team has answered over 12’000 support requests from confused users about the RMRK token and its use on Statemine in the past six months. That is only the number of those we as a team replied to - those who figured it out with the help of our ambassadors and community are not counted.

## The Solution

There are two possible solutions to dramatically improve the usability of RMRK tokens.

1. Give RMRK sufficiency.
2. Move the RMRK token off of Statemine.

Despite our token already being bridged to [Karura](https://karura.network), granted sufficiency there, and made usable for paying transaction fees, where possible we would prefer to stay neutral. Thus, our preference is option 1.

### Sufficiency

Sufficiency is the concept of allowing a token on Statemine to exist and be used without accounts needing an existential deposit of KSM to accept the token.

This is achieved through a governance proposal passed through the Kusama council or public referendum, and entails “flipping a switch” on the Statemine end.

RMRK has completed the initial phases of our project, and we will soon be further expanding our scope with the launch of a metaverse and accompanying marketing efforts. Consequently, many of the issues identified will be further compounded by further growth of our project. As such, we strongly believe that it is in everyone’s best interest to make RMRK sufficient on Statemine as this, apart from making use orders of magnitude simpler, will allow us to:

- Move RMRK NFTs to Statemine, preventing Kusama node hard-drive bloat
- Allow trading of NFTs with RMRK tokens as currency
- Focus on supporting Statemine’s native NFTs as well
- Deliver the promised token utility without solely migrating to more programmable chains

Our proposal is to make RMRK sufficient through an external governance call, subject to community vote.

Call data on Statemine: 
```
0x32122000d1bc4259aeb77874ee7ca72a9763d6385763068b56bf47fcabd0d854311ab7c100d1bc4259aeb77874ee7ca72a9763d6385763068b56bf47fcabd0d854311ab7c100d1bc4259aeb77874ee7ca72a9763d6385763068b56bf47fcabd0d854311ab7c100d1bc4259aeb77874ee7ca72a9763d6385763068b56bf47fcabd0d854311ab7c1821a06000100
```

Hash on Statemine: 
```
0xe5183c1d4c58c6c5ab41b37d753eb6798d7e8f8176af5c8561f7ed8805fd7bab
```

Call data on Kusama: 
```
0x630001000100a10f0204060302286bee350232122000d1bc4259aeb77874ee7ca72a9763d6385763068b56bf47fcabd0d854311ab7c100d1bc4259aeb77874ee7ca72a9763d6385763068b56bf47fcabd0d854311ab7c100d1bc4259aeb77874ee7ca72a9763d6385763068b56bf47fcabd0d854311ab7c100d1bc4259aeb77874ee7ca72a9763d6385763068b56bf47fcabd0d854311ab7c1821a06000100
```

Hash on Kusama: 
```
0xb42f79bdb3eb16cb3d8d00bdafa4b41eee6e29813f3e098769b9ff0218c6be99
```

We would like to thank Raul Romanutti for help with this proposal!

Proposal for RMRK token sufficiency on Statemine

Swap para lease between 2003 and 2000

Statemine Runtime Upgrade to v900

Kusama Runtime Upgrade to v9190

Encointer Runtime Upgrade to Full Functionality

Update genesis state for Mangata X chain (at Mangata team Request)

Statemine Runtime Upgrade to v800

Runtime v9180 on Kusama Network

Resolve Sudo Account Issue on the Integritee Shell Parachain

In order for parachain to communicate with each other, they need to have a HRMP channel opened first.
Currently the maximum number of HRMP channel allowed on Kusama 10.

We have 27 parachains at moment and Karura is already have 6 channels and working with many more parachains on opening more channels. 10 channels is simply not enough.

There are overheads on relaychain per each established HRMP channels and therefore we needs an upper limit. However similar to number of parachains, we do not know the upper limit value and will want to gradually increase the limit and observe the performance of Kusama. This also helps to configure a safe limit for Polkadot.

This proposal aims to increase the maximum number of HRMP channels from 10 to 30. Note that number of inbound and outbound channels are separate configuration and therefore this is a batch call to update both values.

30 channels should be enough for at least next few months. We have another proposal to increase further if any parachains are approaching this limit and Kusama is still operating fine.

Increase maximum number of HRMP channels from 10 to 30

Runtime v9170 on Kusama Network

Reduce validationUpgradeCooldown to 6 hours

Statemint/e Upgrade to v700