Boost | Shardeum: Core
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, will cover the Web3 aspects of the project, as well as some internal libs. This will cover three components: Shardus Core, Shardeum Validator, and Crypto Utils library.
Live
Triaged by Immunefi
PoC required
This Boost Is Live!
$500,000 USD is available in rewards for finding bugs in Shardeum's codebase of about 70000 nSLOC. There is no KYC required.
Shardeum team will respond within 24 hours on weekdays to all bug reports. Any technical questions and support requests can be asked directly to Shardeum or Immunefi in the Shardeum Boost Discord channel.
In this contest bug fixes may be applied mid-contest. Further details are in the 'Assets In Scope' section.
When the Boost has ended Immunefi will publish an event-specific leaderboard and bug reports from the event.
Rewards by Threat Level
The following reward terms are a summary, for the full details read our Shardeum | Core Reward Distribution Terms.
The reward pool will be distributed among participants. The size depends on the bugs found:
- If no High or Critical severity bugs are found the reward pool will be $250,000 USD
- If one or more High severity bugs are found the reward pool will be $300,000 USD
- If 1 Critical severity bug is found the reward pool will be $400,000 USD
- If 2 Critical severity bugs are found the reward pool will be $450,000 USD
- If 4 or more Critical severity bugs are found the reward pool will be $500,000 USD
For this Boost, duplicates and private known issues are valid for a reward.
Private known issues will unlock higher reward pools according to their severity level without any downgrade. For example, a Critical severity bug which was a private known issue would unlock the reward pool conditional on a Critical severity bug being found.
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.
Rewards will be distributed all at once based on Immunefi’s distribution formula after the event has concluded and the final bug reports have been resolved.
Insight Rewards Payment Terms
Insight Rewards: Portion of the Rewards Pool
The "Insight" severity was introduced on Boost & 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
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, will cover the Web3 aspects of the project, as well as some internal libs. This will cover three components: Shardus Core, Shardeum Validator, and Crypto Utils library.
Shardus Core covers the Layer 1, p2p and consensus protocol. Shardeum Validator is the L2 EVM-compatible distributed application (DApp). Everything here except smart contracts is in scope. Finally, the crypto utils library holds wrappers for cryptographic functions used throughout the Shardeum Foundation codebase.
For more information about Shardeum, please visit https://shardeum.org/.
Shardeum provides rewards in USDC, denominated in USD.
KYC not required
No KYC information is required for payout processing.
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.