Maya Protocol
Maya Protocol is a decentralized multi-chain liquidity protocol built as a fork of THORChain, providing seamless cross-chain asset exchanges while maintaining transparency and security. It utilizes Cosmos-SDK, Tendermint, and Threshold Signature Schemes (TSS) to ensure a robust and reliable platform. With a unique Liquidity Auction design and a dual-token model ($CACAO and $MAYA), the protocol ensures fair distribution and encourages user participation.
PoC required
Rewards
Rewards by Threat Level
Reward amount is 10% of the funds directly affected, capped at the maximum critical reward of:
$35,000Please review how rewards are distributed based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale system with separate scales for Smart Contracts and Websites/Apps.
Payouts and Payout Requirements:
Payouts are handled by the Maya Protocol team directly and are denominated in USD. However, payouts are done in USDC and USDT. Whitehats also have a choice to get paid in BTC, RUNE, CACAO, and/or MAYA. Maya Protocol commits to honoring payouts according to the terms set out in this program at the time of report submission, and to treat this program as the agreement and source of truth concerning bug reports and responsible disclosures.
For the purposes of determining report validity, this is a Primacy of Rules program.
Learn more about report validity best practices here: Best Practice - Primacy of Impact vs Primacy of Rules.
KYC Requirements:
Maya Protocol does not have a Know Your Customer (KYC) requirement for bug bounty payouts.
Audit Discoveries and Known Issues:
Bug reports covering previously-discovered bugs are not eligible for any reward through the bug bounty program. If a bug report covers a known issue, it may be rejected together with proof of the issue being known before escalation of the bug report via Immunefi.
Previous audits and known issues can be found at:
Program Overview
Maya Protocol is a decentralized multi-chain liquidity protocol built as a fork of THORChain, providing seamless cross-chain asset exchanges while maintaining transparency and security. It utilizes Cosmos-SDK, Tendermint, and Threshold Signature Schemes (TSS) to ensure a robust and reliable platform. With a unique Liquidity Auction design and a dual-token model ($CACAO and $MAYA), the protocol ensures fair distribution and encourages user participation.
Maya Protocol leverages an innovative approach to node operations, combining bonded $CACAO tokens with other native assets in liquidity pools to maximize capital efficiency and security. This design allows node operators to earn both Liquidity Provider rewards and Validator Rewards, making the protocol more attractive for user engagement and investment.
This program covers the protocol's core functionality, and other critical aspects, focusing on receiving bug reports for vulnerabilities with potentially significant impacts on users and the system.
For more information about how Maya Protocol works, please visit https://docs.mayaprotocol.com
We are an open-source, community-driven protocol with a 100% fair launch where all tokens were distributed to the community under equal terms. This transparent and equitable approach to token distribution reflects our commitment to true decentralization and community ownership
For Whitehats: It is highly recommended that you review the details of this program in full. Although many Bug Bounty programs have standard terms and conditions, each also has their own unique details that are critical to your success.
Prior to submitting a report please review the Immunefi Bug Report Template and Best Practices.
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
- The following activities are prohibited by this bug bounty program. Violation of these rules can result in a temporary suspension or permanent ban from the Immunefi platform at the sole discretion of the Immunefi team, which may also result in: 1) the forfeiture and loss of access to all bug submissions, and 2) zero payout.
- Please note that Immunefi has no tolerance for spam/low-quality/incomplete bug reports, “beg bounty” behavior, and misrepresentation of assets and severity. Immunefi exists to protect the global crypto community, not facilitate grift.
- 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.