GMXTrade is a decentralized leveraged trading platform built on the Solana blockchain, drawing inspiration from the technical innovations introduced by GMX V2. The platform aims to provide a seamless trading experience with fast transaction times and low fees, while maintaining security and decentralization.
Runnable PoC Required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Protocol insolvency
Theft of unclaimed yield
Permanent freezing of unclaimed yield
Temporary freezing of funds
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Unbounded gas consumption
Out of scope
Known Issues Bug reports covering previously-discovered bugs (listed below) are not eligible for a reward within this program. This includes known issues that the project is aware of but has consciously decided not to “fix”, necessary code changes, or any implemented operational mitigating procedures that can lessen potential risk. Every issue opened in the repo, closed PRs, previous contests and audits are out of scope.
All issues submitted by wardens to the GMTrade bounty will be added to this repo once they have been reviewed by the sponsors. These are considered known issues and are out-of-scope for bounty rewards.
https://github.com/gmsol-labs/gmx-solana/blob/main/README.md#known-issues
Previous Audits Any previously reported vulnerabilities mentioned in past audit reports are not eligible for a reward.
GMTrade previous audits can be found below:
https://github.com/gmsol-labs/gmx-solana-audits
Specific Types of Issues • Informational findings. • Design choices or expected design behaviors related to protocol. • Issues that are ultimately user errors and can easily be caught in the frontend. For example, transfers to the System Program. • Rounding errors. • Relatively high gas consumption. • Attacks requiring access to Timelock or Oracles. • Risk of loss due to decline in pool asset prices. • Price manipulation on third-party exchanges. • Exploits based on delayed or extreme price feed updates. • Attacks that are not economically feasible. • Vulnerabilities related to hosting providers.
Trusted Roles • Program upgrade authorities responsible for deploying and upgrading program code. • The administrators with control over the default store account authority, typically protected by multisig and timelock mechanisms. • Any program-defined privileged roles granted or managed by the administrators. • Keeper accounts responsible for critical operations or maintaining service availability.
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