Nucleus
Bounty Range
$1,000 - $500,000
external program
Nucleus
Nucleus is the default yield provider for networks. Nucleus stands to revolutionize the way users interact with networks by removing the opportunity costs of exploring new ecosystems via embedding yield for all users at the network layer.
Nucleus enables networks to create a new yield generating primitive at the base of a network's ecosystem. Users are able to generate yield by default on a wide variety of assets by bridging supported assets to the network. These assets will allow users to earn more while exploring all of the unique applications in the network's ecosystem.
Nucleus's mission is to enable yield by default in every network in the crypto ecosystem to further empower the builders, users, and infrastructure within them.
From a security perspective, the contracts are different from traditional vault standards in that it combines offchain actors with on-chain constraints—giving offchain entities specific permissions to maintain exchange rates and to manage the vaults' liquidity—allowing the vault to operate with more compute and maintain state across multiple chains while safeguarding the depositors from malicious behavior. This design decision can be found throughout the codebase.
Smart Contract
Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $500,000.
Minimum reward to discourage security researchers from withholding a bug report: $25,000
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
Reward Calculation for Critical Level Reports
For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD $500,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD $25,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
Repeatable Attack Limitations
If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk.
For critical repeatable attacks on smart contracts that cannot be upgraded or paused, the project will consider the cumulative impact of the repeatable attacks for a reward. This is because the project cannot prevent the attacker from repeatedly exploiting the vulnerability until all funds are drained and/or other irreversible damage is done. Therefore, this warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward.
Reward Calculation for High Level Reports
High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of minimum high to maximum high depending on the funds at risk, capped at the maximum high reward.
In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24h that the funds are temporarily frozen, up until a max cap of the high reward. This is because as the duration of the freezing lengthens, the potential for greater damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures stronger incentives for bug disclosure of this nature.
Reward Payment Terms
Payouts are handled by the Nucleus team directly and are denominated in USD. However, payments are done in USDC on ETH.
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.
Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:
Nucleus adheres to category 3 - Approval Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports.
Nucleus adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms and conditions stated within this page.
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.
Proof of concept is always required for all severities.
Nucleus's completed audit reports can be found at https://docs.nucleusearn.io/security/audits. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
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.
By adhering to Immunefi's best practice recommendations, Nucleus has satisfied the requirements for the Immunefi Standard Badge.
No KYC information is required for payout processing.