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.
right now, we don't do a great job of bounds checking in the follow places :
## surface area:
1. kill bounty
2. submit bounty
3. accept bounty
if you fail to meet the boundary conditions , youll see a nasty metamask module that shows you using up too much gas : http://bits.owocki.com/0h1R3J3r1j1w
# current functionality
upon form submission on these pages, metamask will show this module, which shows that theres too much gas being used: http://bits.owocki.com/0h1R3J3r1j1w
# desired functionality
upon form submission on these pages, an `_alert` is shown telling the user what bounds they crossed (the most common one is likely to be that the bounty has expired)
example error message: "Error: Cannot submit bounty as it has expired. Please contact bounty submitter directly to resolve."
# bounds conditions to check
1. try to submit work on an issue you are the funder
2. you submit work on an issue that is on a different network than you (mainnet vs rinkeby)
3. any other conditions enforced in [StandardBounties](https://github.com/ConsenSys/StandardBounties/)
4. network of bounty != network that the users current metamask instance is on