Shardeum is an EVM-based, linearly scalable network offering low gas fees forever while maintaining true decentralization and (hopefully) solid security. Shardeum is a large project and as such, will be split over two concurrent boosts. This boost, called Core III, will cover the Web3 aspects of the project. This will cover four components: Shardus Core Protocol, Shardeum Validator Nodes, networking libs, and Crypto-utils. For more information about Shardeum, please visit https://shardeum.org/
Evaluating
Triaged by Immunefi
PoC required
Vault program
This Audit Competition Is Under Evaluation
Immunefi vault program
Rewards
Rewards by Threat Level
The following reward terms are a summary, for the full details read our Shardeum Core III Reward Terms
The reward pool size is determined by the greatest condition met. If multiple conditions are met only the largest reward pool applies.
If one or more Critical severity bugs are found, the reward pool will be 100% of the respective reward pool, $250,000 USD If one or more High severity bugs are found, the reward pool will be 75% of the respective reward pool, $187,500 USD If one or more Medium severity bugs are found, the reward pool will be 50% of the respective reward pool, $125,000 USD Otherwise, the reward pool will be 25% of the respective reward pool, $62,500 USD
Duplicates and private known issues are valid for a reward.
Duplicates of Insight reports are not eligible for a reward. Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3..
Reward Payment Terms Payouts are handled by the Shardeum team directly and are denominated in USD. However, payments are done in USDC on Ethereum.
Insight Rewards Payment Terms Insight Rewards: Portion of the Rewards Pool The "Insight" severity was introduced on Audit Competition & Attackathon programs to recognize contributions that extend beyond identifying immediate vulnerabilities. Currently, it's not an option to select the Insight severity when submitting a report. However, our team or program will designate it accordingly if applicable. "Insights" underscores our commitment to valuing all types of contributions that contribute to a more secure environment and will always be rewarded. View more information about Insights.
Program Overview
This Audit Competition is running on testnet. The following conditions apply:
Shardeum team will freeze the codebase during the duration of the Audit Competition
- Duplicates are rewarded
- Shardeum provides rewards in USDC, denominated in USD.
Note:
Whitehats who need to run the network locally must submit their EVM address for whitelisting to receive test tokens from the project team in the Discord channel. Alternatively, you can DM the Shardeum Team for assistance.
Audits
Known Issues
KYC not required
No KYC information is required for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- Any testing with pricing oracles or third-party smart contracts
- Attempting phishing or other social engineering attacks against our employees and/or customers
- Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
- Any denial of service attacks that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Any other actions prohibited by the Immunefi Rules
Feasibility Limitations
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.