However, only those in the table are considered as in-scope of the bug bounty program. 

All following known issues, as well as those in past audit reports [https://docs.tokemak.xyz/protocol-information/network-security](https://docs.tokemak.xyz/protocol-information/network-security), are considered out-of-scope of this bug bounty program:
  - Centralized backend entity
  - For loop not capped, can have excessive gas consumption
  - Different Solidity versions
  - ERC20 allowance double spend exploit
  - Unsafe cycle durations
  - Possibility of sandwich attacks during liquidity deployments
  - Schedule.setup check in the Staking contract always passes it

If an impact can be caused to any other asset managed by Tokemak 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. This only applies to Critical impacts.

For further reference, the relevant GitHub can be found at [https://github.com/Tokemak/contracts-v1/tree/main](https://github.com/Tokemak/contracts-v1/tree/main). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program. 


Tokemak is a decentralized liquidity providing/market making protocol designed to create efficient, sustainable liquidity across DeFi.

Direct theft or permanent freezing of staked funds in Tokemak contracts

Redirected funds by address modification

Users spoofing other users leading to loss of user funds

Theft of unclaimed yield

Freezing of staked funds in Tokemak contracts for more than 10 minutes

Freezing of unclaimed yield for a period of more than 10 minutes

Vote manipulation

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 and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

All bug reports are required to come with a PoC. A suggestion for a fix is also required for all severity levels. 

Critical smart contract vulnerabilities are further capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and marketing considerations, at the discretion of the team. However, there is a minimum reward of __USD 50 000__. Rewards for critical smart contract bugs have the potential to be paid out over time at $50k USD value per month.

All 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. Smart contracts bug reports are required to include a runnable PoC in order to prove impact. Exceptions may be made in cases where the vulnerability is objectively evident from simply mentioning the vulnerability and where it exists. However, the bug reporter may be required to provide a PoC at any point in time.

Attacks caused by rebase tokens, fee-on-transfer tokens or non-standard ERC20 tokens are out of scope unless a reactor has been created for that token by Tokemak and configured for deployment.

Attacks caused by data conditions that require privileged access to a contract to set, but are not already in a current and deployed version of the contract are capped at a Medium payout level.

Any vote manipulations are considered at max a High vulnerability.

Payouts are handled by the __Tokemak__ team directly and are denominated in USD. However, payouts are done in __ETH__, __TOKE__, or stablecoins, at the discretion of the team.

Tokemak

Resources & Documentation