candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Rejected

whitelisted_caller

Duplicate of #354 - please ignore

- We lost 50 KSM while trying to move it between accounts.  
- We used the wrong code, so the KSM disappeared.  
- The KSM didn’t go to any account—it’s lost in the system.  
- We made a mistake by not double-checking the code.  
- Developers are working to fix this problem in the future.  
- The 50 KSM was meant to bid for a special job (system-collator).  
- We didn’t win the bid, and now the KSM is gone.  
- We hope to recover the lost KSM.

Executed

small_spender

We lost 50 KSM in a blockhole during a teleport call. We were trying to teleport 50 KSM from our account on Bridgehub-Kusama to Kusama.

We first tried with small amounts after we had found the right working call and then we thought copied the call-data to initiate the actual transfer, but it was an old copy that lead to the error of `unroutable`, which is a fatal error and the tokens get lost apparently in the system. We don't know where they get lost. You can see it in the [events](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fsys.ibp.network%2Fbridgehub-kusama#/explorer/query/0xbe5d33b166c6e839eba295c04c646c512bd715622ad8faf2287f1ea9d9f098ee) that the tokens don't get deposited anywhere. This is new information to us.

This is the call-data I have used: `0x1f0903000109030300010100666963fc8192623504df2da473a1db2c69e1660463e2fd5071bcc68a96c3970d0304000100000b00203d88792d0000000000`

This would have been the correct call-data: `0x1f090301000300010100666963fc8192623504df2da473a1db2c69e1660463e2fd5071bcc68a96c3970d0304000100000b00203d88792d0000000000`

Our request is to recover the 50 KSM from openGov to the account that made call.

-   The call was our mistake, we should have double checked.
-   There is work in progress by the core developers to make sure these errors are claimable in the future, but it's not in production yet.
-   The 50 KSM was on that account was to bid for a system-collator slot for bridgehub, which we didn't win. The teleport was one way until runtime upgrade `1,001,000`

WHO: OpenGov
WHAT: Recover 50 KSM lost in a blockhole during a teleport call due to user error.
PRICE/TIMEFRAME/RESOURCES: Not specified.

Recover KSM from a erroneous teleport/XCM call 

TimedOut

referendum_canceller

This is a ReferendumV2 post. It can only be edited by the proposer of the post .

WHO: Kusama and Polkadot communities
WHAT: Initializing the Kusama side of the Polkadot<>Kusama bridge by calling `forceXcmVersion` and `bridgePolkadotGrandpa::initialize()`
PRICE/TIMEFRAME/RESOURCES: Not specified.

Initialize Polkadot GRANDPA light-client running on Kusama BridgeHub

**Proposal Summary**

- **Proponent**: Fy6erZmPp78ZY2cN945FU9KnKdATmxvG2eB9a1kh2VX33xz
- **Date**: March 1, 2024
- **Requested KSM**: $250,000 (5102 KSM)
- **Objective**: Improve security of bridges between chains.
- **Risks**: Bridges are targets for malicious activities, leading to financial losses.
- **Solution**: Implement a Security Bug Bounty Program.
- **Community Involvement**: Engage bug bounty hunters to find vulnerabilities.
- **Details**: Full proposal includes threat model and context details.
- **Impact**: Protect both source and destination blockchains.

big_spender

**WHO**: Fy6erZmPp78ZY2cN945FU9KnKdATmxvG2eB9a1kh2VX33xz

**WHAT**: Implement a Security Bug Bounty Program for bridges in Polkadot and Kusama to ensure utmost security and community involvement.

**PRICE/TIMEFRAME/RESOURCES**: $250,000 (5102 KSM) requested on 01.03.2024. Full details in attached proposal.

POLKADOT <> KUSAMA BRIDGE SECURITY BOUNTY

- The Polkadot OpenGov Observer is a Twitter tool for real-time updates on Polkadot OpenGov activities.  
- It helps people understand and participate in Polkadot voting.  
- The funding request was reduced from 200 KSM to 75 KSM based on community feedback.  
- The project aims to increase voter participation from 13.1% to 40%.  
- It uses tools like Subscan API, Twitter API, and Node.js.  
- The project is open-source on GitHub.  
- Future plans include expanding OpenGov awareness and engagement.  
- Created by Ashutosh Singh to grow the Polkadot community.

Dear Community,

This proposal includes a decrease in the funding amount for Referendum 346. Initially set at 200 KSM, it has been reduced to 75 KSM based on suggestions from many voters in a previous referendum.

This reduction in funding will not lead to any cost-cutting measures or a decline in bot quality.

