Mt Pelerin is a regulated Swiss company specialized in cryptocurrency exchange, mobile wallet and asset tokenization services.
PoC Required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Loss of user funds staked (principal) by freezing or theft
Data theft
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Execute arbitrary system commands
Retrieve sensitive data/files from a running server, such as:
- /etc/shadow
- database passwords
- blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)
Direct theft of user funds
A loss of funds involving an attack that does not require any user action
Private key or private key generation leakage leading to unauthorized access to user funds
Freezing of unclaimed yield
Temporary freezing of funds for any amount of time
Data deletion
Temporary freezing of funds
Out of scope
Important note on Bridge Protocol Bridge Protocol is deprecated. No new token will be deployed on it, and the only token in production on this protocol is MPS v2 on Gnosis Chain. Only impacts on MPS v2, as currently deployed and configured, are eligible. This means:
- Findings must be demonstrated with a PoC running on a fork of Gnosis Chain against the deployed MPS v2 contracts and their actual configuration. Local harnesses built from source, or setups where the researcher deploys or configures contracts themselves, will not be accepted as proof of impact.
- Findings related to token sales (TokenSale) are out of scope, as no token sale is planned on this protocol.
Additional out of scope information:
- Best practice critiques
- Attacks requiring privileged access from within the organization
- Bugs without proof-of-concept exploits showing impact
Smart Contract 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