Lista DAO
Lista DAO, powered by the BNB Smart Chain, introduces an innovative integration of Liquid Staking and Staking services. Lista DAO's native CDP stablecoin is known as lisUSD, and it is over-collateralized against a variety of tokens such as BNB, ETH, wBETH and slisBNB.
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.
Reward calculation of Critical bug reports
For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 1 000 000 USD, however there is a minimum of USD 100 000
Reward calculation of High bug reports
High severity vulnerabilities concerning theft of unclaimed yield, permanent freezing of unclaimed yield, and temporary freezing of funds for a minimum period of 30 days are considered at the full amount of funds at risk, capped at the maximum high reward. This is to incentivize security researchers to uncover and responsibly disclose vulnerabilities that may have not have significant monetary value today, but could still be damaging to the project if it goes unaddressed.
All vulnerabilities marked in the Certik security review, Peckshield security review, Slowmist security review, Veridise security review and https://github.com/lista-dao/synclub-contracts/tree/master/audit and https://github.com/lista-dao/lista-dao-contracts/tree/master/audits are not eligible for a reward.
All rewards for the Lista bug bounty program are scaled based on an internally established team criteria, taking into account the exploitability of the bug, the impact it causes, and the likelihood of the vulnerability presenting itself, which is especially factored in with bug reports requiring multiple conditions to be met that are currently not in-place. However, there is a minimum reward of USD 1,000 for each severity level, rewards will be provided at the determined fair value by the team depending on these conditions, assuming that the bug report is in-scope of the bug bounty program.
Payouts are handled by the Lista team directly and are denominated in USD. However, payouts are done in USDT, USDC and lisUSD, with the choice of the ratio at the discretion of the team.
Program Overview
Lista DAO, powered by the BNB Smart Chain, introduces an innovative integration of Liquid Staking and Staking services. Lista DAO's native CDP stablecoin is known as lisUSD, and it is over-collateralized against a variety of tokens such as BNB, ETH, wBETH and slisBNB. Upon borrowing lisUSD, users can opt to stake their holdings for long-term yield on affiliated partner DEXes, engage in trading activities, or utilize lisUSD as a form of monetary payment.
Lista DAO also offers simple and secure liquid staking solutions on the BNB Smart Chain, with users minting Lista Staked BNB, slisBNB, in exchange for staking their BNB. The staked BNB is held securely on BSC validator nodes providing attractive liquid staking yields on their staked BNB.
KYC not required
No KYC information is required for payout processing.
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.