The proposal aims to upgrade Polkadot’s runtime to [v9300](https://github.com/paritytech/polkadot/releases/tag/v0.9.30). More information about the release can be found on the link in this post. As the external queue can only hold one proposal at a time, yesterday's [motion 286](https://polkadot.polkassembly.io/motion/286), removing the limits on members in nomination pools, deleted previously approved [motion 285](https://polkadot.polkassembly.io/motion/285) aiming to upgrade Polkadot's runtime. This new proposal replaces motion 285.

**Runtime**

* [S] ✅ audited [#12170](https://github.com/paritytech/substrate/pull/12170) Low - Pallet-identity: be more paranoid ;)
* [S] ⏳ pending non-critical audit [#12222](https://github.com/paritytech/substrate/pull/12222) Low - Add constfeemultiplier to the transaction payment pallet
* [S] ⏳ pending non-critical audit [#11981](https://github.com/paritytech/substrate/pull/11981) Low - Breaking: rename call & event
* [S] ✅ trivial [#11738](https://github.com/paritytech/substrate/pull/11738) Low - Add inspect trait for asset roles
* [S] ⏳ pending non-critical audit [#11806](https://github.com/paritytech/substrate/pull/11806) Low - Improve base weights consistency and make sure they're never zero
* [S] ✅ trivial [#12205](https://github.com/paritytech/substrate/pull/12205) Low - Add special tag to exclude runtime storage items from benchmarking
* [S] ⏳ pending non-critical audit [#12034](https://github.com/paritytech/substrate/pull/12034) Low - [feature] part 1: add targetlist for validator ranking
* [S] ✅ trivial [#12186](https://github.com/paritytech/substrate/pull/12186) Low - Contracts: use weakboundedvec for instrumented code
* [P] [#5535](https://github.com/paritytech/polkadot/pull/5535) Low - Runtime/disputes: slashing
* [S] ✅ trivial [#12258](https://github.com/paritytech/substrate/pull/12258) Low - Breaking: rename origin
* [S] [#12230](https://github.com/paritytech/substrate/pull/12230) Low - Bound staking storage items
* [S] ✅ trivial [#12083](https://github.com/paritytech/substrate/pull/12083) Low - Make automatic storage deposits resistant against changing deposit prices
* [S] ✅ trivial [#12283](https://github.com/paritytech/substrate/pull/12283) Low - Rename anonymous to pure proxy
* [P] ✅ trivial [#6037](https://github.com/paritytech/polkadot/pull/6037) Low - Increase blockhashcount parameter
* [S] ⏳ pending non-critical audit [#12329](https://github.com/paritytech/substrate/pull/12329) Low - Add base-weight to system::extrinsic* events
* [P] ✅ trivial [#6032](https://github.com/paritytech/polkadot/pull/6032) Low - Paras: unblock offboarding when pvf-check concludes
* [S] ⏳ pending non-critical audit [#12366](https://github.com/paritytech/substrate/pull/12366) Low - [feature] add deposit to fast-unstake
* [P] [#6050](https://github.com/paritytech/polkadot/pull/6050) Low - Add fast-unstsake pallet to all runtimes
* [S] ⏳ pending non-critical audit [#12277](https://github.com/paritytech/substrate/pull/12277) Low - Add storage size component to weights

Proposal hash: `0xf1eeaa09f9a85633cf7f1fa588bf3247a58acf9f4cb3e8e12350833c595bc7d3`

You can review the hash and changes in the release notes and use SRTool to verify proposal hash - make sure to vote at your convenience! This proposal is submitted as an **external motion**: meaning after Council vote, the community will need to vote on the proposal in referenda queue. 

 Reject a proposed spend. The original deposit will be slashed.

 May only be called from `T::RejectOrigin`.

 # <weight>
 - Complexity: O(1)
 - DbReads: `Proposals`, `rejected proposer account`
 - DbWrites: `Proposals`, `rejected proposer account`
 # </weight>

Problem Statement & Audience:
- Lack of awareness and adoption of privacy and zero knowledge proofs (zkp) in the Polkadot ecosystem.
- Intended audience: Polkadot community and blockchain enthusiasts.

Significance:
- Privacy is a barrier to wider adoption of blockchain technology.
- Hosting an event raises awareness and encourages discussion on privacy in Polkadot.
- Provides a platform for networking and idea sharing.

Proposed Solution:
- Funding a virtual event to raise the profile of privacy and zkp in the Polkadot ecosystem.
- Using €8000 in DOT from the treasury to support the event.

Expected Outcomes:
- Increased awareness and understanding of privacy and zkp in the Polkadot community.
- Encouragement of discussion and networking among participants.
- Promotion of more extensive adoption of privacy and zkp technology in the blockchain space.

#287 Runtime v9300 Upgrade On Polkadot