Coreum
Bounty Range
$1,000 - $25,000
external program
Coreum
Coreum addresses the existing limitations of the current blockchains and empowers a solid foundation for future decentralized projects. Coreum's unique approach is to provide built-in, on-chain solutions to process transactions in a deterministic way to ensure a fast, secure, cheap, and green network for various use cases.
For more information about Coreum, please visit https://www.coreum.com/
Coreum provides rewards in COREUM.
Primacy of Impact vs Primacy of Rules
Coreum adheres to the Primacy of Impact for their entire program. If a category's severity level is covered within the Primacy of Impact, it means that even if the impacted asset is not in-scope but is owned by the project, then it would be considered as in-scope of the bug bounty program as long as it involves an impact under that respective severity level. When submitting a report, just select the Primacy of Impact asset placeholder. If the team behind this project has multiple projects, those other projects are not covered under the Primacy of Impact of this program. Instead, check if those other projects have a bug bounty program on Immunefi.
Testnet and mock files are not covered under the Primacy of Impact.
All other severity levels not listed here are considered under the Primacy of Rules, which means that they are bound by the terms of the bug bounty program.
Coreum provides rewards in COREUM, denominated in USD.
Blockchain/DLT
Reward amount is 10% of the funds directly affected, capped at the maximum critical reward of $25,000.
Minimum reward to discourage security researchers from withholding a bug report: $3,000
The reward is dependent on the ratio between the funds at risk, which includes all affected projects on top of the respective blockchain/DLT, and the market cap according to the average between CoinMarketCap.com and CoinGecko.com, calculated at the time the bug report is submitted.
Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table.
For critical Blockchain/DLT bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 25,000, but may also consider subsequent impacts on other projects built on the respective blockchain, as well as PR and brand reputation risk, capped at the maximum critical reward USD 25,000.
To incentivize security researchers and ensure bug reports are not withheld, a minimum reward USD 3,000 will be provided.
For Total Network Shutdown, the maximum payment of $25,000 will be rewarded.
If the blockchain/DLT component where the vulnerability exists can be upgraded/paused/killed, only the initial attacks within the first hour will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading, pausing, or in some cases, killing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk.
All other impacts that would be classified as Critical would be rewarded a flat amount of USD 3,000. The rest of the severity levels are paid out according to the Impact in Scope table.
Payouts are handled by the Coreum team directly and are denominated in USD. However, payments are done in COREUM.
The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability. For avoidance of doubt, if the reward amount is USD 5,000 and the average price is USD 1.75 per token, then the reward will be 2,857.142857 units of that token.
This bug bounty program will have a hard cap of USD 500,000. In the event that multiple bug reports are submitted that exceed this amount, the rewards will be provided on a first come first served basis.
Bug reports covering previously-discovered bugs acknowledged below are not eligible for any reward through the bug bounty program:
Coreum has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
A PoC is required for the following severity levels:
All PoCs submitted must comply with the Immunefi-wide PoC Guidelines and Rules. Bug report submissions without a PoC when a PoC is required will not be provided with a reward.
No KYC information is required for payout processing.
Category 3: Approval Required
Program's Custom Prohibited Activities:
Default Prohibited Activities:
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.
Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report:
Coreum has satisfied the requirements for the Immunefi Standard Badge, which is given to projects that adhere to best practices.