Triaged by Immunefi
Step-by-step PoC Required
This Audit Competition Is Live!
$15,000 USD in rewards is available for finding bugs on Firelight's contracts.
For more information about the project, please visit about Firelight
-
KYC is not required.
-
Flat Reward Pool
Proof of Concept (PoC) Requirements
-
A runnable PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.
-
Any technical questions and support requests can be asked directly to the Firelight team or Immunefi in the #firelight-audit-competition discord channel.
Rewards
Rewards by Threat Level
Rewards are distributed among SRs according to Immunefi’s Standardized Competition Reward Terms and includes All Star Pool and Podium Pool reserved for All Star Program participants.
Rewards are denominated in USD and distributed in USDC on Ethereum.
The reward pool is $15,000 for any bug found. That means that even if 1lLow severity bug is found, the whole reward pool is unlocked and has to be fully distributed between security researchers.
If not a single bug is found (Insights do not count as bugs) the reward pool is $2,250 of Max SR Rewards.
Program Overview
The Firelight Vault is an upgradeable ERC‑4626 compatible vault with additional features.
Audits
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.