ERC20Distributor (Pancake Stable pool lisUSD/USDT)

ERC20Distributor (Thena slisBNB/BNB correlated)

ERC20Distributor (Thena lisUSD/FRAX stable)

ERC20Distributor (Thena lisUSD/USDT cl stable)

ERC20Distributor (Thena lisUSD/frxETH norrow)

ERC20Distributor (Thena lisUSD/frxETH wide)

ERC20Distributor (Thena lisUSD/BNB norrow)

ERC20Distributor (Thena LISTA/USDT norrow)

All smart contracts of Lista can be found at https://github.com/lista-dao/lista-dao-contracts, https://github.com/lista-dao/synclub-contracts and https://github.com/lista-dao/lista-token.
However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

For proxy contracts, both the current implementation and any further updates to the implementation contracts are considered in scope.

If an impact can be caused to any other asset managed by Lista that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.

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.

Theft of unclaimed yield

Temporary freezing of funds for a minimum period of 30 days

Injecting/modifying the static content on the target application without Javascript (Persistent) such as HTML injection without Javascript, replacing existing text with arbitrary text, arbitrary file uploads, etc.

Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as email or password of the victim, etc.

Improperly disclosing confidential user information such as email address, phone number, physical address, etc.

Subdomain takeover without already-connected wallet interaction

Smart contract unable to operate due to lack of funds

Unbounded gas consumption

Theft of gas

Redirecting users to malicious websites (open redirect)

Changing non-sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as changing the first/last name of user, or en/disabling notification

Injecting/modifying the static content on the target application without Javascript (Reflected) such as reflected HTML injection or loading external site data

Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Protocol insolvency

Taking down the application/website

Direct theft of user funds

Execute arbitrary system commands

Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)

Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as, changing registration information, commenting, voting, making trades, withdrawals, etc.

Subdomain takeover with already-connected wallet interaction

Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/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](https://drive.google.com/file/d/1A_iAbKkRyToXjFA25v8gLFfuSqFuIPEd/view?usp=sharing), [Peckshield security review](https://drive.google.com/file/d/1tyH5DAg0EE12TKOvucORw-kSsXpJFofu/view?usp=sharing), [Slowmist security review](https://drive.google.com/file/d/1ki1MrZcnkHReKuR5cMY40n2j-U9bnx25/view?usp=sharing), [Veridise security review](https://github.com/lista-dao/lista-dao-contracts/blob/master/audits/Veridise_270622.pdf) 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.