Want to earn some $JUNO and build reputation?
Welcome to Juno bounties.
To claim a bounty, first you should message the core team to express your interest in one of the bounties. If approved you can start working on it and when it's complete you can submit a PR to this repo and add your Juno address to the corresponding row in the table. A member of the core team will evaluate your claim, and if successful you'll be paid out the reward.
In addition, if you go above and beyond the call of duty, the reviewers may decide to offer a bonus.
Eligible GitHub repositories for Bug Bounties include:
- juno: the Juno blockchain source code.
- wasmd: the core smart contract module used by the Juno Blockchain.
- cw-plus: a library of contracts used by many Juno Projects.
Please confidentially report vulnerabilities to Meow Stargaze ✨🔭#1736 or dimi 🦙#2998 on the Juno Discord. Rewards will be determined based on the severity and whether or not a fix is provide.
Critical Vulnerability:
A critical vulnerability is something that would take down the chain, or cause the token to devalue in a serious manner.
Medium Vulnerability:
A medium vulnerability is something that could potentially disrupt the chain.
Low Vulnerability:
A low vulnerability is something that might slow down the chain or make it less efficient.
The bounties involve contribution to the Cosmos SDK. They will need to be implemented upstream and merged into junod.
| Task | Reward | Claimed by |
|---|---|---|
| Improve speed of Invariant checks | 10000 JUNO |
Recently during Cosmos SDK chain halts, invariant checks have taken over 10 hours to pass. The poor performance is largely because invariant checks are single threaded, and as chain state grows they take longer and longer. Invariant checks are important and should not be skipped as they verify the state integrity of the chain.
This bounty will involve improving the performance and speed of invariant checks. Potentially this could be done by doing invariant checks multi-threaded, but we will leave implementation up to those deciding to take on the bounty.
The minimum threshold is taking 25% off the unaltered invariant check time. i.e. if checks take 10 mins, your implementation saves 2min 30s.
The base reward is 10000 Juno.
We will be benchmarking solutions, and there will be significant bonuses for speeding invariant checks up past over 100% improvement (i.e. <5mins total elapsed time in the example above).
Any submission should be provided with sufficient evidence of a speedup, using the phoenix-2 genesis used to restart Juno in July e.g.:
- reproducible benchmark in a github repo
- a runnable example, hosted online
Ideally you will submit several proofs. Simply submitting logs or screenshots is not adequate.
The phoenix-2 genesis can be found here along with instructions for using it.
Due to the fact this will be shared openly, the first successful implementation that meets the criteria will take the bounty.
Teams or individuals that find further optimizations will be eligible for additional discretionary awards.
NOTE: to claim this bounty, your solution will need to be merged into the main Cosmos SDK repo and go through the review process there.
These challenges involve writing contracts. To claim, PRs must link to an open source repo.
One of the most exciting things about Juno smart contracts, is that they support the Inter-Blockchain Communication protocol (IBC) by default. So much is possible.
To claim these bounties, you must provide working open source code and successfully make transactions on mainnets of any of the networks specified.
Band protocol supports requesting oracle data over IBC. For this challenge, please implement a smart contract that demonstrates requesting oracle data over IBC. Be sure to demonstrate this working on Juno mainnet and provide adequate documentation for replication in the contract's README.md file.
| Task | Description | Reward | Claimed by |
|---|---|---|---|
| Request oracle data over IBC | Implement a contract to request oracle data over IBC. | 500 JUNO |
- Submissions are open source. By submitting a PR, you're agreeing to License your contribution under an Open Source license.
- Credit other people for their work.
- Some solutions may require iteration to be accepted.