Gear
Gear protocol is an advanced WASM based smart contract platform capable of being deployed as a Kusama and Polkadot parachain, that enables developers to deploy their dApps in under 5 minutes in the easiest and most efficient way possible.
PoC required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Network not being able to confirm new transactions (total network shutdown)
Unintended permanent chain split requiring hard fork (network partition requiring hard fork)
Direct loss of funds
Permanent freezing of funds (fix requires hardfork)
Unintended chain split (network partition)
Transient consensus failures
RPC API crash
Network unable to process internal message queue and requires maintenance mode to restart it
High compute consumption by validator/mining nodes when blocks are not full
Attacks against thin clients
DoS of greater than 30% of validator or miner nodes and does not shut down the network
DoS of greater than 10% but less than 30% of validator or miner nodes and does not shut down the network
Out of scope
- Issues that can be reproduced on networks configured and currently run by Gear, i.e.:
- Gear Test Network V6
- Vara Network
Severity of Issues that point out problems with the code and can theoretically affect the above network list will be considered individually.
- Best practice critiques
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
8.5k