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

test proposal to check that preimage for fix for preimage migration of 248 referenda

There are some problems with the submitted runtime code. We need to update the genesis information

Deregister this paraID and apply for a new paraID #112


justifications;

-No product
-No tokens
-Block users on Social Media
-People stay away from joining Parachains because they despise people joining Parachain
-https://twitter.com/zachxbt tweets about Omar

I demand that Picasso Network and Composable Finance be prevented from buying Parachain again.

This is a proposal to swap the slot leases of Zeitgeist parachain (2101) with parachain 2231.

The new parachain runtime seems to contain a bug that could not be spotted during onboarding in a local relay chain environment, since it worked flawlessly. However, on the live environment the collator panics during block production. The original plan was to execute the swap via XCM, however this is not possible now anymore. Once lease 25 expires, Zeitgeist parachain will downgrade if no swap is executed before.

To be able to provide continuous operation of the prediction market protocol, we kindly ask the Kusama community to execute the swap via governance.

To prove that the swap is authorized, a signature is applied by the manger of parachain 2231 (that will lose slot leases to 2101).

Message (includes timestamp): `[1668545144] I hereby authorize the swap of slot leases between parachain 2231 and 2101 on Kusama`

Manager account for 2231 (`registrar.paras(2231)`): `E8MLdGgiZxAJNUJggDYSM6j3tiLYEDRbtRmDF5fhse8xqaK`

Signature: `0x2cbb57e83bb5cc37a7d0304d467f688561ec4cf05ed2aca85722e87a340ea07ef4e6eca4c83140dd356dbcded8b52f361e0cc1e333991a5ef5cfceaf1285be8a`

Parachain Slot Swap for Zeitgeist parachain

A treasury submission for the 1st milestone development of **KAGOME** - a Polkadot Host written in C++ and developed by **Soramitsu**, is now up for vote, at request of the team. The goal of the proposal is to complete client integration on the Polkadot ecosystem and allow node operators to run KAGOME as validating nodes. More specifically, this submission aims to cover Parachain integration, Warp sync, allowing node runners to trustlessly spin up the node, Light client support, Dynamic pruning, Lean BEEFY integration, storage optimization, Multithreading and general maintenance, among others. 

Further information, including technicalities, budget, milestones and overall roadmap, can be found in the post link below. Please note that this proposal is up for vote as an external motion, given the allocation requested: if approved by the Council this will be then be up for vote by the community.

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


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

proposalHash

votingPeriod

delay

The Spanish language is becoming increasingly relevant within the Polkadot and Kusama ecosystem. The community from both Latin America and Spain has been steadily increasing and this has been reflected in an increase of the incorporation of new ambassadors, candidates and people who promote the development of ideas and initiatives for the ecosystem that is constant and growing.

The objective of this bounty is to **reward the community's content creators for their efforts in creating content in Spanish**, as well as to ensure that the content created is of quality and kept in line with the needs of the ecosystem, incorporating defined criteria for each area of assessment.

The **scope of work** of this bounty is divided into the following categories:

1.Translation of content into Spanish

1.1 Translation of written content

1.2 Dubbing

1.3 Subtitling

Creation of Spanish language content

Organization of events oriented to the Spanish-speaking community

Again, with this bounty we want **to create a mechanism for the curation of both Spanish content and events** created by the community with a focus on speed, effectiveness and control for content audits.

