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…
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
If a user deploys a contract with an expiration > 60 days in the future, the deployment will fail, and eat up all their gas ;(
oraclize.it only allows us to schedule queries 60 days out, so current there is a check in the deployment [here](https://github.com/MARKETProtocol/MARKETProtocol/blob/ca06662259a6b1ce52a9f0a7374ad761db35d444/contracts/oraclize/MarketContractOraclize.sol#L75)
We need to add a validation of the expiration date to avoid people running into this issue
### Why Is this Needed?
[comment]: # (Describe the problem and why this task is needed. Provide description of the current state, what you would like to happen, and what actually happen)
*Summary*: To avoid a bad user experience and wasted gas!
[comment]: # (Feature or Bug? i.e Type: Bug)
### Current Behavior
[comment]: # (Describe what actually happened.)
No check for expiration beyond 60 days
### Expected Behavior
[comment]: # (Describe what you expected to happen.)
Check to ensure expiration is within 60 days before deploying
[comment]: # (Provide a summary of the solution and a task list on what needs to be fixed.)
*Summary*: Add checks on expiration variables
## Before you `start work`
If you have ongoing work from other bounties with us where funding has not been released, please do not pick up a new issue. We would like to involve as many contributors as possible and parallelize the work flow as much as possible.
Please also note that in order for work to be accepted, all code must be accompanied by test cases as well.