---
# System prepended metadata

title: Bounty dapp idea

---

# Bounty app idea


It's incredibly cumbersome to manage payments and paper work as a multisig entity &mdash; to run and crosscheck balance sheets, submit post-event spending reports and stay on track about everything. We should have one place to make it easier to do this simple task.

---

## Problem: 

Paying people and managing post-event follow-ups is a big pain for hackathon managers today in web3. In turn, people get upset when they aren't paid in time which sets a bad precedent for hackathon organizers.

**A little more on the problem as I've experienced it:**

* We're still using spreadsheets, estimating the market price, jumping from address submitted by email to a dedicated multisig dapp and linking back to Google drives for expense proofs. It's a lot of unessecary steps to achieve something that should be straightforward.
* To do multiple calls (for e.g. you need to pay 10 different addresses different amounts) you need to construct a utility.batch call using Polkadot JS then submit the call to the multisig, typically a different dapp (e.g. Multix). This UX is not intuitive and could be done in one step instead of needing to switch tabs.
* It takes time to do all this stuff. And it could be streamlined.
* Reimbursing any leftover DOT is a pain. I have to go to the spreadsheet, do all the calculations there and submit the transaction for the reimbursed amount. Then paste the transaction proof into the report.
* When processing payments, you always need to take the current price of DOT and if its less then you need to account for it. That means two things: 1. The exchange rate is taken from an external source which is always approximate and the payment is never made in real time; 2.  You need to justify the spending to reimburse whatever is left over typically using spreadsheet that links to the reimbursement payment. Headache.

## Idea

Have tool for event managers primarily. Make it easier to submit payments to bounty winners (e.g. from hackathons) and team members (e.g. salaries) as a first step. Then, grow the dapp into something that puts the onus on whoever needs to claim a payment to a multisig account. 

They submit a call to request their payment and the multisig just needs to approve it. That way, all the curators need to do is verify transactions. This could work for paying salaries, paying out bounties and expenses.

The idea is to have a dapp with a "claim" view and "event manager" view. 

**1. For claimants:** allows anyone to claim a payment. The app handles the price and conversion (for e.g. if the reward is $100 dollars you can chose DOT or USDC). And submits a request of approval to the multisig. 

**2. For event managers:** Manager view can see all the pending transactions to be approved. They can also create a spreadsheet out of them once they're approved. Managers can also submit payments from the multisig. They can also easily construct batch calls in one click. 

## Opportunity

A common-good / public good app that anyone can use for their bounty payout management systems, first built for Polkadot.

License: MIT License