candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

- DOT can be used on Kusama through a special bridge.  
- Around 4900 DOT are on Kusama right now.  
- DOT can be sent to Kusama’s Treasury for spending.  
- A rate is set to control how much DOT can be spent (1 DOT = 10 USDC/USDT).  
- Kusama uses a rate of 1 KSM = 4 DOT for spending limits.  
- DOT and KSM have different decimal places (DOT: 10, KSM: 12).  
- This rate helps Kusama’s treasury understand DOT amounts correctly.  
- The rate is set by a governance vote.

Deciding

treasurer

Set Asset rate for DOT/KSM to enable treasury spends of DOT through Kusama OpenGov

- This referendum moves DOT funds to the Kusama Treasury track.  
- Polkadot and Kusama can share DOT using a bridge.  
- About 4900 DOT are already on Kusama.  
- The treasury needs rules to spend DOT properly.  
- A rate of 1 KSM = 4 DOT is set for spending limits.  
- This helps Kusama OpenGov understand DOT values.  
- The rate can be changed later if needed.

Preparing

root

DO NOT PLACE DECISION DEPOSIT - Moving Ref to Treasurer Track

Approved

whitelisted_caller

[Whitelisted Caller] Upgrade Kusama to v1.5.0

[Whitelisted Caller] Referendum #297: Upgrade Kusama v1,000,000

small_tipper

WHO: Proponent 16JVrgg7t6m5UXAtDBM7jYp9XjAxALRVFP6GuKVFmi9HLw8d (Batman, Polkadot)

WHAT: Funding for further development of the dotappstore, including Dynamic App Pages with user authentication, upvote feature, claim feature, and report feature.

PRICE/TIMEFRAME/RESOURCES: 1,800 DOT (~$6,500) requested on 13 Oct 2023. Codebase is open-source and available on Github.

WHO: The proposer.

WHAT: Develop a UI for tracking weight consumption over all Polkadot and Kusama parachains.

PRICE/TIMEFRAME/RESOURCES: Requesting a tip for the developed code. Will register a custom domain for the website if approved. No specific price, timeframe, or resources mentioned.

- This proposal is part of a series to improve Kusama OpenGov.
- It builds on two earlier milestones: Milestone 0 and Milestone 0.5.
- So far, 54 audits have been completed, with 19 done by new auditors.
- A new challenge is the lack of feedback during proposal discussions.
- Milestone 1 focuses on more audits, expanding auditor roles, and using post-paid tips for transparency.
- The goal is to audit 60 treasury proposals in 2 months.
- Milestone 1.5 continues educating and onboarding new auditors.
- More details are in the full proposal linked above.

small_spender

Kusama OpenGov proposes to continue on-chain proposal audits, expand auditor tasks, and introduce auditor and reviewer roles in Milestone 1. The goal is to deliver audit reports for 60 treasury proposals over two months, with all work being post-paid through self-submitted tips. The proposal aims to ensure transparency and community involvement by transferring the audit process to the Kusama community. The proposal also includes a continuation of Referenda #67 - Proposal Extension to onboard additional community auditors.

OpenCommunity Governance - Proposal Audit Reports

### Substrate-API-Client

- **Purpose**: Connects to a Substrate-based node via RPC.
- **Alternative**: Alternative to `subxt`.
- **Importance**: Essential for Rust developers working with Substrate parachains.
- **Features**:
  - Supports `no_std` environments.
  - Facilitates extrinsic creation in trusted hardware (e.g., Intel SGX).
  - Potential for IoT applications.
- **Interface**: Easy-to-use with practical examples.
- **Proposal**:
  - Maintenance and support for 3 months (Nov-22 to Jan-23).
  - Evaluation and design of two new features:
    - CLI wallet implementation.
    - Full `no_std` compatibility.

