Attackathon | XRPL Lending Protocol
The XRP Ledger (XRPL) is a decentralized layer 1 blockchain renowned for its decade-long reliability and stability in tokenizing and exchanging crypto-native and real-world assets.
The XLS-66 specification introduces the XRP Ledger-native Lending Protocol, which facilitates straightforward, on-chain, uncollateralised fixed-term loans with pre-set interest terms. Loan liquidity is sourced from pooled funds, while the design relies on off-chain underwriting and risk management to assess borrowers’ creditworthiness.
Live
Triaged by Immunefi
Step-by-step PoC Required
KYC required
This Attackathon Is Live!
A Flat $200,000 USD reward pool for finding bugs on XRPL Lending Protocol.
You can ask technical questions to the XRPL's Team directly in the #xrpl-attackathon channel in Immunefi's Discord.
When the XRPL Lending Protocol Attackathon ends, Immunefi will publish a leaderboard and Attackathon findings report.
Rewards
Rewards by Threat Level
Reward Terms
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 RLUSD on Ethereum.
Flat Rewards
The reward pool is $200,000 USD if any bug is found. That means that even if 1 Low severity bug is found, the whole reward pool is unlocked and will be fully distributed between security researchers.
If not a single bug is found (Insights do not count as bugs) the reward pool is $30,000 USD.
Private known issues, meaning known issues that were not publicly disclosed, are valid and unlock the corresponding reward pool.
Code of the assets in scope is frozen while the program is live.
Duplicate submissions of bugs are valid. Duplicate submissions of Insights are invalid.
The project commits to keeping private all info related to bug findings until this program is over. This means the project will not leak info about any bug findings or planned bug fixes, including bug findings found independently by the project or from concurrent private audits.
Insight Rewards Payment Terms
Insight Rewards: Portion of the Rewards Pool
The "Insight" severity was introduced on Audit Competitions & Attackathon programs to recognize contributions that extend beyond identifying immediate vulnerabilities. "Insights" underscores our commitment to valuing all types of contributions that contribute to a more secure environment. View more information about Insights
Duplicates of Insight reports are not eligible for a reward.
Proof of Concept (PoC) Requirements
A runnable PoC is required. For more information, please read Immunefi Proof of Concept (PoC) Guidelines and Rules
Program Overview
The XRP Ledger (XRPL) is a decentralized layer 1 blockchain renowned for its decade-long reliability and stability in tokenizing and exchanging crypto-native and real-world assets.
The XLS-66 specification introduces the XRP Ledger-native Lending Protocol, which facilitates straightforward, on-chain, uncollateralised fixed-term loans with pre-set interest terms. Loan liquidity is sourced from pooled funds, while the design relies on off-chain underwriting and risk management to assess borrowers’ creditworthiness.
For more information about the XRPL, please visit https://xrpl.org/
For more information about Ripple, please visit https://ripple.com/
Audits
Known Issues
KYC required
The submission of KYC information is a requirement 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.