Audit Comp | Shardeum: Ancillaries-logo

Audit Comp | Shardeum: Ancillaries

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 audit competitions. This audit competition, called Ancillaries, will cover the Web2 aspects of the project.

Shardeum
Infrastructure
Services
Rust
Typescript

Status

Finished
Rewards Pool
$200,000
Vault TVL
$0.01
Started
08 July 2024
Ended
14 August 2024
Rewards Token
USDC
nSLOC
55,472
  • Triaged by Immunefi

  • PoC required

  • Vault program

This Audit Competition Is Over

Audit Competition cards for security researchers with paid reports are available here.

All paid bug reports are available in original format here.

Started
08 July 2024 06:00 UTC
Ended
14 August 2024 06:00 UTC

VaultImmunefi vault program

Funds available

$0.01

30d Avg. Funds availability

$0.01

Assets in vault

  • 0.01  USDC

Public vault address

0xf6BBA894B4C8B2F918d2c6dD8E78Ba87655b52E4

Rewards

Audit Comp | Shardeum: Ancillaries provides rewards in USDC on Ethereum, denominated in USD.

Rewards by Threat Level

Websites and Applications
Critical
Portion of the Reward Pool
High
Portion of the Reward Pool
Medium
Portion of the Reward Pool
Low
Portion of the Reward Pool

The following reward terms are a summary, for the full details read our Shardeum | Ancillaries 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 $100,000 USD
  • If one or more High severity bugs are found the reward pool will be $120,000 USD
  • If 1 Critical severity bug is found the reward pool will be $160,000 USD
  • If 2 Critical severity bugs are found the reward pool will be $180,000 USD
  • If 4 or more Critical severity bugs are found the reward pool will be $200,000 USD

For this Audit Competition, 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 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

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 audit competitions. This audit competition, called Ancillaries, will cover the Web2 aspects of the project. This will cover seven components: Validator Gui, Validator CLI, Archiver, Explorer, Distrubutor/Collector libraries, RPC, and Shardus-Net networking code.

The Validator GUI is the website that optionally runs on each node. This allows the node operator to interact with their node. Despite our best efforts, the community likes to have this webpage available on the internet. The Validator CLI is the command line tool used to administer the node. The GUI calls commands in the CLI, or the operator can enter the commands manually. The Archive Server’s primary role is to hold the historical state of the network and accounts.Once the network has consensed on a state change, that information is saved to archive servers. The Explorer serves a similar function to https://etherscan.io/. The relayer consists of two parts: collector and distributor. These two components work together to shuffle data between ancillaries, namely the archiver servers, RPC servers, and explorer. The RPC server acts as an API, allowing users to interact with the network and inject transactions. It is designed to be as compliant as possible with Ethereum’s RPC specification, though some differences exist. Finally, lib-net is the bottom level networking library for the Shardeum network. It is written in a mix of Rust and TypeScript.

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.

Proof of Concept

Proof of concept is always required for all severities.

Prohibited Activities

Default 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.

30d Avg. Funds Availability
$0.01
Total Assets in Scope
8