For more details, see the [discussion](https://kusama.polkassembly.io/post/1923) and [full proposal](https://docs.google.com/document/d/1miIIMyHsNzdoZejVdBiV_u3NLyj7CHsr9uWBdKonrtQ/edit?usp=sharing).

big_spender

WHO: The proposal is made by the substrate-api-client team.

WHAT: The proposal aims to fund maintenance and support for the substrate api client over 3 months, along with the evaluation and design of two new features: CLI-wallet implementation and full no_std-compatibility.

PRICE/TIMEFRAME/RESOURCES: The funding is required for 3 months (Nov-22 until Jan-23). The cost is not mentioned in the summary.

Treasury Proposal: Maintenance for the substrate-api-client Nov-22 to Jan-23

- The post requests a top-up for the Moderation Team Bounty.
- The top-up is needed due to current market conditions.
- Changes have been made to the initial proposal.
- Details and spending analysis are available in a linked document.
- The original bounty top-up post is also linked for reference.
- The community is thanked for their attention.

WHO: The community.

WHAT: Requesting a top-up to the Moderation Team Bounty to continue funding their contributions and support.

PRICE/TIMEFRAME/RESOURCES: Details can be found in the proposal linked.

Treasury Proposal: Moderation Team Bounty Top-up

### Summary of Math Crypto's Batch Delegation Guide

- **Purpose**: Provides a guide and tool for delegating all Gov2 tracks on Kusama to a single account in one transaction.
- **Resources**: Includes a [steps guide](https://www.math-crypto.com/opengov/batch-delegate/) and a [web page](https://backend-opengov.math-crypto.com/) with a delegation hash generator.
- **Benefit**: Simplifies the process for users who want to delegate multiple votes at once.
- **Proponent's Action**: The guide's proponent plans to use the new Gov2 system for a tip in an unused track.
- **Status**: Gov2 is operational and ready for use on Kusama.

big_tipper

WHO: Math Crypto

WHAT: Provides a batch delegation guide and web page with a delegation hash generator for OpenGov/Gov2 on Kusama.

PRICE/TIMEFRAME/RESOURCES: Not specified.

Gov2 - Batch delegation step guide

### Summary of OpenGov Referendums

1. **Referendum 1 and 2**: Initially proposed but found to be unsuccessful due to the use of `treasury.ApproveProposal`, which requires root origin.

2. **Resubmitted Proposals**: The teams resubmitted their proposals using the `Treasurer` and `Big spender` tracks with the call `treasury.Spend`.

3. **New Referendums**:
   - **Referendum 3**: Funds the development of **Snowbridge**.
   - **Referendum 5**: Supports **Polkawatch**'s decentralization analytics and Parachain operations.

4. **Cancellation Service**: Uses the Referenda Canceller track to cancel Referendums 1 and 2, replaced by Referendums 5 and 6.

referendum_canceller

WHO: OpenGov
WHAT: Resubmitted Referendum 3 and 5 to fund Snowbridge and Polkawatch's operations respectively, using treasury.Spend call. Also cancelling Referendum 1 and 2.
PRICE/TIMEFRAME/RESOURCES: Not specified.

Referendum aiming to cancel two invalid Referendums (1 & 2)

### Polkawatch Proposal Summary

- Polkawatch recently launched decentralization analytics on Kusama and added Nomination Pools support.
- The community is increasingly aware of the importance of decentralization, sparked by a recent deplatforming event of Solana nodes.
- Other teams, including wallets, parachains, and data scientists, are interested in accessing Polkawatch data to raise awareness in the ecosystem.
- Parachains, while secured by the relay chain, are still vulnerable to censorship from dishonest collators, network operators, or regulatory changes.
- This proposal aims to extend Polkawatch support to parachains, continue service operations, and make minor improvements.
- The proposal has been discussed and feedback has been incorporated.
- A detailed version of the proposal is available [here](https://docs.google.com/document/d/1ljvYDuazbNBgjf94yFUbUEdeyBN5ixG6BXAEKxuxmL4/edit?usp=sharing).
- An extraordinary fee for re-submission costs has been included.

Polkawatch proposes to bring parachain support to their decentralization analytics service, following interest from other teams in the ecosystem. The proposal includes continued operation of the service and minor improvements, with an extraordinary fee included for re-submission costs. No specific price, timeframe, or resources are mentioned.

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

### Ordum: Public Good Grants Aggregator

- **Purpose**: Ordum aims to create a public good grants aggregator for the Polkadot and Kusama ecosystems, focusing on R&D funding.
- **Current Issue**: Existing grant management tools like Gitcoin are insufficient for the needs of web3 ecosystems, leading to scattered information and difficulties in tracking funding.
- **Problem**: Treasuries and foundations have excess funds due to a lack of projects, and grant information is hard to find and manage.
- **Solution**: Ordum proposes a decentralized application (dapp) to index and manage grants, including features like custom APIs, light clients, and integration with Github.
- **Milestone Certificates**: Non-transferable NFTs will be minted to certify completed milestones, enhancing transparency and accountability.
- **Transparency**: Grant applications, funding, and milestones will be displayed on team profiles for public viewing.
- **User Experience**: Surveys and feedback will be used to optimize the UX for managing treasury grants.
- **Funding Request**: Ordum seeks $78,804 for development, with a Kusama rate of 25.24 as of November 24, 2022.

Ordum proposes to build a public goods grant aggregator for the Polkadot and Kusama ecosystems to solve the scattered information and lack of software for managing grants. They plan to create a dapp, mint non-transferable NFTs, display milestones and funding on a team's profile, and issue surveys for optimal grant management. They request funding of 78,804 USD and aim to deliver a V1 POC of the aggregator.

 Treasury Proposal: Ordum | Public Good Grants Aggregator for Polkadot and Kusama 

Executed

[Runtime 1.4.3] Upgrade Kusama Asset Hub

- A team will build a simple app called [kusama.app](https://kusama.app) for newcomers.  
- It helps people start projects or groups easily, even without Web3 knowledge.  
- No wallet or tokens needed to begin.  
- The app will include basic tools for managing groups and assets.  
- First step (Q2): Design and a working prototype.  
- Second step (Q3): A working DAO governance system.  
- Budget: 8000 KSM.  
- Curators will oversee the project.

Rejected

KSM RFP #3 - Kusama.App ~ $100K price!

DotShield is a new Web3 bot designed to improve security in Telegram and Discord communities within the Polkadot and Kusama ecosystem. It helps with moderation, verification, and scam prevention. Here are some key points about DotShield:

1. It solves the problem of existing bots that use easy-to-bypass captchas instead of Web3 verification.
2. DotShield allows groups to set their own criteria for membership, like balance thresholds and council membership.
3. It is important because it helps protect Web3 communities from spam, bot invasions, and scams.
4. The creator of DotShield learned to code to make this solution after being frustrated with existing options.
5. DotShield has features like dynamic chain state verification, single sign-in for Web3 users, flexible moderation, scam prevention, and expansion to Discord.
6. The creator is asking for funding to support the deployment and expansion of DotShield.
7. Users have given DotShield good feedback, with suggestions for improvement like more detailed guides and better transparency about data handling.
8. Many users would recommend DotShield to others and support its adoption across the Polkadot ecosystem.

DotShield - Take back control of your community

PolkaTalent is a new project by Kunveno and Virto, creators of Kreivo. It is part of the work3spaces vision, a decentralized marketplace to connect freelancers with companies. The project aims to help freelance professionals in Web3. They are recruiting Web3 freelance developers for early user journey interviews to design intuitive UX flows. Interviews will be from April 7 to April 11, and participants will be compensated with 4 KSM for a 45-60 minute call. Apply before April 7 to join and help shape the future of decentralized work.

<img src="https://i.ibb.co/Dgfyxqz4/Green-Rustic-Organic-Stamp-Textured-Circle-Sticker-4.png" alt width="154" height="154" />
We&rsquo;re excited to officially introduce PolkaTalent, a new project developed by <a href="https://kunveno.xyz/">Kunveno</a> in collaboration with the amazing <a href="https://virto.network/">Virto</a> crew&mdash;the builders behind Kreivo, one of the most forward-thinking networks in the Kusama ecosystem focused on simplifying the creation and management of decentralised organisations.
All of this feeds directly into our <a href="https://cloud.disroot.org/s/S9F8qEJj973tggb">white paper</a>, where we detail how PolkaTalent fits into the broader work3spaces vision&mdash;a decentralised marketplace designed to connect freelancers with companies seeking top-tier talent, built on fair reputation, transparent value, and trustless coordination.
PolkaTalent is part of our broader mission to unlock new pathways for freelance professionals in Web3. Think of it as a decentralised talent engine that starts by listening to those who know the industry best&mdash;you.
We&rsquo;re currently recruiting Web3 freelance developers active in the Polkadot and Kusama ecosystems to join us for early user journey interviews. Your insights will help us design intuitive UX flows tailored to real dev needs and workflows in this space.
📆 Interviews will run from April 7 to April 11.
💰You&rsquo;ll be compensated with 4 KSM for a 45&ndash;60 minute call.
If you are a Web3 developer excited to shape the future of decentralised work and co-create with us from day 1, <a href="https://blocksurvey.io/polkatalent-developer-ux-journey-u2jumdYtQ0W7nV3a574B2g?v=o">apply here</a> before April 7.
Let&rsquo;s build something incredible, together.

PolkaTalent: Recruiting Web3 freelance devs for early user journey interviews

Kusama AssetHub has registered several assets with Polkadot Assethub as the owner. These assets include popular tokens like ETH, WETH, USDT, USDC, and many others. The goal is to support bridging ERC-20 tokens from Ethereum to Kusama in two steps: first from Ethereum to Polkadot, and then from Polkadot to Kusama using the P<>K bridge. A test demonstrating this process has been added to a GitHub repository.

Registers the following assets on Kusama AssetHub (with the asset owner being Polkadot Assethub &mdash;
<a href="https://assethub-kusama.subscan.io/account/FwGjEp7GXJXT9NjH8r4sqdyd8XZVogbxSs3iFakx4wFwJ5Y?tab=transfer">FwGjEp7GXJXT9NjH8r4sqdyd8XZVogbxSs3iFakx4wFwJ5Y)</a>:&nbsp;
<table style="border-collapse:collapse; width:100%; height:1190px;" border="1">
<tbody>
<tr>
<td style="width:31.2267%; height:49px;">
Token
</td>
<td style="width:31.2267%; height:49px;">
Address
</td>
<td style="width:31.2267%; height:49px;">
Token Name
</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
ETH
</td>
<td style="width:31.2267%; height:49px;">
Ether
</td>
<td style="width:31.2267%; height:49px;">&nbsp;</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
WETH
</td>
<td style="width:31.2267%; height:49px;">
0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2
</td>
<td style="width:31.2267%; height:49px;">
Wrapped Ether (WETH)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
USDT
</td>
<td style="width:31.2267%; height:49px;">
0xdac17f958d2ee523a2206206994597c13d831ec7
</td>
<td style="width:31.2267%; height:49px;">
Tether USD (USDT)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
USDC
</td>
<td style="width:31.2267%; height:49px;">
0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48
</td>
<td style="width:31.2267%; height:49px;">
USD Coin (USDC)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
Staked USDe
</td>
<td style="width:31.2267%; height:49px;">
0x9d39a5de30e57443bff2a8307a4256c8797a3497
</td>
<td style="width:31.2267%; height:49px;">
Staked USDe (sUSDe)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
Pepe
</td>
<td style="width:31.2267%; height:49px;">
0x6982508145454ce325ddbe47a25d4ec3d2311933
</td>
<td style="width:31.2267%; height:49px;">
Pepe (PEPE)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
LDO
</td>
<td style="width:31.2267%; height:49px;">
0x5a98fcbea516cf06857215779fd812ca3bef1b32
</td>
<td style="width:31.2267%; height:49px;">
Lido DAO (LDO)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
Savings USDS
</td>
<td style="width:31.2267%; height:49px;">
0xa3931d71877c0e7a3148cb7eb4463524fec27fbd
</td>
<td style="width:31.2267%; height:49px;">
Savings Dai (sDAI)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
LBTC
</td>
<td style="width:31.2267%; height:49px;">
0x8236a87084f8b84306f72007f36f2618a5634494
</td>
<td style="width:31.2267%; height:49px;">&nbsp;Liquid BTC (LBTC)</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
EurC
</td>
<td style="width:31.2267%; height:49px;">
0x1abaea1f7c830bd89acc67ec4af516284b1bc33c
</td>
<td style="width:31.2267%; height:49px;">
Euro Coin (EURC)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
Sky
</td>
<td style="width:31.2267%; height:49px;">
0x56072c95faa701256059aa122697b133aded9279
</td>
<td style="width:31.2267%; height:49px;">
SkyToken (SKY)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
Myth
</td>
<td style="width:31.2267%; height:49px;">
0xba41ddf06b7ffd89d1267b5a93bfef2424eb2003
</td>
<td style="width:31.2267%; height:49px;">
Mythos (MYTH)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:70px;">
tBTC v2
</td>
<td style="width:31.2267%; height:70px;">
0x18084fba666a33d37592fa2633fd49a74dd93a88
</td>
<td style="width:31.2267%; height:70px;">
Threshold Network tBTC v2
</td>
</tr>
<tr>
<td style="width:31.2267%; height:70px;">
wstETH
</td>
<td style="width:31.2267%; height:70px;">
0x7f39c581f595b53c5cb19bd0b3f8da6c935e2ca0
</td>
<td style="width:31.2267%; height:70px;">
Wrapped liquid staked ETH (wstETH)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
TONCOIN
</td>
<td style="width:31.2267%; height:49px;">
0x582d872a1b094fc48f5de31d3b73f2d9be47def1
</td>
<td style="width:31.2267%; height:49px;">
Toncoin (TONCOIN)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
DAI
</td>
<td style="width:31.2267%; height:49px;">
0x6b175474e89094c44da98b954eedeac495271d0f
</td>
<td style="width:31.2267%; height:49px;">
Dai Stablecoin (DAI)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
SHIB
</td>
<td style="width:31.2267%; height:49px;">
0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce
</td>
<td style="width:31.2267%; height:49px;">
Shiba Inu (SHIB)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:70px;">
WBTC
</td>
<td style="width:31.2267%; height:70px;">
0x2260fac5e5542a773aa44fbcfedf7c193bc2c599
</td>
<td style="width:31.2267%; height:70px;">
Wrapped Bitcoin (WBTC)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
tBTC (v1)
</td>
<td style="width:31.2267%; height:49px;">
0x8daebade922df735c38c80c7ebd708af50815faa
</td>
<td style="width:31.2267%; height:49px;">
tBTC (Keep Network v1)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
Kilt
</td>
<td style="width:31.2267%; height:49px;">
0x5d3d01fd6d2ad1169b17918eb4f153c6616288eb
</td>
<td style="width:31.2267%; height:49px;">
Kilt Protocol (KILT)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
LINK
</td>
<td style="width:31.2267%; height:49px;">
0x514910771af9ca656af840dff83e8264ecf986ca
</td>
<td style="width:31.2267%; height:49px;">
Chainlink (LINK)
</td>
</tr>
<tr>
<td style="width:31.2267%; height:49px;">
AAVE
</td>
<td style="width:31.2267%; height:49px;">
0x7fc66500c84a76ad7e9c93437bfc5ac33e2ddae9
</td>
<td style="width:31.2267%; height:49px;">
Aave (AAVE)
</td>
</tr>
</tbody>
</table>
The plan is to support bridging ERC-20s to Kusama by double bridging from Ethereum -&gt; Polkadot and then from Polkadot -&gt; Kusama in a second hop through the P&lt;&gt;K bridge. A test demonstrating this has been added here:&nbsp;
<a href="https://github.com/polkadot-fellows/runtimes/pull/625">https://github.com/polkadot-fellows/runtimes/pull/625</a>

[Whitelisted Caller] - Register Snowbridge ERC-20 Assets on Kusama

A Request for Proposal (RFP) was introduced on AAG to create a simple user interface (UI) for launching RFPs. The prize pool for this project is $10,000, with a Finder's Fee of $1,000 and Supervisors receiving $1,000. The project requires 945 KSM (Amount + 25%).

The project timeline is as follows:
- Monday, March 31: Single-ref Bounty + Curators
- 2 Weeks after Bounty Funding: Submission Deadline
- Saturday, May 31: Project Completion

The project scope includes:
- Dapp: Connect popular Substrate wallets to the app (Nova Wallet, Talisman, Subwallet)
- User Interface: Browser-based, mobile-ready UI hosted on IPFS, User Manual, Present fields for RFP proposes to fill in, Checks balance for launching Treasurer track referendum & submitting Decision Deposit
- Project Scope Fields: Funding Fields, Supervisors (Bounty Curators), Timeline, Project Scope, Milestones
- RFP Launcher: Create multi-sig for Curators, Create “One-shot” Bounty on Treasurer track with curators and scheduled payment, Generate Markdown-ready text for Subsquare/Polkassembly
- Open-Source Delivery: All code published under the MIT license, Publicly accessible repositories, Project updates shared transparently via Polkassembly, Subsquare, or Polkadot Forum from Team with Milestone deliveries, Developer & User documentation

Milestones:
1. Basic Dapp & UI: $3,000 USD, 1 week
2. RFP Creation: $3,000 USD, 1 week
3. Mainnet Deployment: $4,000 USD, 2 weeks

The Finder's Fee is set aside to incentivize a broad search for the right implementor and is paid out at the time of team engagement. Teams that submit themselves can collect their own Finder's Fee at the completion of the project.

<img src="https://i.ibb.co/NnT7GGmw/image-1.jpg" alt />
This RFP was introduced on <a href="https://www.youtube.com/live/70TkeD6rVB0?si=9NLgRYDK7dBf9jqo&amp;t=639">AAG</a> to create a simple UI to launch RFPs in the style of ref below.&nbsp;&nbsp;
<h3>APPLY NOW - pls fill out <a href="https://forms.gle/gVpTzFSsPUC7DYFcA">this form</a>.</h3>
<hr />
Prize Pool: $10,000 Finder&rsquo;s Fee: $1,000 ** Supervisors: $1,000
945 KSM Requested (Amount + 25%)
<h3>Supervisors (Bounty Curators)</h3>
<ul>
<li>Leemo</li>
<li>Jay Chrawnna</li>
<li>Jose</li>
</ul>
Excess or unused funds will be returned to the treasury by Bounty Curators.
<h3>Timeline</h3>
Monday, March 31 - Single-ref Bounty + Curators ✅ 2 Weeks after Bounty Funding - Submission Deadline Saturday, May 31 - Project Completion
<h3>Project Scope</h3>
Dapp
<ul>
<li>Connect popular Substrate wallets to app (Nova Wallet, Talisman, Subwallet)</li>
</ul>
User Interface
<ul>
<li>Browser-based, mobile-ready UI hosted on IPFS</li>
<li>User Manual</li>
<li>Present fields for RFP proposes to fill in</li>
<li>Checks balance for launching Treasurer track referendum &amp; submitting Decision Deposit</li>
</ul>
Project Scope Fields
<ul>
<li>
Funding Fields -- Prize Pool -- Finder&rsquo;s Fee (Fixed 1k, 2k, 5k, 10k) -- Supervisors&rsquo; Fee
</li>
<li>
Supervisors (Bounty Curators) -- Add addresses
</li>
<li>
Timeline -- Funds Expiry (if no submissions after n weeks following bounty funding) -- Project Completion Deadline
</li>
<li>
Project Scope -- Text field to describe scope
</li>
<li>
Milestones -- Add Milestone Button -- Text field -- Amount -- Check that Milestone amounts = &ldquo;Prize Pool&rdquo;
</li>
</ul>
RFP Launcher
<ul>
<li>Create multi-sig for Curators</li>
<li>Create &ldquo;One-shot&rdquo; Bounty on Treasurer track with curators and scheduled payment. See example.</li>
<li>Generate Markdown-ready text for Subsquare/Polkassembly</li>
</ul>
Open-Source Delivery
<ul>
<li>All code published under the MIT license</li>
<li>Publicly accessible repositories Project updates shared transparently via Polkassembly, Subsquare, or Polkadot Forum from Team with Milestone deliveries</li>
<li>Developer &amp; User documentation</li>
</ul>
<h3>Milestones</h3>
Milestone 1, Basic Dapp &amp; UI: $3,000 USD 1 week
<ol>
<li>Connect Wallet</li>
<li>RFP Creation Flow</li>
<li>Total USD converted to KSM + 25%</li>
<li>Validated by Supervisors</li>
</ol>
Milestone 2, RFP Creation: $3,000 USD 1 week
<ol>
<li>Chopsticks demonstration of on-chain Treasurer Track ref</li>
<li>App checks balance for Multi-sig reserve deposit, Ref Launch &amp; Decision Deposit</li>
<li>Creation Multi-sig</li>
<li>Scheduler Calculations for filling Bounty</li>
<li>UI Integration</li>
</ol>
Milestone 3, Mainnet Deployment: $4,000 USD 2 weeks
<ol>
<li>Improved UI Design</li>
<li>User Manual included</li>
<li>Demonstration of RFP launching capabilities</li>
<li>Documentation</li>
</ol>
<hr />
re: Finder&rsquo;s Fee: this payment is set aside to incentivize a broad search for the right implementor. Finder&rsquo;s Fees are paid out at time of team engagement. Teams that submit themselves can collect their own Finder&rsquo;s Fee at completion of project.

KSM RFP #2 - RFP Launcher Dapp - $12k Total Prize!

This proposal is about changing the target for coretime sales in the Kusama ecosystem. The main idea is to adjust the "ideal_bulk_proportion" parameter from 100% to 40%. This change will help coretime prices be more realistic and benefit the Kusama ecosystem. The main use of KSM is to pay for coretime, but the current prices are very low, which is not good for the system. By making this change, we can find the true value of coretime and keep the current inflation rate that supports validator operations. This is just a starting point, and the parameter can be adjusted in the future based on how the market responds and the needs of the ecosystem.

Adjust (only) ideal bulk proportion

Kusama Fellowship Referenda 97 is a proposal to increase the parachain validator set size from 600 to 700, keeping the maximum backing group size at 5. This change will increase the total number of usable cores to 140. The proposal also updates the setNDelayTranches from 257 to 299 to maintain the number of assignments per candidate at around 2.33. The justification for this parameter can be found in the ELVES paper and a discussion on the Polkadot SDK GitHub page.

This referenda increases the parachain validator set size from 600 to 700. The maximum backing group size is kept to 5, so the total number of usable cores increases to 140.
Additionally, also update the setNDelayTranches from 257 to 299, so that the number of assignments per candidate stays constant to around ~2.33, the justification why this is the desired value for this parameter can be found in ELVES <a href="https://eprint.iacr.org/2024/961">https://eprint.iacr.org/2024/961</a> paper and here.<a href="https://github.com/paritytech/polkadot-sdk/issues/6853#issuecomment-2540373492.">https://github.com/paritytech/polkadot-sdk/issues/6853#issuecomment-2540373492.</a>

[Whitelisted Caller] Increasing max_validators to 700

We want to move Youdle DAO's money to a safer place called Kusama Treasury. The people who control the money now, Invarch team, have made some bad choices with the money before. They moved a lot of ASTAR money without telling anyone. People are worried and want to know what's going on, but the team doesn't give clear answers. 

To keep the money safe, we should move the rest of the money (400 KSM) to Kusama, where it can be managed better. Later, we will give the money back to Youdle DAO in a way that everyone can see and trust. We hope everyone will agree with this plan to keep the DAO's money safe.

Here are some examples of why we don't trust the Invarch team:
- They moved money to a place called CEX without a good reason.
- They were supposed to share Pink tokens with the community, but they gave a lot to their own founder instead.
- They launched a new token called VARCH, and people who bought it lost a lot of money.
- They didn't give all the KSM tokens they promised.
- They shut down a project called Tinkernet and gave people VARCH tokens instead, which turned out to be bad too.

TimedOut

To prevent potential mismanagement of Youdle DAO treasury funds, we propose temporarily transferring these assets to the Kusama Treasury, which is now the safest option.
Rationale:
The Invarch team, which currently controls the funds, has a history of questionable financial decisions, including the transfer of more than 200K ASTAR from the DAO to a CEX without transparency.
Community members have raised concerns and asked questions about fund management, but the team has not provided clear answers.
To ensure responsible management, these remaining funds (400 KSM) should be safeguarded under Kusama governance.
Next Steps:
The funds will later be returned to Youdle DAO holders through a transparent and verifiable process.
&nbsp;
We urge the community to support this measure to protect DAO resources.
&nbsp;
Evidence: Rug on virtuals <img src="https://i.ibb.co/ksV69hZw/image.png" alt="image.png" width="397" height="352" />
 <img src="https://i.ibb.co/d07KbCzS/image.png" alt="image.png" width="434" height="546" />
&nbsp;
Polkadot treasury rugs <img src="https://i.ibb.co/gF6yFp85/image.png" alt="image.png" width="370" height="434" />
&nbsp;
Youdle DAO rug
Moving DAO funds to a CEX because it's a shared address instead of moving to another on chain address? No answers.&nbsp;
<img src="https://i.ibb.co/q3PybP6K/image.png" alt="image.png" width="394" height="321" /><img src="https://i.ibb.co/sJHcg9gj/image.png" alt="image.png" width="438" height="56" />
<img src="https://i.ibb.co/rY3JSbx/image.png" alt="image.png" width="482" height="50" />
Pink rug Pink distributed by the pink team to invarch was supposed to get distributed to the community <img src="https://i.ibb.co/HLqzpKdz/image.png" alt="image.png" width="338" height="302" />
but instead 2000000 pink were allocated to xcastronaut (invarch founder) wallet
<img src="https://i.ibb.co/HfgvmkFQ/image.png" alt="image.png" /> <img src="https://i.ibb.co/Tx54NZdx/image.png" alt="image.png" width="551" height="66" />
Then went to hydration and got sold. VARCH rug
$VARCH token launched less than 30 days ago. ICO investors are down -96% <img src="https://i.ibb.co/fdtT68tX/image.png" alt="image.png" width="415" height="200" /> 
KSM partial rug 
Not fully delivered.&nbsp; 
<img src="https://i.ibb.co/n8b29qmz/image.png" alt="image.png" width="397" height="322" />
Tinkernet rug Tinkernet (kusama parachain) was shutdown. Investors were given 4 VARCH for 1 TINKER. VARCH was later a rug so this converts Tinkernet in a rug. Before shuting down they made an LBP in Osmosis (Cosmos) which also was a rug.&nbsp;

Secure Funds 

This is a Request for Proposals (RFP) for a project to create a shielded Kusama Hub transfer system. The prize pool is $43,000, with a Finder's Fee of $2,000 and Supervisors' fee of $5,000. The project timeline starts on March 17 and ends on July 31, pending the Kusama Hub launch. The project scope includes smart contract development, user interface, anti-correlation attack mitigations, and open-source delivery. There are three milestones with specific tasks and deadlines. The project aims to create a private and secure way to deposit, withdraw, and transfer assets on the Kusama network.

<img src="https://i.ibb.co/chKdpcvh/image-1-copy.jpg" alt width="692" height="389" />
This RFP was adapted over several weeks on <a href="https://www.youtube.com/live/LlgUGCeF_KI?si=jsTdRVIvEcz4mGrU&amp;t=542">AAG</a> to turn a treasury proposal in <a href="https://kusama.polkassembly.io/post/2659">discussion</a> to an <a href="https://forum.polkadot.network/t/ksm-rfp-1-shielded-kusama-hub-transfers/12147">RFP</a> with refined scope and oversight.
<h3>To apply for the prize pls fill out <a href="https://forms.gle/wDnK6oKhzsQbzVjK9">this form</a>. &nbsp;</h3>
<hr />
Prize Pool: $43,000 Finder&rsquo;s Fee: $2,000 ** Supervisors: $5,000
<h3>Supervisors (Bounty Curators)</h3>
<ul>
<li>Flipchan</li>
<li>Byte (Erin)</li>
<li>James Slusser</li>
</ul>
Excess or unused funds will be returned to the treasury by Bounty Curators.
<h3>Timeline</h3>
Monday, March 17 - AAG Discussion &amp; this forum post! ✅ Monday, March 24 - Single-ref Bounty + Curators&nbsp;✅ 4 Weeks after Bounty Funding - Submission Deadline Thursday July 31 - Project Completion (Pending Kusama Hub Launch)
<h3>Project Scope</h3>
Smart Contract Development
<ul>
<li>A Solidity-based smart contract deployed on Kusama Hub</li>
<li>ZK enabled for private deposits &amp; withdrawals</li>
<li>Compatibility with all Kusama Hub assets</li>
</ul>
User Interface
<ul>
<li>Browser-based, mobile-ready UI hosted on IPFS</li>
<li>Support for: Deposits, Withdrawals, Transfers, XCM Transfers</li>
<li>Compatible with popular ecosystem wallets (Nova Wallet, Talisman, Subwallet)</li>
</ul>
Anti-correlation Attack Mitigations:
<ul>
<li>Fixed deposit amounts (e.g. 1, 10, 100, 1000 units)</li>
<li>Batch payouts for withdrawals to multiple users Interoperability</li>
<li>Ability to receive assets via XCM from any Kusama-connected parachain and transfer them to Kusama Hub for use in shielded pool.</li>
</ul>
Open-Source Delivery
<ul>
<li>All code (smart contracts and UI) published under the MIT license</li>
<li>Publicly accessible repositories Project updates shared transparently via Polkassembly, Subsquare, or Polkadot Forum from Team with Milestone deliveries</li>
<li>Developer &amp; User documentation</li>
</ul>
<h3>Milestones</h3>
Milestone 1, Initial Pools &amp; Basic UI: $16,200 USD 1 month
<ol>
<li>Tests - Smart contract test</li>
<li>Smart contract - ZK shielded smart contract with KSM and multi asset support on Westend or Paseo</li>
<li>Basic UI - A basic UI for interacting with the smart contract</li>
</ol>
Milestone 2, UI + XCM: $9,900 1 month
<ol>
<li>Tests - tests for all features</li>
<li>User interface design - UI design</li>
<li>XCM transfers - XCM transfer assets in UI</li>
<li>Fixed amount transfer only - Allow fixed amount transfers in the UI</li>
</ol>
Milestone 3, Mainnet Deployment: $16,900 1 - 1.5 months
<ol>
<li>Contract Migration to Kusama Assethub - Migrate contract from Testnet to Kusama Hub</li>
<li>Public documentation - Documentation for using Kusama shield and developer integration documentation</li>
<li>Test - tests for contract</li>
<li>V1 UI - User tested &amp; something we can be proud of</li>
</ol>
<hr />
** re: Finder&rsquo;s Fee: this payment is set aside to incentivize a broad search for the right implementor. Finder&rsquo;s Fees are paid out at time of team engagement. Teams that submit themselves can collect their own Finder&rsquo;s Fee at completion of project.

KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!

The Fellowship Collective is a group that works on projects related to Polkadot. They have rules that members must follow. If someone breaks these rules, they might be removed from the group. A person named Invarch did not follow the rules, so Gabe, who is an important member, thinks Invarch should not be part of the group anymore. The rules are called "tenets" and they are:

1. Always support Polkadot and not do things that hurt it.
2. Understand and follow the ideas and beliefs of Polkadot.
3. Follow the group's rules, habits, and ways of voting.
4. Be nice to other members and the people in the community.

fellowship_admin

Members of the Fellowship Collective involved in projects flagged by the <a href="https://app.ogtracker.io/mediumSpender/6">OG tracker </a>should provide a proper explanation, return the funds to the Treasury, or face expulsion.
Invarch failed to provide the first two, so Gabe, a founding member of the team, does not meet the ethical standards required to have a voice in the Fellowship. TENETS (extract from the<a href="https://github.com/polkadot-fellows/manifesto/blob/main/manifesto.pdf"> fellowship manifesto</a>) 
"Members are expected to faithfully uphold the following tenets. Clarifications to the rules should be in agreement with these tenets. Acting in clear breach of these tenets may be considered by voters as grounds for non-promotion, demotion or, in extreme cases, exclusion from the Fellowship.
 (1) Sincerely uphold the interests of Polkadot and avoid actions which clearly work against it. (2) Respect the philosophy and principles of Polkadot. (3) Respect the operational procedures, norms and voting conventions of the Fellowship. (4) Respect your fellow Members and the wider community"

OpenGov Referenda