Radiant
Radiant Capital is the first omnichain money market atop LayerZero, where users can deposit and borrow a variety of supported assets across multiple chains, seamlessly.
Triaged by Immunefi
PoC required
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
For the purposes of determining report validity, this is a Primacy of Impact program. Learn more about report validity best practices here: Best Practice - Primacy of Impact vs Primacy of Rules.
All smart contract and web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.
Rewards for critical smart contract vulnerabilities are further capped at 10% of the funds at risk. In cases of repeatable attacks, only the first attack is considered unless the smart contract cannot be upgraded or paused. However, there is a minimum reward of USD 20 000 for Critical smart contract bug reports.
Rewards for high smart contract vulnerabilities are further capped at 100% of the funds at risk. In cases of repeatable attacks, only the first attack is considered unless the smart contract cannot be upgraded or paused. However, there is a minimum reward of USD 5 000 for High smart contract bug reports.
Rewards for medium smart contract vulnerabilities with direct monetary impact are further capped at 100% of the funds at risk. In cases of repeatable attacks, only the first attack is considered unless the smart contract cannot be upgraded or paused. However, there is a minimum reward of USD 1 000 for Medium smart contract bug reports.
All other valid low smart contract bug reports will be rewarded USD 1 000.
Known issues highlighted in the following audit reports are considered out of scope:
- https://blog.openzeppelin.com/radiant
- https://github.com/peckshield/publications/tree/master/audit_reports/PeckShield-Audit-Report-RadiantV2-v1.0.pdf
- https://twitter.com/zokyo_io/status/1638856299629907973
- https://github.com/blocksecteam/audit-reports/blob/main/solidity/blocksec_radiant_v2.0.pdf
Payouts are handled by the Radiant team directly and are denominated in USD. However, payouts are done in USDC.
Program Overview
Radiant Capital is the first omnichain money market atop LayerZero, where users can deposit and borrow a variety of supported assets across multiple chains, seamlessly.
$RDNT, an OFT-20, is Radiant's native utility token. Layer Zero Labs’ omnichain fungible token (OFT) interoperability solution enables native, cross-chain token transfers. With LayerZero’s guarantee of valid delivery, the token is burned on the source chain and minted on the destination chain directly through the token contract.
Ecosystem participants can lock Radiant liquidity tokens to receive a share of protocol revenue from borrowers’ loan repayments in the form of a variety of blue chip assets. Locking RDNT liquidity also activates the ability to earn $RDNT emissions from borrowing and lending within the money market, as well as rights to vote in governance on the future direction of the protocol.
For more information about Radiant, please visit radiant.capital
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.
199.5k