![](https://i.ibb.co/LdjXFcbq/image-2.jpg)

### APPLY NOW - pls fill out [this form](https://forms.gle/hZKDLt3xfH75hp8e7).

---


Prize Pool: $1,200  
Finder's Fee: $100  
Supervisors: $200  

96 KSM Requested (Amount + 25%)

## Supervisors (Bounty Curators)

- Jay Chrawnna  
- Leemo

Excess or unused funds will be returned to the treasury by Bounty Curators.

## Timeline

Friday, May 23 - Single-ref Bounty + Curators ✅  
1 Weeks after Bounty Funding - Submission Deadline  
Monday, June 30 - Project Completion  

## Project Scope

Staying grounded while we reach for the stars!

The app this RFP proposes intends to rejuvenate the productive and encouraging tipping culture of Gov1!

This model offers a a field to fill in % Finders Fee for proposers who do the work of submitting the contributions of others for assessment. The %-based Finders Fee reflects the increased burden of convincing tokenholders of the tip validity!

But don't get greedy! Bigger tips will face more scrutiny by holders!

### Dapp
* Connect popular Substrate wallets to app (Nova Wallet, Talisman, Subwallet)

### User Interface
* Browser-based, mobile-ready UI hosted on IPFS
* User Manual
* Checks balance for proposing Tip
* Presents simple fields to fill
* Provides text to copy/paste into Subsquare & Polkassembly

### Project Scope Fields
* Total proposal in $USD
* Finders Fee % field
* Field auto-fills 10%
* Work submission
* Tip justification
* Tip beneficiary address
* Tip finder address (can be the same for self-submit)

### Open-Source Delivery
* All code published under the MIT license
* Publicly accessible repositories Project updates shared transparently via Polkassembly, Subsquare, or Polkadot * Forum post from Team with Milestone deliveries
* Developer & User documentation


## Milestones

### Milestone 1, Milestone 1, Basic Dapp & UI  
$350 USD

1. Connect Wallet
2. Tip proposal flow
3. Tatal USD converted to KSM + 25%
4. Presentation to Supervisors



### Milestone 2, Milestone 2, Tip Creation  
$350 USD

1. Chopsticks demonstration of on-chain Treasurer Track ref
2. App checks balance for Multi-sig reserve deposit, Ref Launch & Decision Deposit
3. UI Integration



### Milestone 3, Milestone 3, Mainnet Deployment  
$350 USD

1. Improved UI Design
2. Deployment



### Milestone 4, Milestone 4, Documentation  
$150 USD

1. User Manual
2. Documentation




- **Prize Pool**: $1,200 for a project to improve tipping culture.  
- **Supervisors**: Jay Chrawnna and Leemo will oversee the project.  
- **Timeline**: Starts May 23, ends June 30.  
- **App Features**: Connects wallets, checks balances, and helps submit tips.  
- **Open-Source**: Code will be public for everyone to use.  
- **Milestones**: Four steps to build and launch the app.  
- **Goal**: Make tipping easier and fairer in the community.

acceptCurator

KSM RFP #4 - BigTipper

![](https://i.ibb.co/NnT7GGmw/image-1.jpg)

This RFP was introduced on [AAG](https://www.youtube.com/live/70TkeD6rVB0?si=9NLgRYDK7dBf9jqo&t=639) to create a simple UI to launch RFPs in the style of ref below. 

### APPLY NOW - pls fill out [this form](https://forms.gle/gVpTzFSsPUC7DYFcA).  

---

Prize Pool: $10,000  
Finder’s Fee: $1,000 **  
Supervisors: $1,000  

945 KSM Requested (Amount + 25%)

### Supervisors (Bounty Curators)

- Leemo
- Jay Chrawnna
- Jose

Excess or unused funds will be returned to the treasury by Bounty Curators.


### Timeline

Monday, March 31 - Single-ref Bounty + Curators ✅  
2 Weeks after Bounty Funding - Submission Deadline  
Saturday, May 31 - Project Completion

### Project Scope

**Dapp**
- Connect popular Substrate wallets to 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    
-- Prize Pool  
-- Finder’s Fee (Fixed 1k, 2k, 5k, 10k)  
-- Supervisors’ Fee

- Supervisors (Bounty Curators)  
-- Add addresses

- Timeline  
-- Funds Expiry (if no submissions after n weeks following bounty funding)  
-- Project Completion Deadline  

- Project Scope  
-- Text field to describe scope

- Milestones  
-- Add Milestone Button  
-- Text field  
-- Amount  
-- Check that Milestone amounts = “Prize Pool”  

**RFP Launcher**

- Create multi-sig for Curators
- Create “One-shot” Bounty on Treasurer track with curators and scheduled payment. See example.
- 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

**Milestone 1, Basic Dapp & UI:**  
$3,000 USD  
1 week  
1. Connect Wallet
2. RFP Creation Flow
3. Total USD converted to KSM + 25%
4. Validated by Supervisors

**Milestone 2, RFP Creation:**  
$3,000 USD
1 week  
1. Chopsticks demonstration of on-chain Treasurer Track ref
2. App checks balance for Multi-sig reserve deposit, Ref Launch & Decision Deposit
3. Creation Multi-sig
4. Scheduler Calculations for filling Bounty
5. UI Integration

**Milestone 3, Mainnet Deployment:**  
$4,000 USD
2 weeks  
1. Improved UI Design
2. User Manual included
3. Demonstration of RFP launching capabilities
4. Documentation


---

re: Finder’s Fee: this payment is set aside to incentivize a broad search for the right implementor. Finder’s Fees are paid out at time of team engagement. Teams that submit themselves can collect their own Finder’s Fee at completion of project.

This is a request for proposals (RFP) to create a simple user interface (UI) for launching RFPs. The prize pool is $10,000, with a finder's fee of $1,000 and supervisors receiving $1,000. The project requires 945 KSM (Amount + 25%).

The supervisors are Leemo, Jay Chrawnna, and Jose. Any unused funds will be returned to the treasury by the Bounty Curators.

The 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, fields for RFP proposals, and balance checks for launching Treasurer track referendum and submitting Decision Deposit
- Project Scope Fields: Funding fields, supervisors (Bounty Curators), timeline, project scope, and 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.

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

Prize Pool: $43,000  
Finder’s Fee: $2,000 **  
Supervisors: $5,000  

### Supervisors (Bounty Curators)
- Flipchan  
- Byte (Erin)  
- James Slusser  

### Timeline
Monday, March 17 - AAG Discussion & this forum post! ✅
Monday, March 24 - Single-ref Bounty + Curators
4 Weeks after Bounty Funding - Submission Deadline
Thursday July 31 - Project Completion (Pending Kusama Hub Launch)

### Project Scope
**Smart Contract Development**
- A Solidity-based smart contract deployed on Kusama Hub
- ZK enabled for private deposits & withdrawals
- Compatibility with all Kusama Hub assets  

**User Interface**
- Browser-based, mobile-ready UI hosted on IPFS
- Support for: Deposits, Withdrawals, Transfers, XCM Transfers
- Compatible with popular ecosystem wallets (Nova Wallet, Talisman, Subwallet)

**Anti-correlation Attack Mitigations:**
- Fixed deposit amounts (e.g. 1, 10, 100, 1000 units)
- Batch payouts for withdrawals to multiple users  
Interoperability
- Ability to receive assets via XCM from any Kusama-connected parachain and transfer them to Kusama Hub for use in shielded pool.  

**Open-Source Delivery**
- All code (smart contracts and UI) 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
**Milestone 1, Initial Pools & Basic UI:**  
$16,200 USD  
1 month
 
1. Tests - Smart contract test
2. Smart contract - ZK shielded smart contract with KSM and multi asset support on Westend or Paseo
3. Basic UI - A basic UI for interacting with the smart contract

**Milestone 2, UI + XCM:**  
$9,900  
1 month
  
1. Tests - tests for all features
2. User interface design - UI design
3. XCM transfers - XCM transfer assets in UI
4. Fixed amount transfer only - Allow fixed amount transfers in the UI

**Milestone 3, Mainnet Deployment:**  
$16,900  
1 - 1.5 months

1. Contract Migration to Kusama Assethub - Migrate contract from Testnet to Kusama Hub
2. Public documentation - Documentation for using Kusama shield and developer integration documentation
3. Test - tests for contract
4. V1 UI - User tested & something we can be proud of 

----

** re: Finder’s Fee: this payment is set aside to incentivize a broad search for the right implementor. Finder’s Fees are paid out at time of team engagement. Teams that submit themselves can collect their own Finder’s Fee at completion of project.


This project is about creating a smart contract and user interface for a private and secure platform on the Kusama Hub. The total prize money is $43,000, with an extra $2,000 for finding the right team to work on the project. The project will be supervised by Flipchan, Byte (Erin), and James Slusser.

The project timeline starts on March 17 and ends on July 31. The project includes smart contract development, user interface, anti-correlation attack mitigations, and open-source delivery. The smart contract will be based on Solidity, have private deposits and withdrawals, and be compatible with all Kusama Hub assets. The user interface will be browser-based, mobile-ready, and hosted on IPFS.

There are three milestones in the project:
1. Initial Pools & Basic UI: $16,200, 1 month
2. UI + XCM: $9,900, 1 month
3. Mainnet Deployment: $16,900, 1-1.5 months

The Finder's Fee of $2,000 is set aside to find the right team for the project. Teams that submit themselves can collect their own Finder's Fee at the completion of the project.

KSM RFP #1 - Shielded Kusama Hub Transfers

**Proponent**: Fy6erZmPp78ZY2cN945FU9KnKdATmxvG2eB9a1kh2VX33xz

**Date**: 01.03.2024

**Requested KSM**: $250,000 (5102 KSM - based on EMA7 March 1st 2024)

**Short description**:

Bridges enable transferring data, assets, and more between multiple chains. Due to their pivotal role and high transaction volumes, they have simultaneously become a hotspot for malicious activities. When exploited, these breaches can lead to significant impact including financial losses.

This proposal aims to ensure the utmost security of the bridges and promote community involvement by implementing a Security Bug Bounty Program. While all developers involved work hard to ensure the software and protocols built are bug-free, secure by design, and third-party code audits have been already performed, it is recognised security best practices to complement this. That’s why Polkadot and Kusama need community and bug bounty hunters to help to identify security vulnerabilities that could cause impact from all the severity levels before it is widely used and adopted.

To support this, the Bug Bounty participants are provided with many context details in the full proposal [attached](https://docs.google.com/document/d/1rzvoJxMVIG1MJfHCkHDLmXYBTlkJZvUgwsP4IV4oHKw/edit), including a threat model of the scope.

As a security vulnerability in the bridge can impact both the source and destination blockchains, a mirror bounty is raised on Kusama and Polkadot

Thanks for your time and support to make Polkadot more secure !

**Proposal Summary**

- **Proponent**: Fy6erZmPp78ZY2cN945FU9KnKdATmxvG2eB9a1kh2VX33xz
- **Date**: 01.03.2024
- **Requested KSM**: $250,000 (5102 KSM)
- **Objective**: Enhance security of bridges between chains by implementing a Security Bug Bounty Program.
- **Rationale**: Bridges are crucial but vulnerable to attacks, leading to financial losses.
- **Community Involvement**: Encourage community and bug bounty hunters to identify vulnerabilities.
- **Details**: Full proposal includes threat model and context details.
- **Impact**: Vulnerabilities in bridges can affect both source and destination blockchains.

POLKADOT <> KUSAMA BRIDGE SECURITY BOUNTY

BountyExtended

*This is a joint-proposal by BlockOps, Dwellir, LuckyFriday, OnFinality, RadiumBlock, RockX, and Stakeworld. Valuable input to this proposal has also been made by the proposed curators.*

### **TL;DR:**

This proposal outlines a procurement strategy for public RPC services in Polkadot and Kusama ecosystems, aiming for high-quality, decentralized, and cost-effective services. It addresses the vital need for reliable RPCs, emphasizing their role in applications like Polkadot.JS and wallets. The strategy focuses on optimizing quality of service, sustainable cost, and decentralization, introducing key definitions and standards. Tenders from RPC providers can follow two models: cost targets or predefined service levels. The proposed budget is $400,000, split between Polkadot and Kusama treasuries.

### **Introduction**

This proposal aims to implement a procurement strategy for public RPC services in the Polkadot and Kusama ecosystems. The goal is to ensure high-quality, decentralized, and cost-effective services for essential applications like Polkadot.JS and wallets. The need for robust public infrastructure was emphasized during Polkadot Decoded discussions.
Problem Statement

Reliable public RPC services are crucial for the growth of the Polkadot and Kusama ecosystems. Existing applications, such as Polkadot.js.org and Nova Wallet, require optimal functioning for an enhanced user experience. The proposal addresses the challenge of balancing service provision with sustainable treasury spending. It acknowledges the evolving role of light clients and the continued need for RPCs and bootnodes.

### **Proposed Strategy**

The procurement strategy aims to optimize quality of service, sustainable cost, decentralization, and simplicity. Key definitions, such as curators, independent RPC monitoring, system chains, and qualified RPC providers, are outlined. Quality of Service Reports and Service Agreements form essential components, with predefined standards and penalties for non-compliance.

### **Tender Submission and Evaluation**

A transparent process is proposed for RPC providers to submit tenders, with defined standards of service. Two potential options for tenders are presented: one focusing on cost targets and the other on predefined service levels. The curators, responsible for evaluation, scoring, and public announcement of selected providers, will ensure transparency and community involvement.

**Operations Phase**

RPC providers awarded service agreements are obligated to provide services throughout the six-month operations phase. Independent RPC monitoring will assess performance, and metrics will be made public. Providers will be paid monthly in arrears based on the EMA7 day average price of DOT/KSM.

### **Budget and Costings**

The proposed budget for the program is $400,000, providing a 12-month runway for assessment. Funding will be split between Polkadot and Kusama treasuries, with curator payments of $350 per month from the Polkadot portion. The budget accounts for potential quarterly expense variations based on traffic and evolving requirements.

**Read the [full proposal here.](https://docs.google.com/document/d/1GS4D95fkNjpi9GbXsiW7-9WOeGb30M5CYXEHXWsWRaw/edit)**

We are excited to share this proposal and are eager to hear your thoughts and feedback. Please feel free to comment, share your insights, and make suggestions to help refine this proposal further.

This proposal has been put forward by the following members of the RPC community:

[BlockOps](https://blockops.network/), [Dwellir](https://dwellir.com/), [LuckyFriday](https://luckyfriday.io/), [OnFinality](https://onfinality.io/), [RadiumBlock](https://radiumblock.com/), [RockX](https://www.rockx.com/), and [Stakeworld](https://stakeworld.io/).


### **Kusama Bounty**

This specific bounty is to cover the Kusama related chains. This bounty proposal also covers the costs for the stipends to the curators, and also the external monitoring.  EMA30 $26.164/KSM was used to calculate $132457.14 to 5,062.57 KSM.

- A group of companies (BlockOps, Dwellir, LuckyFriday, OnFinality, RadiumBlock, RockX, and Stakeworld) proposed a plan for better public RPC services in Polkadot and Kusama.
- RPC services are important for apps like Polkadot.JS and wallets to work well.
- The plan aims to make these services high-quality, decentralized, and affordable.
- There are two ways for RPC providers to apply: one focuses on cost, and the other on service quality.
- The budget is $400,000, split between Polkadot and Kusama treasuries.
- Providers will be monitored, and their performance will be shared publicly.
- The plan includes a 6-month operations phase where providers must meet service standards.
- Feedback and suggestions from the community are welcome to improve the proposal.

Bounty Proposal for Public RPCs for Relay and System Chains

This bounty is primarily designed to fund Collators on System Parachains with a fixed fiat monthly fee of US$300.00.  

Full details on the genesis of this bounty can be found [here](https://docs.google.com/document/d/1H2T1Nx90HkSAYF_CaOPLG-o3LS7h_QAa2WLDdcSJMs0/edit)

Details on monthly spends can be found [here](https://docs.google.com/spreadsheets/d/1XWGigL0t0FQI9fL4I3Wg_W9wgXV4fXYrmn6Bo2eRv9A/edit#gid=329443407)

System Parachains Collator Bounty

This bounty is the Program Milestone 2 inception of the Infrastructure Builders Program that can be found at the link below: https://docs.google.com/document/d/16USQYVhlyAlrU829EUB2TRoqUC0nnfoS\_uCdZ84HT8k

Infrastructure Builders Program

candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

closeBounty - no information about the proposal

Cleaning up erroneous(?) bounty 

- A new app is being proposed for the Kusama ecosystem.  
- It will notify Council members when they need to review or vote on important decisions.  
- The app will connect to the Kusama network and watch for specific events.  
- It will alert users when their input is needed, like for emergency actions.  
- The app can recognize special alerts from Council or Technical Committee members.  
- The goal is to improve participation and transparency in governance.  
- A bounty is being offered to develop this app.  
- Mario and Ana are suggested to help with the project.

Bounty Proposal: Kusama Council Alert App

- Mobile wallets need better security like desktop browsers.  
- Current tools like Subsocial and Kodadot work on mobile but aren’t as safe.  
- Web3Modal helps apps work with any wallet, which is good for both mobile and desktop.  
- Polkadot signing is simpler than Ethereum’s but needs more mobile-friendly options.  
- Ideas include remote signing, relayed signatures, or new tools.  
- Research suggests storing encrypted keys locally for better security.  
- A curator will pick the best mobile signing solution without needing extra apps.  
- Teams can propose ideas, and the best ones will get funding to improve.

@Polkadot/extension-inject on Mobile and/or walletconnect deeplinking equivalent 

While we already have a diverse field of mobile wallets in the ecosystem, they all attempt to be complete solutions, and we have a distinct lack of mobile equivalents to our browser extensions. Where we have solutions like Subsocial and Kodadot with mobile-ready UIs, users cannot use these applications with the same amount of security on mobile as they can on desktop, due to lack of an injected signer being available on mobile. In the longer term, the best-in-class mobile and desktop experiences come from toolkits like Web3Modal which allow developers to build experiences agnostic of the underlying signing solution used by a given user. While Polkadot Signing solutions are significantly lighter than Ethereum's - the signer doesn't require any connection to a node endpoint, the precedent is that the application provides that - it would still be interesting to explore the feasibility of remote signing solutions (portis), relayed signatures (walletconnect), and if the existing tools in the space may be reused, or if new tooling can be created within the scope of this bounty. One direction that is in research within the ecosystem that could lead to novel work deployed to Kusama and Polkadot is the concept of a page that stores encrypted keys in localstorage, with dapp developers loading it in an iframe and communicating with it for signatures - the idea being that the page that is loaded is specified by the user, based on their security model, up to and including a page that is hosted on localhost with a self-signed certificate as the most secure option, and a hosted wallet providing traditional username signup as the least secure option. REQUEST FOR CURATOR: The Curator for this proposal should be someone at least familiar with the equivalent ecosystem components in the Ethereum ecosystem - Mobile Wallets, (ie, Metamask mobile, Trust, etc) Walletconnect, Portis, and in general the Web3Modal ecosystem. And either the ability to independently verify the safety/veracity of proposals and teams applying for this bounty, or connections to individuals that can do so (who's verification work is to be funded by subbounty, presumably). It will be the Curator's primary responsibility to deliver a mobile-first signing solution, preferably an open standard, for Polkadot, preferably without requiring users to install an additional application on their devices so that it is platform agnostic, "as secure as possible". It should be clear that a Curator cannot directly be involved in the development of, or directly connected to the groups or individuals making proposals for, this bounty - although in this case knowledge of the ecosystem and relationships with the teams should probably be considered a positive factor in curators selection, so there will likely be a grey area between the two criteria. REQUEST FOR PROPOSALS: I'd be excited to see the aforementioned teams and projects extending their tools to Polkadot, but ideally any team that is capable of providing a solution that satisfies the curator selected for this bounty should apply. It is ultimately up to the curator to determine, but I would suggest using part of this bounty to fund several PoC sub-bounties that allow self-hosted solutions for app devs and users, and use the remainder to audit and polish the most promising solution(s) - Bounties can be extended via making treasury proposals to their address, and I will support increasing this bounty's funding after the first stage of PoCs

Mobile Signers / Injectors / Walletconnect equivalent 

- **Proposal:** A request to add sub-bounties to the bounty system.
- **Goal:** Allow curators to reward completed tasks without closing the main bounty.
- **Benefits:** 
  - Helps manage big projects better.
  - Makes it easier to track and use funds.
  - Lets projects grow step by step.
- **How it works:** Curators can create smaller tasks (sub-bounties) from an active bounty and reward them separately.
- **Suggested Curator:** Bryan Chen, who knows a lot about the bounty system.
- **Links:** More details and discussions can be found in the provided links.

Bounty Proposal: Sub-Bounties Extension Implementation

- Users can't see bounties on Apps right now.
- A new feature will let users see and use bounties.
- A bounty is offered to build a Bounty UI on Apps.
- Jaco Greeff is in charge of this bounty.
- The EthWorks team is working on it.
- The bounty includes designing and developing the UI.
- More details are in the bounty proposal.

Treasury Bounties