Lombard Finance
Bounty Range
$1,000 - $250,000
external program
Lombard Finance
Lombard is on a mission to unlock Bitcoin's potential as a dynamic financial tool by connecting it to DeFi with LBTC. LBTC is a secure Bitcoin LST, developed by Lombard on top of Babylon. It's a yield-bearing, natively cross-chain, liquid Bitcoin backed 1:1 by BTC. With LBTC, Bitcoin can be held as a store of value and simultaneously used to lend, borrow, stake, trade, and transfer in DeFi across multiple blockchain ecosystems.
Founded in April 2024, Lombard is dedicated to unlocking Bitcoin's potential as a dynamic financial tool by connecting it to DeFi. Lombard is building the universal standard for Bitcoin. Secured by Bitcoin-aligned ecosystem players, Lombard enables the yield-bearing BTC to move cross-chain without fragmenting liquidity, paving the way to become the single largest catalyst for onboarding net new capital into DeFi.
Bitcoin represents over 50% of the cryptocurrency market. But its interoperability with DeFi has been limited to date.
Our flagship product, LBTC—a yield-bearing, cross-chain, liquid Bitcoin backed 1:1 by BTC— changes this and brings DeFi interoperability to 'digital gold'. For the first time Bitcoin can be held as a store of value, and simultaneously used to earn, stake, trade, and transfer in DeFi at scale.
LBTC opens up new opportunities for Bitcoin holders to earn, stake, and trade on-chain, all while retaining Bitcoin as a store of value. For DeFi protocols, LBTC provides increased liquidity and user activity by unlocking $1.4 trillion new capital.
Lombard is currently live on Ethereum mainnet in Public Beta, where eligible participants are staking native BTC and minting LBTC.
For more information about Lombard, please visit https://www.lombard.finance/
Lombard Finance provides rewards in USDC on Ethereum, denominated in USD.
Smart Contract
Websites and Applications
Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $250,000. Minimum reward to discourage security researchers from withholding a bug report: $50,000
For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 250,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 50,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
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.
High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of $10,000 to $50,000 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.
For critical web/apps bug reports will be rewarded with USD 30,000, only if the impact leads to:
All other impacts that would be classified as Critical would be rewarded a flat amount of USD 15,000. The rest of the severity levels are paid out according to the Impact in Scope table.
Payouts are handled by the Lombard team directly and are denominated in USD. However, payments are done in USDC on Ethereum.
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.
Participants must adhere to the Eligibility Criteria.
Lombard will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
The submission of KYC information is a requirement for payout processing.
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.
Lombard adheres to the Primacy of Impact for the following impacts:
Primacy of Impact means that the impact is prioritized rather than a specific asset. This encourages security researchers to report on all bugs with an in-scope impact, even if the affected assets are not in scope.
When submitting a report on Immunefi's dashboard, the security researcher should select the Primacy of Impact asset placeholder. If the team behind this project has multiple programs, those other programs are not covered under Primacy of Impact for this program. Instead, check if those other projects have a bug bounty program on Immunefi.
If the project has any testnet and/or mock files, those will not be covered under Primacy of Impact.
All other impacts are considered under the Primacy of Rules, which means that they are bound by the terms and conditions set within this program.
Bug reports covering previously-discovered bugs (listed below) are not eligible for a reward within this program. This includes known issues that the project is aware of but has consciously decided not to "fix", necessary code changes, or any implemented operational mitigating procedures that can lessen potential risk.
Lombard's completed audit reports can be found at https://github.com/lombard-finance/evm-smart-contracts/tree/main/docs/audit. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
Category 3: Approval Required
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.