candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

The proposal aims to resubmit [Referendum 243](https://kusama.polkassembly.io/referendum/243) (already approved), this time using OpenGov in order to extend the lease of Encointer's Common Good Chain by eight lease periods. The last proposal failed to enact due to some changes in logic and scheduler that restricted the call. Hence this proposal aims to put forward the extension request once again.

Contextual information by Encointer can be found below:

### Encointer's common good lease run out on Dec 12th 2022.

Based on the following progress reports, we ask the community to appreciate our work done so far and grant us another 48 weeks.

- [Our recent treasury proposal](https://docs.google.com/document/u/2/d/1eTyZGCTCzo7ZGonVtAmJmc5QYYI0qYHab6z8w56B_F0/edit) includes a detailed report on what we have achieved until June 2022 and what our plans are for the future.
- Our [delivery report](https://kusama.polkassembly.io/motion/510#3f6f0d94-639f-49ec-a0ee-1f4ace1a37c8) on above treasury grant updates the information with achievements in the June-Sept 2022 period

We think Encointer has achieved a lot and is gaining momentum, both with its [pioneer community in Zurich](https://leu.zuerich/), but also with [newly launching communities worldwide.](https://trello.com/b/1Yhln6NT/encointer-community-leader-applications)

Our original argumentation for the common good is still valid and can be found [here](https://kusama.polkassembly.io/post/610). What we'd like to add to our value proposition of pure sybil resistance is our approach for [inclusivity](https://polkadot.network/blog/introducing-encointer-making-web3-truly-inclusive/) which has resonated well in the community.

The initial passed referendum to register Encointer as common good is [here](https://kusama.polkassembly.io/referendum/158).

While the Encointer team is aiming to diversify its funding sources, support by the Kusama treasury will be necessary for the upcoming period to continue working at the current pace. Therefore, we will submit our next treasury proposal soon.

Preimage hash: `0x3249b18124aab52cd632f6759c7e46e10bac60b6f3411247e92b44babc67fd41`


- Encointer is a project that needs to extend its lease for the Common Good Chain.
- They have already achieved a lot and want to continue their work for another 48 weeks.
- Encointer's approach for inclusivity has been appreciated by the community.
- The last proposal failed due to some changes in logic and scheduler, so they are resubmitting it.
- Encointer is planning to diversify its funding sources, but support from the Kusama treasury is still necessary.

Executed

lease_admin

Extending Encointer's common good lease by 48 weeks

This proposal aims upgrade Kusama to [v9350](https://github.com/paritytech/polkadot/releases/tag/v0.9.35), aiming to fix the last action point in the plan to relieve validators from the slash events on 09.12.2022 - previous proposal and actions can be found [here](https://kusama.polkassembly.io/referenda/16). 

**Preimage composition:**

![](https://i.ibb.co/yVG604w/Screenshot-2022-12-14-at-08-10-43.png)

### Runtime

* [S] ✅ trivial [#12485](https://github.com/paritytech/substrate/pull/12485) Low - General message queue pallet

* [S] [#12420](https://github.com/paritytech/substrate/pull/12420) Low - Remove implicit approval chilling upon slash.


### Misc

* [S] ✅ trivial [#12837](https://github.com/paritytech/substrate/pull/12837) Low - Rename some crates for publishing to crates.io

* [S] ✅ trivial [#12795](https://github.com/paritytech/substrate/pull/12795) Low - Remove `mem_info` and references to `parity-util-mem`

* [S] ✅ trivial [#12788](https://github.com/paritytech/substrate/pull/12788) Low - Refund referendum submission deposit

* [S] ✅ trivial [#12852](https://github.com/paritytech/substrate/pull/12852) Low - Remove sandboxing host function interface

* [S] ⏳ pending non-critical audit [#12798](https://github.com/paritytech/substrate/pull/12798) Low - Move lockablecurrency trait to fungibles::lockable and deprecate lockablecurrency

* [S] ✅ trivial [#12782](https://github.com/paritytech/substrate/pull/12782) Low - [pallet-assets] add asset_exists(id: assetid) function

* [S] ✅ trivial [#12485](https://github.com/paritytech/substrate/pull/12485) Low - General message queue pallet

* [S] ✅ trivial [#12663](https://github.com/paritytech/substrate/pull/12663) Low - Rpc server with http/ws on the same socket

* [S] [#12420](https://github.com/paritytech/substrate/pull/12420) Low - Remove implicit approval chilling upon slash.


Please note this proposal is submitted to Whitelisted Caller Track: meaning two proposals will be up for vote at the same time: one for the community to approve and one for the Fellowship members to approve.

Here's a summary of the SubSquare post:

- The proposal aims to upgrade Kusama to v9350 to fix the last action point in the plan to relieve validators from the slash events on 09.12.2022.
- The post includes a preimage composition image.
- The post lists various updates and changes to the runtime and miscellaneous items, including removing implicit approval chilling upon slash and renaming some crates for publishing to crates.io.
- The proposal is submitted to the Whitelisted Caller Track, which means two proposals will be up for vote at the same time: one for the community to approve and one for the Fellowship members to approve.

whitelisted_caller

Runtime Release v9350 for Kusama

After its first year as a common good parachain, Encointer has been granted another 48 weeks on Kusama. The Encointer Association seeks for financing of its planned activities for the new common-good parachain lease period, split into two proposals. The current proposal shall cover the funding for Q1 and Q2 2023 (until the end of June 2023). 

The amount of the proposed treasury spend is CHF 610’000 = 22’089 KSM.

Our [**Detailed Proposal**](https://docs.google.com/document/d/173FnUyaemsHD9wnGMipZWnanO23yZUVhco55RxBXKBw#) encompasses all of:
1. What is Encointer?
2. What have we achieved so far?
3. What are we planning to do in 2023?
4. How we funded our past activities
5. What we spent our funds for in the past
6. What we plan to spend in 2023 (Budget)
7. Proposal terms


- Encointer is a project that helps people create their own currency and trade with it.
- Encointer has been given another 48 weeks to work on Kusama.
- They need money to keep working on their project for the first half of 2023.
- They are asking for CHF 610,000 to fund their work.
- They have a detailed proposal that explains what they have done, what they plan to do, and how they will use the money.

big_spender

[Big Spender] Encointer lease 2 Treasury Proposal

As we navigate OpenGov, we re finding new things again, a second time: referendum #1 would not have enacted succesfully, because the call we used (treasury.ApproveProposal) would have only be enacted successfully with root origin. Additionally, we have now discovered that referendum #3 will also not be enacted successfully due to a polkadot-js UI issue whereby it used the expected enactment block as the enactment duration rather than particular given time, so the proposal would take many years to enact.

This has since been fixed in the polkadot-js UI.

This is the (hopefully final) resubmission of the proposal:

- on Treasurer track (same one)
- with the call treasury.Spend (including the amount in KSM for the allocation)

Original replaced treasury submission: [HERE](https://kusama.polkassembly.io/treasury/229)
Second replaced treasury referenda: [HERE](https://kusama.polkassembly.io/referenda/3)

This proposal is now up for vote! aiming to cover the development of **Snowbridge** by the Snowfork team: a fully trustless, permissionless and general purpose bridge between Kusama/Polkadot and Ethereum. The bridge will launch on the Bridge Hub, a common-good parachain that is being developed by Parity for Kusama and Polkadot. 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 can be reviewed on [the post](https://kusama.polkassembly.io/treasury/229) 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. Please note that both networks are voting on the project: the Polkadot proposal (up for vote by the council as external motion and later by the community if approved) can be found [here](https://kusama.polkassembly.io/treasury/229).

- A previous proposal would not have worked because it needed a special permission to work.
- Another proposal also had a problem with the time it would take to be enacted, but it has been fixed.
- There is a new proposal to fund a project called Snowbridge.
- Snowbridge is a bridge between Kusama/Polkadot and Ethereum.
- The proposal is for 28 months of funding for Snowbridge to launch on the Bridge Hub.

treasurer

[Replacement for Referenda #1 and #3] Treasury Proposal: Snowbridge Funding Proposal


[Referenda #5, contains an error. The parameter "after" was misinterpreted resulting in an enactment time of 2.8 years and will be cancelled with others in the same situation, it can be found  [here](https://kusama.subsquare.io/referenda/referendum/5)] 

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.

- Polkawatch launched decentralization analytics on Kusama and Nomination Pools support.
- The community is becoming more aware of the need for effective decentralization in the ecosystem.
- Parachains are secured by the rely chain but are still vulnerable to censorship, and they would benefit from decentralization analytics too.
- The proposal aims to bring parachain support for Polkawatch and other minor improvements.
- The detailed proposal can be accessed through the provided link.

[Replacement for Referenda #5] Polkawatch Decentralization Analytics Parachain Support and Continued Operation.

Dear Community,

We are resubmitting our proposal due to issues with the UX indicating enacment 3 years from now. The previous proposal can be viewed [here](https://kusama.subsquare.io/referenda/referendum/4).

Ordum is a public good grants aggregator for the Polkadot and Kusama ecosystems. This proposal addresses the funding of R&D.

**Introduction**

There is no existing software besides Gitcoin to publish, apply for and manage grants. Gitcoin focuses on a quadratic funding model, while there is a need for an overall indexer and management software for grants in web3.

After reading the Builders Program [post](https://forum.polkadot.network/t/builders-programs/226) on the Polkadot Forum and speaking with other members of the community (including councillors, Web3 Foundation, and members of Shokunin Network), it was evident that a grants aggregator is imperative for bringing projects into the ecosystem as well as scaling it.

In order to construct a rich and independent environment of public goods and DAOs, it is fundamental for teams to easily find and acquaint themselves with treasuries and foundations.

**Problem**

Treasuries / foundations(eg. Polkadot Treasury) are burning funds as there are not enough projects to support. 

Grants information and guidelines within the ecosystems are scattered and therefore difficult to find (there are only 2 places where we have a somewhat overview of these; Polkadot/Kusama documentation and Web3 Foundation Github). 

It is difficult to publicly track (grant) funding for different stages of project development. This has previously resulted in conflicts within the community.

There isn’t a unified public record to privately / publicly manage and display a grant recipient’s quality and outcome of delivery (scattered documentation). 

With GOV2 incoming, further research is required on tracking proposals and deliverables in order to determine the appropriate UX. 

**Solution**

Success for Ordum is the deliverance of all milestones and a V1 POC of a public goods grant aggregator.

**A dapp which contains all grants from the ecosystems.**

- Index data from treasuries in the ecosystem by building custom APIs(Subsquids) for tracking proposals 
- Integrate Github in the front end for tracking and submitting non-treasury grants 
- Building and maintaining light clients for quick data retrivals, security and low loading times 
- Enable log in with multiple DID services, Github and Wallets 

**Minting of non-transferable NFTs as “certificates” for completed milestones. Each token would contain information on what was executed and how it was evaluated.**

- Ordum will be built on Phala to leverege the chains privacy capabilities and Phat smart contracts 
- Create a connection between DID (foundation)–> Phala Smart Contract–> Non-transferable NFT–>DID (recipient) 
- Design a custom type of RMRK non-transferable NFT, stored on Crust, containing reports from the foundations on milestone delivery 

**Delivery of milestones, grant applications and funding are displayed on a team’s profile for transparency**.

- Front end displaying funding amounts and certificates within a roadmap

**Issuing surveys and analyzing / feedback data for the purpose of aggregating and managing treasury grants in the most optimal way.**

- Design the optimal UX through collaboration with other teams in the ecosystem

Requested funding 78,804 USD // 2770 KSM
Kusama rate EMA7 as per 12th of December 2022, 11.00 (and reimburstment of submission and decision deposit)

The full proposal can be viewed [here](https://hackmd.io/@XyloDrone/Ordum)

We look forward to hearing your feedback.


- Ordum is a software that helps manage grants for Polkadot and Kusama ecosystems.
- There are not enough projects to support treasuries/foundations, and grants information is scattered.
- Ordum will create an index of all grants, integrate Github, and maintain light clients for quick data retrieval.
- Completed milestones will be represented by non-transferable NFTs containing information on what was executed and how it was evaluated.
- Teams' profiles will display delivery of milestones, grant applications, and funding for transparency.

[Resubmission proposal 4] Treasury Proposal: Ordum | Public Good Grants Aggregator for Polkadot and Kusama

The InvArch Network team seeks to provide the ecosystem with a new multi-signature solution, named Saturn, **available to every parachain & implementable throughout any dApp on those parachains**. This multi-signature solution will be made so that it can be **easily adopted by existing wallets in the ecosystem** & be immediately implemented to provide a superior multi-signature solution to the Dotsama ecosystem **compared to external solutions such as Gnosis Safe**.

Multi-party ownership solutions are the core of nearly every project being developed by the InvArch Network team, which has heavily influenced the design of the network’s infrastructure. While sharing our proposed multi-signature implementation with other builders & community members throughout the ecosystem, we have received tremendous interest & support. We also had a meeting with a member (Ricardo) from Parity Technologies in the past regarding our solution and received positive feedback on its capabilities.

The current multi-signature implementations available for builders in the ecosystem either rely on the current implementation used in the original multi-sig Pallet developed by Parity (which is limiting) or by developing their own custom solutions (which is time-consuming & costly). The ecosystem also lacks account-recovery capabilities & the ability to onboard & off-board new members of a multi-signature implementation. This is a very restricting problem, with concerns being shared across the Kusama community. We would like to change this current reality.

What we are proposing to build for the ecosystem is designed to service the entirety of Kusama & its parachains. We are providing it in a way that individuals will never need to purchase TNKR (optional, though) & can use KSM. **This is an open-source solution for Kusama and a solution that we truly believe will be a big boost for the ecosystem.** We are confident that if trusted by the community to deliver this solution, Kusama will go from having one of the worst multi-sig experiences in Web3 to one of the best, if not the best. Public interest in the potential for our multi-sig has been shared by the community in the past, and we would be extremely grateful if the community will signal their support for us to build this for Kusama.

- A full overview of the proposal & cost breakdown can be found [here](https://docs.google.com/document/d/e/2PACX-1vQLhnD3l0K5fYQN9_ECiHUeQZT_lTN4FvWkkPKIWy8mVGvhvKwmjwrMIlwHCVlitA0ovWyF2Qvaplfu/pub)

- A link to the public discussion previously posted regarding this proposal can be found [here](https://kusama.polkassembly.io/post/2031).

SubSquare is a team that wants to create a new multi-signature solution called Saturn for the Kusama ecosystem. This solution will be better than other solutions like Gnosis Safe and can be used by anyone without having to buy TNKR. The team has received positive feedback from the community and Parity Technologies. They want to solve the problem of limited multi-signature implementations and lack of account-recovery capabilities in the ecosystem. The solution will be open-source and available for every parachain and dApp. The team has shared a proposal and cost breakdown for the project.

InvArch Tinkernet - Funding for a Multi-Signature Solution

# Encointer V12 + Statemine 9330 Upgrade via Gov2

## Contextual Information

This proposal batches all upgrades for Kusama's system parachains: Statemine and Encointer.

Details of Encointer's upgrade can be found in [this post](https://kusama.polkassembly.io/post/2017), including release notes and feature additions of the V12 release.

Release notes for Statemine are in the [Cumulus v9330 release](https://github.com/paritytech/cumulus/releases/tag/parachains-v9330). This primarily adds a new Assets API for asset class destruction. The new methods can handle cleaning up state over multiple calls, which would be relevant when an asset class has too many accounts/approvals to remove in one block due to PoV limits.

## Proposal Call Data

Call on Statemine: [StatemineAuthorizeUpgrade](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fstatemine-rpc.polkadot.io#/extrinsics/decode/0x0102957f0c9b47bc84d11116aef273e61565cf893801e7db0223aeea112e53922a4a)

- Data: `0x0102957f0c9b47bc84d11116aef273e61565cf893801e7db0223aeea112e53922a4a`

Call on Encointer: [EncointerAuthorizeUpgrade](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama.api.encointer.org#/extrinsics/decode/0x0102ccdfc804e0482f951ef7ad15fda0d38ead81c42e93a8276e60a45c663b8a3b91)

- Data: `0x0102ccdfc804e0482f951ef7ad15fda0d38ead81c42e93a8276e60a45c663b8a3b91`

Call on Relay Chain: [Batch XCM Send](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x180408630001000100a10f0204060202286bee880102957f0c9b47bc84d11116aef273e61565cf893801e7db0223aeea112e53922a4a630001000100a50f0204060202286bee880102ccdfc804e0482f951ef7ad15fda0d38ead81c42e93a8276e60a45c663b8a3b91)

- Call Hash: `0x461c26edbf3148234fef402415fd55aa80add45abc3982578218d0b2f690141c`

The calls below are the ones that are required to pass this proposal on the Whitelist track using OpenGov.

## Whitelist the Call

Whitelist Call: [WhitelistCall](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x2c00461c26edbf3148234fef402415fd55aa80add45abc3982578218d0b2f690141c)

- Hash: `0x34fd5fdf54f9cfcfe8038d1aed183df0f84791878e29f0572d7c3b7d6d08f181`
- Len: 34

Fellowship Referendum:

![](https://i.imgur.com/UfSDoGW.png)

## Dispatch the Call

Dispatch: [WhitelistedCallWithPreimage](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x2c03180408630001000100a10f0204060202286bee880102957f0c9b47bc84d11116aef273e61565cf893801e7db0223aeea112e53922a4a630001000100a50f0204060202286bee880102ccdfc804e0482f951ef7ad15fda0d38ead81c42e93a8276e60a45c663b8a3b91)

- Hash: `0xc77ff5a4dd42ef33bad99104b6580c6cda9ff9c32086840d8492ed751d744893`
- Len: 107

Public Referendum:

![](https://i.imgur.com/vYfJ3NJ.png)


Encointer V12 and Statemine 9330 upgrades are being proposed for Kusama's system parachains. 

Encointer's V12 release includes new features and release notes can be found in the provided link. 

Statemine's upgrade includes a new Assets API for asset class destruction, which can handle cleaning up state over multiple calls. 

There are three calls required to pass this proposal on the Whitelist track using OpenGov. 

The Fellowship Referendum and Public Referendum are shown in the provided images.

[Whitelisted Caller] Referendum #17: Upgrade Statemine and Encointer Parachains

staking_admin

referendum_canceller

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. This proposal replaces referendum 254 on Gov1: approved by the community but not successfully enacted due to some changes, gov1 got changed to use some of the OpenGov logic: and this failed on dispatch. The original contextual information, below:

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

- The proposal is about upgrading Kusama's runtime to v9340.
- The upgrade will include some changes to Gov1, which failed to work properly before.
- The proposal has some technical details, including different types of audits and code changes.
- The proposal is submitted with a set_storage call, not a set_code call.
- After the Council vote, the community will need to vote on the proposal in the referenda queue.

Runtime v9340 Upgrade On Kusama: Fixing OpenGov Parameters and more! (Replacing referendum 254 on Gov1, which failed to execute)

Cancelled

REJECT - FAILED SUBMISSION

Encointer has a new code upgrade which
* allows participants to unregister from ceremony cycles. This will help us decrease noshows and increase security by doing so
* allows reputables to endorse newbies. This is a massive improvement for growth. Before, only bootstrappers could endorse a one-off amount of newbies. Now, everybody that has recently proven their personhood can endorse a small number (~2-5, TBD) of newbies with every cycle. This is very much in line with the "word of mouth" growth strategy 
* upgrades our dependencies to polkadot-0.9.28

Detailed changes to our [runtime](https://github.com/encointer/encointer-parachain/compare/1.2.0...1.3.2) and to our [pallets](https://github.com/encointer/pallets/compare/1.2.0...1.3.2)


[runtime release v12 in our GH repository](https://github.com/encointer/encointer-parachain/releases/tag/1.3.2)

# OpenGov Theory

We would like our runtime upgrade to be whitelisted by the fellowship. As a common good parachain we can't upgrade ourselves and the runtime upgrade needs a knowledgeable review which the fellowship is able to provide. It would be possible to submit to the root track directly, but that is expected to take too long to be practical (~28d) because of very restricitive support thresholds.

The gov2 process in pseudocode for sending a whitelisted XCM with Superuser origin is as follows:

```
// The actual proposal to enact. (no need to note this as a preimage)
let proposal = xcmPallet.send(...);

// Whitelist the `proposal` for dispatch from `WhitelistedCaller`.
let whitelistProposal = whitelist.whitelistCall(hash: hash(proposal));
let preimageWL = preimage.notePreimage(whitelistProposal);

// Whitelists the `proposal` from the Fellowship. 
// This has to be submitted by any member of felllowship (No matter the rank)
let fellowshipReferendum = fellowshipReferenda.submit(
  proposalOrigin: Origins.Fellowship3Dan,
  proposal: Lookup {
    hash: preimageWL.hash, 
    len: preimageWL.len
  },
  ...
);

// Now the fellowship has to vote.....

// The following public referendum can already start. However, the proposal must be whitelisted before the public referendum is enacted

// Dispatch the `proposal` from `WhitelistedCaller`.
let dispatchProposal = dispatchWhitelistedCallWithPreimage(
  call: proposal,
);
let preimageD = preimage.notePreimage(dispatchProposal)

// Dispatches the proposal as long as it has been whitelisted before enacted.
let publicReferendum = referenda.submit(
  proposalOrigin: Origins.WhitelistedCaller,
  proposal: Lookup {
    hash: preimageD.hash,
    len: preimageD.len
  },
  ...
);
```

# Practise

## The call to be executed on the Encointer parachain with root privilege

[authorizeUpgrade call on Encointer](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama.api.encointer.org#/extrinsics/decode/0x0102ccdfc804e0482f951ef7ad15fda0d38ead81c42e93a8276e60a45c663b8a3b91
)

## the proposal

[proposal call xcmPallet.send to be executed on Kusama](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama.api.onfinality.io%2Fpublic-ws#/extrinsics/decode/0x630001000100a50f0204060202286bee880102ccdfc804e0482f951ef7ad15fda0d38ead81c42e93a8276e60a45c663b8a3b91
) yields hash `0x7776194086d1496a812cb61670080157d2f511cbcbaafddd44ff248a753788e7`

## whitelisting by fellowship

[whitelistProposal](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama.api.onfinality.io%2Fpublic-ws#/extrinsics/decode/0x2c007776194086d1496a812cb61670080157d2f511cbcbaafddd44ff248a753788e7) encodes to `0x2c007776194086d1496a812cb61670080157d2f511cbcbaafddd44ff248a753788e7`

[note preimageWL](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama.api.onfinality.io%2Fpublic-ws#/extrinsics/decode/0x2000882c007776194086d1496a812cb61670080157d2f511cbcbaafddd44ff248a753788e7)

preimageWL hash =  `0xb98f987a58c1cda0cb8b8fd07d441e2e5b67a809742e6eb3bd2ec5f2976cb29c` len = 34
has been noted 

Now, propose to fellowship 

[submit fellowship referendum](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama.api.onfinality.io%2Fpublic-ws#/extrinsics/decode/0x17002b1402b98f987a58c1cda0cb8b8fd07d441e2e5b67a809742e6eb3bd2ec5f2976cb29c2200000001f9c9ed00) (must be submitted by member of fellowship. decision deposit is 0.333 KSM)

The decision period for the fellowship whitelist referendum [is 7 days](https://github.com/paritytech/polkadot/blob/bc65cf22a359859c20bc4aae94bcffad1846d5b6/runtime/kusama/src/governance/fellowship.rs#L112-L130)

## public referendum

propose to dispatch the whitelisted call

[dispatchProposal](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama.api.onfinality.io%2Fpublic-ws#/extrinsics/decode/0x2c03630001000100a50f0204060202286bee880102ccdfc804e0482f951ef7ad15fda0d38ead81c42e93a8276e60a45c663b8a3b91) encodes to `0x2c03630001000100a50f0204060202286bee880102ccdfc804e0482f951ef7ad15fda0d38ead81c42e93a8276e60a45c663b8a3b91`

[note preimageD](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama.api.onfinality.io%2Fpublic-ws#/extrinsics/decode/0x2000d42c03630001000100a50f0204060202286bee880102ccdfc804e0482f951ef7ad15fda0d38ead81c42e93a8276e60a45c663b8a3b91)

hash = `0xd394967583efb9b8fe1dd4ad84d3bcb7c5382cae19319b2cfc1682e227ce76d3` len = 53

[publicReferendum submission](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama.api.onfinality.io%2Fpublic-ws#/extrinsics/decode/0x15002b0d02d394967583efb9b8fe1dd4ad84d3bcb7c5382cae19319b2cfc1682e227ce76d33500000001c4caed00) (may be submitted by proposer. Must have submission deposit of 100KSM)

Then, the decision deposit of 33.333 k KSM :lol: must be provided (can be a different party providing it)




Encointer has made some upgrades to their code which will help improve their platform. Here are the changes:
- Participants can now unregister from ceremony cycles to decrease no-shows and increase security.
- Reputables can now endorse newbies, which will help with growth. Previously, only bootstrappers could endorse newbies.
- The dependencies have been upgraded to polkadot-0.9.28.
- Encointer has requested a runtime upgrade to be whitelisted by the fellowship.
- There are some steps that need to be followed to execute the call to be executed on the Encointer parachain with root privilege.

TimedOut

Encointer runtime upgrade v12

Dear fellow Kusama community,

We come to you with a humble but urgent request and need your help. 

### TL;DR:

- The Kintsugi parachain stopped producing blocks at block 1,983,993 [2022-12-01 09:32:18 (+UTC)] due to a Kintsugi-specific issue with the slot duration in Aura
- A fix has been found, tested, and reviewed with the help of Parity
- No user funds are affected as of this writing
- The only way to recover the Kintsugi chain is to update the runtime on the relay-chain via Kusama governance and upgrading all Kintsugi collators


**We are asking the Kusama community to vote on recovering the Kintsugi parachain as soon as possible.**

This is a technical emergency and we are hence requesting the whitelist track for this proposal, to accelerate recovery of Kintsugi.

# Summary

The Kintsugi parachain has stopped producing blocks after a runtime upgrade. The issue is with the slot duration migration and is specific to the Kintsugi chain configuration. No other parachains are affected. See detailed description below. 

The only way to recover the chain is via a Kusama governance proposal.  

No user funds are affected as of this writing. 

**Current status of the network: **All operations are halted. New kBTC cannot be issued and kBTC cannot be redeemed. KINT, kBTC, KSM, LKSM, and any other currency on Kintsugi cannot be moved. There are no KINT rewards for either stakers or vaults. Collateral backing BTC is still locked but collateral thresholds are not enforced at the moment.

Vaults are overall very healthy (https://kintsugi.interlay.io/dashboard/vaults) and no liquidations are expected at this time. There were no pending issues or redeem requests at the time of halting. 

Until Kintsugi is back online and producing blocks:
- All exchanges have been advised to halt withdrawals 
- All XCM-connected parachains have been advised to halt XCM channels 

# Technical Details of the Issue 

## Problem

The issue was caused by a problem with the slot duration. Specifically, there is a panic when a collator tries to produce a block:

```
[Parachain] panicked at 'Timestamp slot must match `CurrentSlot`'
```

Initially, Kintsugi was set at genesis to have a slot duration of 6 seconds but parachains typically have 12 second block times. The other chains built from the interBTC code-base (Interlay, and Interlay and Kintsugi testnets) used 12 seconds. A temporary fix was included in the Kintsugi collators to ensure that block production would succeed even with the 6 second blocktimes. The Kintsugi team did not run a migration as suggested by Parity so the temporary fix remained in place. The missing migration did not cause issues for several runtime upgrades.

However, with the 1.20.0 runtime upgrade we included a recommended change to prevent malicious block producers from potentially building a block. Due to the missing migration, a check in the Aura hook panicked due to an incorrect slot duration calculation which prevented Kintsugi from producing blocks.

Collators are not able to produce new blocks as the relay-chain validation would reject any new blocks with the updated runtime. Unfortunately, this issue was not caught during the release process, code reviews, and testnet upgrades. Also, this issue would not have been caught by the `try_runtime` testing approach as this issue is specific to collator producing blocks and the runtime migrations as such were not an issue. The issue is specific to the Kintsugi configuration and was hence not caught by the testing process on testnet. We are not aware of any other parachains being affected by this. 

A detailed post-mortem will be provided shortly and linked to this proposal. 

## Solution

There are two parts to solve this issue:

1. Updating the Kintsugi runtime on Kusama: Collators are unable to produce blocks. Even by using `codeSubstitutes` Kintsugi cannot recover alone due to the bug described above. Hence, a new wasm needs to be set via Kusama governance on the relay-chain.
2. Updating all collators on Kintsugi to use the patched wasm: Updating the Kintsugi runtime on Kusama needs to be executed together with providing all collators in the Kintsugi network a patched wasm to be used via the `codeSubstitutes` approach.

# Preimage:

- Para: 2092
- newCode: https://github.com/interlay/interbtc/releases/download/1.20.0-hotfix/kintsugi_runtime_parachain.compact.compressed.wasm
and

# References

- https://substrate.stackexchange.com/questions/5828/what-is-codesubstitutes-in-the-chain-spec
- https://github.com/paritytech/cumulus/pull/1876

Kintsugi parachain has stopped producing blocks due to a technical issue with the slot duration in Aura. No user funds are affected as of now. The only way to recover the Kintsugi chain is to update the runtime on the relay-chain via Kusama governance and upgrading all Kintsugi collators. The Kusama community is being asked to vote on recovering the Kintsugi parachain as soon as possible. All operations are halted until Kintsugi is back online and producing blocks.

Emergency Proposal: Recover Kintsugi Parachain

As we navigate OpenGov, we re finding new things: it seems referendum #1 wont enact succesfully, because the call we used (treasury.ApproveProposal) will only be enacted successfully with root origin.

This is the resubmission of the proposal:

- on Treasurer track (same one)
- with the call treasury.Spend (including the amount in KSM for the allocation)

Original treasury submission: [HERE](https://kusama.polkassembly.io/treasury/229)

This proposal is now up for vote! aiming to cover the development of **Snowbridge** by the Snowfork team: a fully trustless, permissionless and general purpose bridge between Kusama/Polkadot and Ethereum. The bridge will launch on the Bridge Hub, a common-good parachain that is being developed by Parity for Kusama and Polkadot. 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 can be reviewed on [the post](https://kusama.polkassembly.io/treasury/229) 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. Please note that both networks are voting on the project: the Polkadot proposal (up for vote by the council as external motion and later by the community if approved) can be found [here](https://kusama.polkassembly.io/treasury/229).


- A proposal for funding the development of Snowbridge by the Snowfork team is up for vote.
- Snowbridge is a bridge between Kusama/Polkadot and Ethereum that is fully trustless, permissionless and general purpose.
- The proposal is for 28 months worth of funding for the Snowbridge team, with the goal to launch as a common-good bridge on the Bridge hub on both Polkadot and Kusama.
- The full proposal includes details related to motivation, roadmap, governance, economic plans, and incentives for successful execution.
- Both networks are voting on the project: the Polkadot proposal can be found on the Polkadot website.

#3 [Replacement for Referenda #1] Treasury Proposal: Snowbridge Funding Proposal

As we navigate OpenGov, we re finding new things: it seems this referendum #2 wont enact succesfully, because the call we used (treasury.ApproveProposal) will only be enacted successfully with root origin, which is the case.

We will need to resubmit this proposal:

    on Treasurer track (same one)
    with the call treasury.Spend (including the amount in KSM for the allocation)

The proposal has now been [resubmitted here](https://kusama.subsquare.io/referenda/referendum/5). 

----

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.


- A proposal for a referendum did not work because it needed a different type of approval.
- The proposal was resubmitted with a different type of approval needed.
- Polkawatch launched decentralization analytics on Kusama and now supports Nomination Pools.
- The community is interested in effective decentralization in the ecosystem.
- A proposal aims to bring parachain support for Polkawatch and other minor improvements.

Rejected

Polkawatch Decentralization Analytics Parachain Support and Continued Operation. [this proposal will not enact successfully if approved: more info below]

Original treasury submission: [HERE](https://kusama.subsquare.io/treasury/proposal/229)

This proposal is now up for vote! aiming to cover the development of **Snowbridge** by the Snowfork team: a fully trustless, permissionless and general purpose bridge between Kusama/Polkadot and Ethereum. The bridge will launch on the Bridge Hub, a common-good parachain that is being developed by Parity for Kusama and Polkadot. 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 can be reviewed on [the post](https://kusama.polkassembly.io/treasury/229) 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. Please note that both networks are voting on the project: the Polkadot proposal (up for vote by the council as external motion and later by the community if approved) can be found [here](https://kusama.polkassembly.io/treasury/229). 

Hash: `0xfae1763e293099ff7858ddf848255fb05efb10b973f49886b5b213b2981fb111`



- The Snowfork team wants to create a bridge between Kusama/Polkadot and Ethereum.
- They need money to work on this project for 28 months (16 months already passed and 12 months in the future).
- The bridge will be launched on the Bridge Hub, which is being developed by Parity for Kusama and Polkadot.
- Both networks are voting on the project.
- The full proposal has more details about the project's plans and goals.

OpenGov Referenda