Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Ethical ads to power 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.
Follow the orgs you like more with tribes and build relationships and meaningful projects.
Meet the top hunters and contributors from our community.
Most people working with Ethereum have questions about ETH2.0. Kevin Owocki hosted some developers working on the project for a recent episode of the…
Sia recently ran the Skynet Hackathon with Gitcoin for Skynet’s launch, leading to over 40 project submissions in a 2 week period. This piece, …
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.
When running the tests on the `develop` branch using `truffle test`, one notices that there are 76 pending tests which have stubs (ie are described generally), but don't actually run anything. These stubs need to be filled in.
Go through the JS tests folder, and write the tests for all of the stubs. The tests already describe what exactly is being tested, and what the behaviour of the tests should be. For example, tests describing "should revert if..." are expecting the contract to revert when performing a particular action under a given set of circumstances. When writing these tests, you should look at the style and manner in which similar tests have been implemented. There are a number of actions which must occur for particular test to even be possible (for example a claimant must first be whitelisted before they may begin opening claims). For a detailed description of these various actions, please see [the whitepaper](https://docs.google.com/document/d/1CNBjz4oTUTQo2VjRh2jK0VBY5z7GAVPwT8YsVtOv1Ns/edit). If any questions arise about a particular action or test, please comment on this issue and we'll be happy to explain.
# Definition of Done
There should be 125 tests, which all run, and are all properly describing the case which is being tested (we'll look at every single test to make sure it actually **does** test what we ask for)
A correct submission will:
- have all 125 tests executing
- pass all linting requirements (this can be tested by running `npm run test` instead of `truffle test`, which runs the truffle tests along with the linter)
- have tests which accurately test the cases being described in the existing stubs
# Who Should Work On This Bounty
This bounty will require a considerable understanding of not only how to write truffle tests for solidity, but also a thorough understanding of how Delphi works. Reading the whitepaper through and through a couple times **is a prerequisite** before even submitting your intention to work on this bounty.