All smart contracts of MagpieXYZ can be found at [https://github.com/magpiexyz/contracts](https://github.com/magpiexyz/contracts). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If an Critical and High impact can be caused to any other asset managed by MagpieXYZ 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. 

Magpie is a BNB Chain native yield boosting platform that maximizes governance benefits for veTokenomics based protocols. Incubated by Wombat Exchange, Magpie is focused on locking WOM tokens to own governance rights and boosted yield benefits as liquidity provider on Wombat. 

Any governance voting result manipulation

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

Permanent freezing of funds

Protocol Insolvency

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Temporary freezing of funds for at least 24 hours

Smart contract unable to operate due to lack of token funds (vulnerabilities purely relying on the project neglecting to top up funds in their smart contracts are out of scope)

Block stuffing for profit

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Theft of gas

Unbounded gas consumption

Smart contract fails to deliver promised returns, but doesn’t lose value

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. 

All Critical Smart Contract 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.  In addition, all Critical severity bug reports must come with a suggestion for a fix in order to be considered for a reward. 

Rewards for critical smart contract vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum reward of __USD 50 000__ for Critical smart contract bug reports. 

Rewards for high smart contract vulnerabilities are further capped at 20% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum reward of __USD 5 000__ for High smart contract bug reports.

Known issues highlighted in the following audit reports are considered out of scope: 
- [https://docs.magpiexyz.io/security/audit-reports](https://docs.magpiexyz.io/security/audit-reports)

Payouts are handled by the __MagpieXYZ__ team directly and are denominated in USD. However, payouts are done in __USDC__ and __BUSD__.


MagpieXYZ

Resources & Documentation