Merchant Moe is the cornerstone DEX for Mantle Network, offering seamless trading, discretized liquidity, and real yield all within his intuitive and easy-to-navigate platform. Built with the same robust technology as LFJ Dex, Merchant Moe is a distinct and purpose-built native DEX for the Mantle Network, with unique features and offerings tailored specifically to serve the Mantle Ecosystem.
Vulnerabilities discovered in code shared between LFJ and Merchant Moe may only be submitted to one bug bounty program. Duplicate submissions to both programs for the same underlying issue will be rejected.
Runnable PoC Required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$100,000Minimum reward to discourage security researchers from withholding a bug report:
$10,000Reward Calculation for Critical Level Reports For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 100,000 . The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 1,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
Repeatable Attack Limitations
If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward.
The amount of funds at risk will be calculated with the impact of the first attack being at 100% and then a reduction of 25% from the amount of the first attack for every [300 blocks] the attack needs for subsequent attacks from the first attack, rounded down.
Reward Calculation for High Level Reports High impacts concerning theft/permanent freezing of unclaimed yield/royalties are rewarded with a range of MIN to USD 100,000 with the reward calculated based on 100% of the funds at risk, though capped at the maximum high reward.
In the event of temporary freezing, the reward doubles from the full frozen vallue for every additional 24h that the funds are temporarily frozen, up until a max cap of the high reward.
Program Overview
Merchant Moe is the cornerstone DEX for Mantle Network, offering seamless trading, discretized liquidity, and real yield all within his intuitive and easy-to-navigate platform. Built with the same robust technology as LFJ Dex, Merchant Moe is a distinct and purpose-built native DEX for the Mantle Network, with unique features and offerings tailored specifically to serve the Mantle Ecosystem.
Vulnerabilities discovered in code shared between LFJ and Merchant Moe may only be submitted to one bug bounty program. Duplicate submissions to both programs for the same underlying issue will be rejected.
Responsible Publication
Merchant Moe adheres to Category 3: Approval Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.
Primacy of Impact vs Primacy of Rules
Merchant Moe adheres to the Primacy of Impact for the following impacts:
- Smart Contract - High
- Smart Contract - Critical
- Smart Contract - Medium
- Smart Contract - Low
Primacy of Impact means that the impact is prioritized rather than a specific asset. This encourages security researchers to report on all bugs with an in-scope impact, even if the affected assets are not in scope.
For more information, please see Best Practices: Primacy of Impact
When submitting a report on Immunefi’s dashboard, the security researcher should select the Primacy of Impact asset placeholder. If the team behind this project has multiple programs, those other programs are not covered under Primacy of Impact for this program. Instead, check if those other projects have a bug bounty program on Immunefi.
If the project has any testnet and/or mock files, those will not be covered under Primacy of Impact.
Proof of Concept (PoC) Requirements
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.
Previous Audits Merchant Moe's completed audit reports can be found here:
Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
Audits
KYC not required
No KYC information is required for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
Responsible Publication
Category 3: Approval Required
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.