You can read the full proposal [here](https://docs.google.com/document/d/1LAL57c8Z11puHxk1IXAvX49gq1cguAH7SMO8GhTYx9A/edit?usp=sharing).

Original discussion post can be found [here](https://kusama.polkassembly.io/post/1895).

Spanish Content and Event Production Bounty

Hello Kusama community,

This proposal is for a retroactive grant of my two open source, free tools. One for selecting the best validators and another for gathering staking income in a spreadsheet. You can try the validator selector [here](https://james-sangalli.github.io/dot-validator-selector/) and the staking income spreadsheet generator [here](https://james-sangalli.github.io/dot-staking-income-web/).

I originally set out to create these tools because I was struggling with staking. Selecting the best validators and tracking your staking income were unsolved issues at the time and they are still causing confusion for many. Therefore, I decided to solve my own problems and the problems of others by creating simple, easy to use tools that would get the job done. 

You can read the full proposal [here](https://docs.google.com/document/d/1YT2qssdH12AtWFRloRnBanK6H1sGuE6EaX782d4qK40/edit?usp=sharing).

Thank you for taking the time to consider this proposal!



Polkadot/Kusama staking tools proposal

Hi Community,

We recently launched [Polkawatch decentralization analytics on Kusama](https://twitter.com/polkawatch/status/1578348493303083008), and [Nomination Pools](https://twitter.com/polkawatch/status/1583591038572036098) support.

The community is becoming more and more aware of the need for effective decentralization in our Ecosystem.

The interest peaked with a recent[ deplatforming event of Solana nodes](https://twitter.com/polkawatch/status/1588130270917627910) by a Network operator. 

We are been contacted by other teams of our community: Wallets, Parachains, Data Scientists, etc That want access to the data and help contribute to bringing awareness to the ecosystem. Which I think is good news.

Parachains are secured by the rely chain, but they are still vulnerable to censorship. Censorship could come from dishonest collators, deplatforming from network operators or sudden regulatory changes from hosting Countries. Despite been secured by the rely chain, parachains would benefit from decentralization analytics too.

On this proposal we aim to bring parachain support for Polkawatch, on top of continued operation of the service and other minor improvements.

The proposal has been for [discussion](https://kusama.polkassembly.io/post/1942) here.

We were invited to participate in [AAG#11](https://twitter.com/polkawatch/status/1595083537107009537) where an interesting discussion followed

Community feedback has been incorporated to the proposal.

You can access the [detailed proposal](https://docs.google.com/document/d/1ljvYDuazbNBgjf94yFUbUEdeyBN5ixG6BXAEKxuxmL4/edit?usp=sharing) here.


Treasury Proposal: Polkawatch Decentralization Analytics Parachain Support and Continued Operation.

- **Treasury Proposal:** Snowbridge Funding Proposal
- **Beneficiary:** Gbb7iGbd6Q7o1fGcT2Re4L6RXJ3U7A32itSLMjsUJzmq5LD
- **Amount:** USD 612,000.00 based on EMA7 rate by Subscan
- **Scope:** See the [full funding proposal](https://spinamp.mypinata.cloud/ipfs/QmehcCU8LjXRpj962YZYVJfHzwecvvdxbRH9BMEmiumcb9) for more details

# Overview
Snowbridge is a fully trustless, permissionless and general purpose bridge between Polkadot networks and Ethereum. The proposal covers a request for a 28 months worth of runway for all operations for the Snowbridge team, with the goal to launch as a common-good bridge on Kusama and Polkadot.

Our bridge will launch on the Bridge Hub, a common-good parachain that is being developed by Parity for Kusama and Polkadot.

The proposal includes a motivation for supporting and promoting Snowbridge, a long term roadmap, governance and economic plans as well as incentives for successful execution, launch and long term running of the project.

# Changes
The original Polkassembly post was created 4 weeks ago with extensive community discussion around the project here: [https://polkadot.polkassembly.io/post/1341](https://polkadot.polkassembly.io/post/1341)

This final proposal is the same as in the above post, though a few small changes have been made:

- Added more details about the bridge hub, with XCMv3 and Statemint XCM as an extra milestone of work on our roadmap
- Add 1 month to the launch date to account for the extra work needed for XCMv3 changes for to bridge hub
- We've extended the runway to 28 months instead of 24 month, but we're keeping the price the same and will cover the additional months with a small reduction in costs

# History
Snowfork is one of the longest running teams contributing to the Polkadot ecosystem. For over 2 years we've been working on Snowbridge, a fully trustless and permissionless bridge to Ethereum. We successfully built and completed an initial version of this bridge in September 2021, based on an Ethereum Proof of Work light client and on Parity's original BEEFY proof system funded by an initial grant from the Web3 Foundation.

# Purpose
Polkadot already has a few live Ethereum bridges across various parachains, but these all compromise on Polkadot's security and trust model. Some are secured by trusted multi-sigs, some are secured by alternative insurance collateral, but none are secured by Polkadot and none of the Ethereum or ERC20 assets that exist in the Polkadot ecosystem today are secured by Polkadot's security and trust model.

We believe that without a fully trustless bridge that is secured by Polkadot itself, the security of the wider Polkadot ecosystem is put at risk and that Snowbridge's trustless design is essential to a healthy ecosystem that can support Ethereum-based assets. Similarly, trustless support for Polkadot assets across the Ethereum ecosystem will be a valuable boon for us all.

Snowbridge is also general-purpose, supporting arbitrary message passing and cross-chain smart contract calls, so any kinds of applications can be developed on top of it beyond plain asset transfer.

Additionally, as a common good service, longer term Snowbridge will be able to provide new value for the DOT token itself and generate an additional source of income for the treasury, or an additional lockup/burn mechanism for reducing the DOT supply.

## Funding Request
This proposal is a funding request for 28 months worth of long term runway for all operations for the Snowbridge team *(16 months retroactive, 12 months in future)*, with the goal to launch as a common-good bridge on the Bridge hub on both Polkadot and Kusama.

The full proposal has been uploaded to IPFS separately, and includes extensive additional details related to further motivation for supporting and promoting Snowbridge, a long term roadmap, governance and economic plans as well as long term economic incentives for successful execution, launch and running of the project.

We request that anyone looking to meaningfully contribute to this discussion also reads through this full proposal.

This initial funding requests will be created alongside a secondary request on Kusama:

- **Requested USD on Polkadot:** USD 2,448,000.00 based on EMA7 rate by Subscan.
- **Requested USD on Kusama:** USD 612,000.00 based on EMA7 rate by Subscan.

There is an additional request for around USD 10,000,000.00 of long term economic incentives tied to key success milestones on the bridge, tied to measurable impact on the Polkadot ecosystem, although this payment will not be part of this first requested allocation.

We're planning to push out this proposal in the next month, and so are looking for early feedback and discussion from the community before going live with the proposal.

## Roadmap
1. Support XCMv3
2. Mint wrapped assets on Statemint
3. Governance and upgradability
4. Dynamic circuit breaker on withdrawals 
5. Security Audits
6. Deploy on Kusama (April 2023)
7. Deploy on Polkadot (July 2023)

See the [full funding proposal](https://spinamp.mypinata.cloud/ipfs/QmehcCU8LjXRpj962YZYVJfHzwecvvdxbRH9BMEmiumcb9) for more details.

Snowbridge Funding Proposal

Please delete

This request is for funding first setup and maintenace of stakeworld RPC services for kusama and polkadot. We are proposing it as a tip just like our [snapshot service](https://github.com/stakeworld/stakeworld-treasury/blob/master/Q3-setup-maintenance.md) which was also submitted as a tip (as adviced by the council).

The proposal can be found here: [https://github.com/stakeworld/stakeworld-treasury/blob/master/Q4-RPC-setup-maintenance.md](https://github.com/stakeworld/stakeworld-treasury/blob/master/Q4-RPC-setup-maintenance.md)

STAKEWORLD RPC nodes setup and maintenance Q4 2022

Hello Kusama community and council members,

This Tip Proposal is to make up the difference in short fall of the KSM value against the USD between the time Proposal 216 was made and when [Motion 562](https://kusama.polkassembly.io/motion/562) was passed and paid. 

In [Proposal #216](https://kusama.polkassembly.io/treasury/216), I (Josiah Kotzur) requested $30,000 USD worth of funding to go towards wages for the implementation of dropshipping into our protocol for a hoodie test. As well as a $12,000 loan to purchase the 500 hoodies, paid in KSM at the time of the transaction, to be sold to the Community “Not for Profit” as a test.

At the time of submission, KSM was ranging between $41 and $44 and when the funds were received and exchanged the value was $33,859 (excluding exchange fees). 

KSM price went down approximately 19%, in the USD value this equated to an approximate $8,140. The hoodies are a fixed price of $12,000 USD and $3,000 drop shipping allocation for 6 months. This leaves our team with $18,860 to pay a budgeted $30,000 in wages, which is a 37% reduction.

This issue was discussed with both @otar.shakarishvili:matrix.parity.io and  @raul.rtti:matrix.parity.io at the acceptance motion, but before the 995KSM was paid.

This Tip proposal is for a further 240 KSM to make up the difference for wages. 


![](https://i.postimg.cc/SxNMV8pS/photo-2022-11-04-08-22-56.jpg)


