Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
In partnership with Protocol Labs, we’re excited to welcome builders from everywhere to APOLLO, your mission control to engage with the builder…
We’re excited to publically announce that Matic Network is partnering with Gitcoin to launch the Build-n-Earn Program – assisting dApps t…
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
### User Story
As an admin, I want to be notified if a funder funds a bounty with an extremely low price because setting reasonable and fair hourly rates is one of many ways that OSS is sustained.
### Why Is this Needed
OSS sustainability is only possible if we pay developers a fair price for the value they put forth. Certain prices (e.g < $1) for any type of task is considered lowballing the developer / bounty hunter. Warning Gitcoin admins of an extremely low bounty price and giving the admins the option to manually follow up with the funder is necessary to prevent publishing of lowball bounties.
### Current Behavior
Currently, there are no warnings or emails triggered when a bounty is funded below a certain threshold.
### Expected Behavior
An email is automatically sent to Gitcoin administrators when a bounty is funded that is below $X.
### Definition of Done
1. When a funder hits "submit an issue," a threshold check (if else logic) on the bounty value is performed.
2. If the bounty value is below the threshold, an automatic email to Gitcoin admins is triggered with the issue link, funder, and funder information.
3. Being below a $X threshold should not prevent the bounty from being published, but an automatic email should be triggered.