I am thrilled to present the "Polkadot OpenGov Observer" project, We are seeking funding of 75 KSM ($3,695) to support the growth and development of this initiative.

**Project Overview:**

The [Polkadot OpenGov Observer](https://twitter.com/OpengovWatcher) is a tool designed to showcase real-time OpenGov activities on Twitter, providing a comprehensive monthly overview of Polkadot OpenGov Treasury and voters' charts. The primary objective is to enhance community engagement, encourage participation in OpenGov voting, and foster a better understanding of the Polkadot ecosystem.

**Beneficiary Information:**

-   Beneficiary: Polkadot OpenGov Observer Multisig
-   ![](https://i.ibb.co/98hxJBf/Screenshot-2024-02-16-at-12-03-08-PM.png)
-   Address:
    
    DZL1jjADYBhsRY9oJp8ETYtHV64Z4iz97Rvtj8pv2VP1nEN
    

**Requested Amount:**

-   75 KSM ($3,695)

**Purpose:**

Funding

**Networks**

Kusama & Polkadot

**Mission and Impact:**

Our mission is to expand the adoption of Polkadot OpenGov across different communities. By leveraging social platforms like Twitter, where 90% of the web3 ecosystem is active, we aim to make concepts surrounding OpenGov more accessible and engaging.

Currently, only 13.1% of DOT holders participate in governance. We believe that increasing this percentage to 40% will lead to more informed and fair decisions within the Polkadot OpenGov system. Our strategy involves showcasing the activities of voters on Polkadot through the OpenGov Observer, making it a valuable tool for evaluating and choosing the best delegates.

![](https://i.ibb.co/VJg97Nw/Screenshot-2024-02-14-at-1-16-10-PM.png)

![](https://i.ibb.co/TPh3nKn/Screenshot-2024-02-14-at-1-15-36-PM.png)

**Open Source GitHub Repository**

[Polkadot OpenGov Observer](https://github.com/AshutoshSingh00001/Polkadot-OpenGov-Observer) Github repo

**List of Tools and Api's used for Twitter Bot**

_Subscan Api_

_polkassembly Api_

_Node js_

_Twitter Api_

_Express_

_Polkadot Js Api_

_Coin Gecko Api_

**Current Stats:**

-   Active Voters: 1,868,686.843
-   Referenda Participation: 13.10%

**Future Impacts and Plans:**

The project is focused on making OpenGov widely used and accessible to everyone. Our implemented features include OpenGov Activity Monitoring, displaying new vote activities in real-time, and providing a monthly overview of OpenGov, voters, and the treasury. This will be instrumental in attracting those interested in OpenGov, whether they are new to the concept or seeking funding for their web3 projects. We aim to build a vibrant and active community of developers within the web3 space.

As we move forward, we will continue to refine and expand our project, ensuring that Polkadot OpenGov becomes a central hub for decentralized decision-making and community involvement.

Thank you for considering our proposal, and we look forward to contributing to the growth and success of the Polkadot ecosystem.

Best regards, Ashutosh Singh (Project Creator and Head, Polkadot OpenGov Observer)

Polkadot OpenGov Voting Observer Twitter Bot

general_admin

One step towards: sybil-resilient faucets (on Encointer) for any fungible token (on Asset Hub) <a href="https://github.com/encointer/pallets/issues/311">Context and tracking issue</a> Moreover, this HRMP channel will be an onramp to the wider ecosystem for people who get their ED++ on Encointer and move funds to Asset Hub and other parachains from there

HRMP channel between Encointer and Asset Hub

treasurer

Bounty Closure Proposal: n.16 and n.21

### Summary of Virto Team Proposal

- **Funding Request**: The Virto team seeks funding at a reduced rate of 260 KSM per 6-day period for the remainder of 2024.
- **Purpose**: To develop light and modular client-side tools, specifically the VirtoSDK, which is multi-platform and usable in embedded hardware.
- **Focus Areas**: The team will create pallets and propose changes to enhance the PolkadotSDK, focusing on practical functionalities like reversible payments, powerful DAOs, and decentralized chat room controls.
- **Community Involvement**: They plan to test and refine these functionalities in their parachain, Kreivo, and invite community suggestions for new features.
- **Long-Term Goal**: The team aims to become self-sufficient by offering solutions as a service and tackling social inequality through the local incentives protocol.

Virto team proposes to continue developing VirtoSDK, a modular and multi-platform tool, at a reduced rate of 260KSM per 6-day spend period until the end of 2024. They will develop pallets and propose changes to enhance the PolkadotSDK, with a focus on practical functionalities. Their long-term goal is to tackle social inequality by implementing the local incentives protocol.

Virto 2024

The call in this referenda updates the `safeXcmVersion` of Kusama System Parachains to value 3.
Currently set version 2 is outdated and will be deprecated. Setting this to version 3 is required to support new V3 destinations/connections by default.
Note: Kusama Relay already has this set to 3 so that's why it's not included in the call.
Needs to be whitelisted by: <a href="https://kusama.subsquare.io/fellowship/referenda/61">https://kusama.subsquare.io/fellowship/referenda/61</a>

WHO: Kusama System Parachains 
WHAT: Update `safeXcmVersion` to value 3 
PRICE/TIMEFRAME/RESOURCES: Not specified

Set `safeXcmVersion` to 3 for AssetHub, BridgeHub and Encointer

Open HRMP channel between Kreivo and AssetHub

- The Polkadot OpenGov Observer is a tool to track OpenGov activities on Twitter.  
- It shows real-time updates and monthly summaries of Polkadot OpenGov.  
- The project needs 200 KSM ($8,730) to grow and help more people.  
- Only 13.1% of DOT holders vote in governance—they want to increase this to 40%.  
- The tool helps people understand and join Polkadot OpenGov decisions.  
- It uses Twitter, GitHub, and APIs to share updates.  
- Future plans include making OpenGov easier for everyone to use.

Dear Community,

I am thrilled to present the "Polkadot OpenGov Observer" project, We are seeking funding of 200 KSM ($8,730) to support the growth and development of this initiative.

**Project Overview:**

The [Polkadot OpenGov Observer](https://twitter.com/OpengovWatcher) is a tool designed to showcase real-time OpenGov activities on Twitter, providing a comprehensive monthly overview of Polkadot OpenGov Treasury and voters' charts. The primary objective is to enhance community engagement, encourage participation in OpenGov voting, and foster a better understanding of the Polkadot ecosystem.

**Beneficiary Information:**

-   Beneficiary: Polkadot OpenGov Observer Multisig
-   ![](https://i.ibb.co/98hxJBf/Screenshot-2024-02-16-at-12-03-08-PM.png)
-   Address:
    
    DZL1jjADYBhsRY9oJp8ETYtHV64Z4iz97Rvtj8pv2VP1nEN
    

**Requested Amount:**

-   200 KSM ($8,730)

**Purpose:**

Funding

**Mission and Impact:**

Our mission is to expand the adoption of Polkadot OpenGov across different communities. By leveraging social platforms like Twitter, where 90% of the web3 ecosystem is active, we aim to make concepts surrounding OpenGov more accessible and engaging.

Currently, only 13.1% of DOT holders participate in governance. We believe that increasing this percentage to 40% will lead to more informed and fair decisions within the Polkadot OpenGov system. Our strategy involves showcasing the activities of voters on Polkadot through the OpenGov Observer, making it a valuable tool for evaluating and choosing the best delegates.

![](https://i.ibb.co/VJg97Nw/Screenshot-2024-02-14-at-1-16-10-PM.png)

![](https://i.ibb.co/TPh3nKn/Screenshot-2024-02-14-at-1-15-36-PM.png)

**Open Source GitHub Repository**

[Polkadot OpenGov Observer](https://github.com/AshutoshSingh00001/Polkadot-OpenGov-Observer) Github repo

**List of Tools and Api's used for Twitter Bot**

_Subscan Api_

_polkassembly Api_

_Node js_

_Twitter Api_

_Express_

_Polkadot Js Api_

_Coin Gecko Api_

**Current Stats:**

-   Active Voters: 1,868,686.843
-   Referenda Participation: 13.10%

**Future Impacts and Plans:**

The project is focused on making OpenGov widely used and accessible to everyone. Our implemented features include OpenGov Activity Monitoring, displaying new vote activities in real-time, and providing a monthly overview of OpenGov, voters, and the treasury. This will be instrumental in attracting those interested in OpenGov, whether they are new to the concept or seeking funding for their web3 projects. We aim to build a vibrant and active community of developers within the web3 space.

As we move forward, we will continue to refine and expand our project, ensuring that Polkadot OpenGov becomes a central hub for decentralized decision-making and community involvement.

Thank you for considering our proposal, and we look forward to contributing to the growth and success of the Polkadot ecosystem.

Best regards, Ashutosh Singh (Project Creator and Head, Polkadot OpenGov Observer)

- Rococo discovered a slowdown in block import times when a parachain processed around 5,000 orders in one block.
- The issue was reported on GitHub.
- To fix this temporarily, the maximum number of orders was reduced from 10,000 to 500.
- This change was made using `configuration.setOnDemandMaxQueueSize`.
- The OnDemandQueue stores orders waiting to be assigned to a core.
- The new limit of 500 orders is a safe temporary measure.
- A permanent solution will be developed later.

WHO: The proposal does not mention any specific organization or individual.

WHAT: Adjusting the configuration through `configuration.setOnDemandMaxQueueSize` to limit the total number of orders temporarily to 500 due to slow block import times caused by a batch call for approximately 5,000 orders in a single block.

PRICE/TIMEFRAME/RESOURCES: No information provided.

Setting setOnDemandQueueMaxSize to 500

- **ParaSpell** is a set of tools for Polkadot and Kusama that help with cross-chain (XCM) transfers.  
- It has three main tools: **XCM SDK** (core tool), **XCM API** (simplifies XCM calls), and **XCM Router** (swaps assets while transferring).  
- **XCM SDK** works with 50+ chains and makes cross-chain transfers easy with one line of code.  
- **XCM API** helps developers by handling complex tasks, reducing server costs, and speeding up call creation.  
- **XCM Router** lets users send one asset and receive another in a single transaction.  
- The team has won awards and completed multiple grants to improve these tools.  
- They are asking for funding to keep these tools free and maintained for the community.

medium_spender

## Dear Kusama community,

##  Meet ParaSpell:

![](https://i.ibb.co/h7j6qDm/main-Logo.png)

## A set of common good XCM tools.

## This is the current state of tools:

There are three tools from which - one is core for the other two. Each tool can be installed independently.

-   [XCM SDK](https://github.com/paraspell/xcm-sdk): Core component for both API and Router. Meant to unify the cross-chain experience on Polkadot and become a layer 2 protocol that allows for seamless integration of XCM into your dApps. XCM SDK groups all 50 integrated XCM-compatible Parachain XCM Pallets into one uniform package and allows you to generate cross-chain calls with just one line.
-   [XCM API](https://github.com/paraspell/xcm-api): (LightSpell⚡️): Meant to ease the integration of XCM interoperability into your dApp, offload your dApp from heavy computing and save you costs. LightSpell implements XCM SDK into simple API endpoints.
-   [XCM Router](https://github.com/paraspell/xcm-router): (SpellRouter☄️): Meant to allow you to create XCM calls where you receive different assets than assets you send (Eg. Send -> DOT from Polkadot, receive ASTR on Astar)—all in just one call.

## The core and the only XCM SDK you will ever need

Created, when there were no other SDKs for XCM in the ecosystem. At the sole beginning of Polkadot. Born from a wild idea, to unify the XCM experience in the ecosystem. Meet our battle-hardened and well-established [XCM SDK](https://github.com/paraspell/xcm-sdk).

[![sdk](https://github.com/dudo50/dudo50/assets/55763425/4348e5e4-b4cc-4205-a890-41efc6cfac15)](https://github.com/paraspell/xcm-sdk)

### The abilities you gain by using XCM SDK:

-   Ability to transfer XCM messages from/to 50 different XCM compatible Parachains (Number of compatible chains fluctuates as some of them are added/removed)
-   Support for all three XCM transfer scenarios (UMP - Para to Relay, DMP - Relay to Para, HRMP - Para to Para)
-   Testing on testnet or localhost (You can input custom API parameter or even custom Parachain ID)
-   Useful asset queries, XCM pallet queries, minimal deposit queries and more!
-   Ability to use a keep-alive kind of XCM transfer which checks the balance of the account on the destination chain and determines if the amount you send is sufficient.

**XCM SDK has since the last 4 months of maintenance had a total of 7.287 downloads on NPMJS**

## Want to go packageless and save space? We got you

Meet our [award-winning](https://www.linkedin.com/posts/angelhack_polkadothackathonapac-activity-7108072292718428160-i1dr/?utm_source=share&utm_medium=member_desktop) and first [XCM API](https://github.com/paraspell/xcm-api) in the ecosystem. XCM API packs every XCM SDK and XCM-Router feature and allows you to implement XCM packagelessly.

[![api](https://github.com/dudo50/dudo50/assets/55763425/e81d3404-f29f-43d8-8744-a7104569b6b7)](https://github.com/paraspell/xcm-api)

### The advantages of LightSpell⚡️ XCM API for developers:

-   Simplified XCM message construction via unified patterns
-   XCM API reduces call construction time to seconds
-   Built-in user error prevention for seamless operation
-   Built-in Token authentication for DDoS prevention
-   Easy to use tech stack: Typescript, Nest.js, ParaSpell XCM-SDK
-   Completely free with an MIT license
-   Also designed for simple private deploy
-   XCM API handles complex logic and you are only required to provide basic details to create calls (Junctions and other complex details are auto-filled for you)
-   API Offloads your server from heavy computing required to construct calls (You receive constructed message already)
-   API saves you server costs (Because of the reason mentioned above)
-   API features Package-less integration (No need to install anything compared to SDK alternatives)
-   API is simple to implement (Constructed to be as dev-friendly as possible)
-   API is already live on the following link: [https://api.lightspell.xyz](https://api.lightspell.xyz)

**XCM API Served since its launch 142 days ago (September 13th. 2023) a total of 126.782 requests and faced 0 downtime**

## Sending one asset cross-chain and receiving another was never this easy

Meet our latest state-of-the-art technology called [XCM-Router](https://github.com/paraspell/xcm-router). It is easy to implement and has plenty of awesome features like automatic exchange chain selection! Featuring **579** asset exchange pools makes it the largest liquidity routing tool in the Polkadot. Try it out via [playground](https://github.com/paraspell/xcm-router/tree/main/playground)!

[![router](https://github.com/dudo50/dudo50/assets/55763425/a13e17fa-7c9f-4c36-a37a-d1770b29bee7)](https://github.com/paraspell/xcm-router)

### You gain the following advantages by implementing SpellRouter☄️:

-   The ability to transfer assets cross-chain via XCM while being able to exchange them for another asset all within one call.
-   Offlift users from the complexity of moving assets to another chain in order to exchange tokens just to send them to another chain later
-   Developers able to hide asset exchange complexity and skip multiple implementation steps
-   Developers save the time required for complex research
-   Complex logic hidden in simple one-line calls

**Eager to find out how XCM Router works? Check out the sequential diagram below.** (This example uses XCM Router implemented in XCM API)

![275827358-d0cf38cc-48e2-4b25-9853-8c2b59e0424f](https://github.com/dudo50/dudo50/assets/55763425/ae457dda-b744-453e-acd1-f8a14d86a5e8)

**XCM ROUTER has since it was introduced 49 days ago (Dec 15th. 2023) had a total of 1.826 downloads on NPMJS**

## Implementation made easy with our [docs](https://paraspell.github.io/docs/)

Meet our comprehensive [documentation](https://paraspell.github.io/docs/) covering just about every topic developers will meet with when implementing XCM and our tools into their dAPPs.

[![docs](https://github.com/dudo50/dudo50/assets/55763425/02abaaa4-8166-4058-a240-2771d3b35df2)](https://paraspell.github.io/docs/)

**Docs had a total of 109 refactor and update deployments on GitHub pages since their launch**

## Our team and history:

-   By now we completed 5 Web 3 Foundation grants meant to fund the development of our common good tools. This goes to show our dedication to the topic and the community. They can be observed here: [Phase 1](https://github.com/w3f/Grants-Program/pull/1118), [Phase 2](https://github.com/w3f/Grants-Program/pull/1245), [Phase 3](https://github.com/w3f/Grants-Program/pull/1589), [Phase 4](https://github.com/w3f/Grants-Program/pull/1817) and [Phase 5](https://github.com/w3f/Grants-Program/pull/2057).
-   We have been granted trust from the Kusama community twice in the following grant proposals that helped us further perfect our tools: [Maintenance 1](https://kusama.subsquare.io/referenda/123) and [Maintenance 2](277) in which we have 1 last month to cover (February).
-   Our latest achievement is getting 🥇first place at the Polkadot Global Series APAC 2023 Hackathon in the XCM Integration track with XCM API. [Here is the final announcement post](https://www.linkedin.com/posts/angelhack_polkadothackathonapac-activity-7108072292718428160-i1dr/?utm_source=share&utm_medium=member_desktop).

**The team behind the project has been hacking in the Polkadot ecosystem for a while now.** The team consists of 2 members:

-   Dušan Morháč: [Recent PBA 2023 Buenos Aires Alumni](https://singular.app/collectibles/statemine/20/12), Building in ecosystem since 2021, [LINKEDIN](https://www.linkedin.com/in/dudo50/), [GITHUB](https://github.com/dudo50)
-   Michael Absolon: Typescript expert with 3 years of professional experience, Building in the ecosystem since 2022, [LINKEDIN](https://www.linkedin.com/in/michael--absolon/), [GITHUB](https://github.com/michaeldev5)

## Aim of this proposal:

The proposal aims to aid server costs and maintenance for the 🥇 first [XCM API](https://github.com/paraspell/xcm-api) and [XCM ROUTER](https://github.com/paraspell/xcm-router) in the Polkadot and Kusama ecosystem. Maintaining XCM API and XCM ROUTER also includes maintaining its core component - [XCM SDK](https://github.com/paraspell/xcm-sdk). These common good tools will be fully maintained for the mentioned period starting on 1st March and ending on 1st August. This proposal allows all three tools to remain completely free for the entire Polkadot and Kusama community. It also allows our team to dedicate time to help other teams that wish to implement our tools.

### What are you getting by implementing one of our tools or more

-   Complex support with implementation (Feel free to open an issue in any repo)
-   Prompt issue solving if any occurs (Feel free to open an issue in any repo)
-   Constant updates for every package (We strive to bring new features for each tool)
-   Comprehensive [documentation](https://paraspell.github.io/docs/) for each tool
-   Reliability (Checked each month for changes in Pallets or compatible Parachains)
-   **Guarantee, that everything is free for everyone. The ParaSpell✨ team aims to deliver only the common good, be completely open-source and free with no hidden costs or subscriptions.**

### What are you getting as a non-developer/dApp user by supporting this proposal

-   Our products allow dApps to be created much faster, so you can enjoy their benefits quicker.
-   You can be sure, that dApp implementing our tool is safe for XCM as our tools are thoroughly tested and regularly updated. There are multiple ways to lose assets cross-chain.
-   You too can try our products via the Playgrounds we build [API Playground](https://github.com/paraspell/xcm-api/tree/main/playground), [Router Playground](https://github.com/paraspell/xcm-router/tree/main/playground) or try out the [deployed version of Playground](https://playground.paraspell.xyz/).
-   We have been in the ecosystem for a while now and we are hardcore ecosystem fans. We will continue maintaining the tools even if we are short of funding (Just at a slower pace). So you do not have to deal with your dApp suddenly disabling your favorite feature. This is because we primarily build and maintain these tools to make life easier for everyone - not for profits (There is no business model or hidden fees in any of our tools. They are purely common good).

## Proposal schedule

-   Discussion: 2. Feb. 2024 - 8. Feb. 2024
-   Voting: 9. Feb. 2024 - 22. Feb. 2024

## Proposal ask

The proposal seeks 30.000$ worth of funding for 5 months of various maintenance tasks and assistance to other teams. This is divided into 6.000$ per month and 25$ per work hour. More information can be found in the full proposal document.

## Documents associated with this proposal:

**[Full proposal (Contains detailed information on how we plan to use funds)](https://docs.google.com/document/d/1AfRYf-dcEec-7VXJuLtJjPMCRZ0vo145TLgZj_SPKZA/edit?usp=sharing)**

[One pager](https://www.canva.com/design/DAFuXF5a0As/ylxqRR43pe3_XRWC27IH-A/edit?utm_content=DAFuXF5a0As&utm_campaign=designshare&utm_medium=link2&utm_source=sharebutton)

[Documentation for XCM ROUTER, XCM API & XCM SDK](https://paraspell.github.io/docs/)

[Forum post prior to this discussion](https://forum.polkadot.network/t/introducing-revolutionary-set-of-xcm-tools-for-dapp-developers-paraspell/5625)

ParaSpell, a team of two, is proposing to maintain and assist other teams in implementing their set of common good XCM tools for the Polkadot and Kusama ecosystem. They are seeking $30,000 worth of funding for 5 months of maintenance tasks and assistance, divided into $6,000 per month and $25 per work hour. The proposal aims to keep their tools free for the community and includes their XCM SDK, XCM API, and XCM Router. Voting will take place from February 9th to February 22nd.

XCM ROUTER, XCM API & XCM SDK 5 months of maintenance and server cost coverage proposal

This sets BEEFY genesis to the next block after it executes, thus enabling BEEFY consensus on Kusama.
BEEFY consensus will then be used in the Kusama&lt;&gt;Ethereum Snowfork bridge.
Requires whitelist by <a href="../member-referenda/59" target="_blank" rel="noopener">https://kusama.polkassembly.io/member-referenda/59</a>

Set BEEFY genesis (thus starting BEEFY consensus on Kusama)

### Summary of Virto Team's Proposal

- **Objective**: Develop decentralized applications to combat social inequality and support local economic development.
- **Tools**: Created VirtoSDK, a toolkit simplifying blockchain interactions for users without specialized knowledge.
- **Platform**: Built Kreivo, a parachain for testing and managing decentralized communities and secure payments.
- **Expansion**: Plans to implement the Local Incentives Protocol to boost local economies.
- **Community Engagement**: Seeks support from the Kusama community for innovation and practical blockchain solutions.
- **Funding**: Requests 333 KSM weekly, with quarterly reviews to determine continued funding.
- **Transparency**: Ensures accountability through on-chain transactions and open governance.
- **Long-Term Goals**: Aim to become self-sustainable and attract more communities to the ecosystem.

Virto team requests 333 KSM/week for Kreivo, a common-good parachain that facilitates secure payments and managing decentralized communities, and VirtoSDK, a toolkit that simplifies interactions with Substrate-based chains. They aim to make blockchain technology more accessible and practical for a wide range of applications. The total cost is 63,332 USD/month for 10-12 FTE, with quarterly community reviews to determine if the team should continue to be funded.

Virto team - Kusama agents continuous funding

Bad preimage -  please vote nay

- **Request**: Asking for 3,333 KSM to help people try new ideas on Kusama.
- **Problem**: Many people want to experiment but don’t have enough money to start big projects.
- **Solution**: Create a special fund managed by trusted people to help pay for these experiments.
- **Timeline**: The money will be used for 6 months, then returned to the Treasury.
- **Signatories**: Four experienced people will manage the fund.
- **Goal**: Help more people try new ideas without needing a lot of money.

WHO: Kusama ecosystem agents Eduardo Cardoso, Rafael Yahlomi, Tommi Niemi, and Adam Steeber.

WHAT: Propose funding a multisig-managed governance proxy to place decision deposits on root track referenda or other-track referenda.

PRICE/TIMEFRAME/RESOURCES: Requested amount of 3,333 KSM for ~6 months, then refunded back to the Treasury.

Funding a Decision Deposit Sponsor

Following the new Fellowship release, this upgrades the Kusama system to v1.1.2. Requires whitelist by https://kusama.polkassembly.io/member-referenda/58

Kusama Runtime Upgrade v1.1.2

- BOTLabs GmbH registered two Kusama parachains (2086 and 2108) for the KILT Protocol.
- Parachain 2086 was used for Spiritnet but is no longer needed since KILT moved to Polkadot in October 2022.
- Parachain 2108 was used to bid for a new lease but was later swapped to 2086.
- Both parachains are no longer required.
- Unlocking a parachain was not supported at the time of registration.
- A proposal is made to deregister both chains through governance.
- The signature for parachain 2086 is provided for verification.

root

BOTLabs GmbH registered Kusama parachains 2086 and 2108 for the benefit of the KILT Protocol. Kusama ParaID 2086 is the legacy Spiritnet which is not required anymore since KILT moved to Polkadot in October 2022. 2108 was used to bid for a new lease which was later swapped to 2086. Both chains are no longer required, but at the time of registration, unlocking a parachain was not supported. We therefore propose to deregister both chains via governance. Please verify the signatures of both registrar accounts for 2086 and 2108.
SIgnature of parachain 2086: <code>0xe4458ecaaaa955dd4d73f43f25f4792a2fd0b003a2bc5e0b2eb2868ff98af916fd5bee389105e47fb771ee633e3248097c890624ad7416e9e82d6ea6f4b7cc80</code>
Signature for 2108 not necessary, beacuse call submitted with that account.

BOTLabs GmbH proposes to deregister Kusama parachains 2086 and 2108, which are no longer required for the KILT Protocol. They request governance to verify the signature of the registrar account for 2086. No price, timeframe, or resources mentioned.

Deregister parachachain IDs 2086 and 2108

- The proposal is about adding Brale and Glo Dollar to Kusama AssetHub.
- The community now knows more about the treasurer track.
- Kusama's confirmation time is now 48 hours, not 3 hours.
- Fixed a mistake in a payment amount (2475 was corrected from 24755).
- Brale's technical integration will take 16 weeks instead of 12 for extra audits.
- More details on launching Kusama and Polkadot stablecoins in later phases.
- A graphic was added to explain the phases.

See full proposal <a href="https://rfc.decent.partners/t/onboard-brale-and-glo-dollar-to-kusama-assethub-v2/57">here</a>
Updates from v1.
&mdash; community have more familiarity with treasurer track.
&mdash; Kusama confirmation period now 48 hours rather than 3 hours post upgrade.
&mdash; corrected issue with a spend amount in one payment (2475 was 24755 in preimage).
&mdash; <a href="https://brale.xyz">Brale</a> technical integration expected to be 16 weeks rather than 12 weeks to give extra time for audits.
&mdash; more detail on opportunity to launch Kusama and Polkadot branded stablecoins in phase 2a/2b.
&mdash; addition of this graphic to explain phases.
<img src="https://i.ibb.co/WKNr9gc/blobid1.png" alt="" />

WHO: Not specified
WHAT: Onboard Brale and Glo Dollar to Kusama AssetHub v2
PRICE/TIMEFRAME/RESOURCES: Not specified, but Brale technical integration expected to take 16 weeks instead of 12 weeks to allow for extra audits. Opportunity to launch Kusama and Polkadot branded stablecoins in phase 2a/2b.

Onboard Brale and Glo Dollar to Kusama AssetHub v2 - inc ability to create Kusama & Polkadot branded stablecoins

We'd like to bring TEER as foreignAsset to Asset Hub&nbsp;

Open HRMP channels between Integritee and Asset Hub

- Encointer asked for money to keep working until December 2023.  
- They made a plan to keep their project running without needing more money soon.  
- They fixed their phone app and made it better.  
- They helped communities in Tanzania and Argentina.  
- They made a group in Zurich to help more people use their project.  
- They want to keep their project working well with a small team.  
- They will focus on helping places where their work can do the most good.

We ask the Kusama Treasury for **CHF 89’000 ≃ USD 103’240 ≃ 2706 KSM** for the period Sep-Dec 2023 (4 mt)

The [Encointer](https://encointer.org/) team has scaled down significantly after rejected proposals on Polkadot but continues to deliver:

work done:

-   Conceptualize a [self-sustainable economy](https://forum.polkadot.network/t/towards-encointer-self-sustainability/4195/1) which can plausibly be reached within few years.
-   integrate [encointer runtime into fellowship repository (RFC22)](https://github.com/polkadot-fellows/runtimes/pull/80)
-   stabilize and refactor Encointer mobile app to use [PolkaDart](https://github.com/leonardocustodio/polkadart)
-   grow Nyota community in Tanzania
-   prepare community in Puerto Madryn, Argentina
-   establish an association of acceptance points in Zurich to grow the network and close economic cycles

outlook:

-   with a minimal but powerful team we aim to keep the Encointer parachain running and well-maintained
-   we aim to focus on supporting and growing the global south communities where our tech promises the biggest impact at low costs

[Full Proposal Document](https://docs.google.com/document/d/1ep0MCQDMr--1y5CSYkIKS09oRwnnuyusDfH2S0j6oCw/edit?usp=sharing)

Appearance on [AAG 102](https://twitter.com/TheKusamarian/status/1752037309413793928)

Encointer team requests **CHF 89,000** for Sep-Dec 2023 to maintain and grow their self-sustainable economy project on Kusama. They aim to support global south communities and have achieved significant progress in integrating their runtime into the fellowship repository and stabilizing their mobile app.

Encointer Retroactive Funding for Sep-Dec 2023

- This vote removes old, broken keys from storage.  
- 19 keys were from a 2019 upgrade that went wrong.  
- 381 more keys were inactive and couldn't be read.  
- No active validators were affected.  
- The removal was checked by code to be safe.  
- The Fellowship group approved this change.  
- The person who suggested this is verified.

This referendum cleans up all undecodable keys from storage.

The first 19 keys removed are undecodable Locks, which were not migrated correctly during a runtime upgrade in 2019. See [this issue](https://github.com/polkadot-fellows/runtimes/issues/104) and [this PR](https://github.com/polkadot-fellows/runtimes/pull/122) for more info.

The remaining 381 keys removed are undecodable, inactive SessionKeys also likely created due to a bad runtime upgrade. See [this comment](https://github.com/polkadot-fellows/runtimes/issues/140#issuecomment-1898081577), [this issue](https://github.com/paritytech/polkadot-sdk/issues/1149), and [this other issue](https://github.com/polkadot-fellows/runtimes/issues/151) for more info.

This call was programatically created and verified for safety checking that

1.  There are no longer any undecodable keys on Kusama
2.  Only Locks from the faulty 2019 runtime upgrade are removed
3.  No session keys removed are from the active validator set

using the code at [this commit](https://github.com/polkadot-fellows/runtimes/compare/main…liamaharon:runtimes:liam-kusama-undecodable-keys-check-safe-removal).

Whitelisted by Fellowship in [this referenda](https://kusama.subsquare.io/fellowship/referenda/57).

---

The identity for [this account](https://www.subscan.io/account/DDdfRGvKc9i2BTnqe5T2yBYuY88DxVmCjs66pLiy77TskWo) is verified on Polkadot - `liamaharon` Fellowship rank I.

WHO: Polkadot-Fellows

WHAT: Remove undecodable keys from Kusama storage, including 19 undecodable Locks and 381 inactive SessionKeys.

PRICE/TIMEFRAME/RESOURCES: Not specified.

OpenGov Referenda

Referenda Tracks