MagpieXYZ
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.
PoC required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is % of the funds directly affected up to a maximum of:
$200,000Rewards 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.
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:
Payouts are handled by the MagpieXYZ team directly and are denominated in USD. However, payouts are done in USDC and BUSD.
Program Overview
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.
The platform offers users the opportunity to deposit their Stablecoins, BNB and Liquid BNB in single-sided boosted pools to earn high APR % while it allows Wombat Exchange voters to cost-effectively acquire voting power and earn passive income at the same time through the MGP token.
Magpie offers WOM holders the chance to earn high APR by converting their tokens into mWOM. mWOM refers to "Magpie WOM". mWOM can be staked on Magpie to earn boosted passive income.
When users convert their WOM tokens, they get mWOM that allows them to earn high rewards while Magpie locks all the converted WOM as veWOM on Wombat Exchange. That's how Magpie accumulates veWOM. veWOM entitles Magpie to boosted WOM rewards and governance benefits on Wombat Exchange. That's why Magpie can offer users sustainable boosted passive income.
For more information about MagpieXYZ, please visit https://www.magpiexyz.io/
KYC not required
No KYC information is required for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
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.