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
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct loss of funds
Unintended chain split (network partition)
Transient consensus failures
Permanent freezing of funds (fix requires hardfork)
Network not being able to confirm new transactions (Total network shutdown)
Unintended permanent chain split requiring hard fork (Network partition requiring hard fork)
Out of scope
- Broken link hijacking is out of scope
- Attacks that are covered by Thorchain either in a future version or that are currently reviewing privately
- No double-dipping
Blockchain/DLT specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers