Gear protocol code can be found at [https://github.com/gear-tech/gear](https://github.com/gear-tech/gear) and [https://github.com/gear-tech/dlmalloc-rust](https://github.com/gear-tech/dlmalloc-rust). Gear Assets in scope table are specified to commit 22dfb9e43fe4fc608c747ca02e0e4ba7c5ccf123. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program. 

For more documentation, please refer to [https://github.com/gear-tech/gear/blob/master/README.md.  ](https://github.com/gear-tech/gear/blob/master/README.md)

If an impact can be caused to any other asset managed by Gear that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.

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.

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

Underpricing transaction fees relative to computation time

Rewards are distributed according to the impact of the vulnerability based on the  [Immunefi Vulnerability Severity Classification System V2.2.](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2/) This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported. 

All Critical Blockchain/DLT bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.

The following vulnerabilities are not eligible for a reward:
- [https://github.com/gear-tech/gear/issues ](https://github.com/gear-tech/gear/issues)
- Issues that cannot 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.

Gear requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed are Passport and Utility Bill. The collection of this information will be done by the project team.

Payouts are handled by the __Gear__ team directly and are denominated in USD. However, payouts are done in __USDC__.

Gear

Resources & Documentation