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.

For more information about Gear, please visit https://www.gear-tech.io/.

Rewards are distributed according to the impact of the vulnerability based on the 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
• 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 protocol code can be found at https://github.com/gear-tech/gear and 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.

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.

The following vulnerabilities are excluded from the rewards for this bug bounty program:

• Attacks that the reporter has already exploited themselves, leading to damage
• Attacks requiring access to leaked keys/credentials
• Attacks requiring access to privileged addresses (governance, strategist)
• Issues that can be reproduced on networks configured and currently run by Gear, i.e.:

1. Gear Test Network V6
2. Vara Network

Severity of Issues that point out problems with the code and can theoretically affect the above network list will be considered individually.

Smart Contracts and Blockchain

• Incorrect data supplied by third party oracles
  • Not to exclude oracle manipulation/flash loan attacks
• Basic economic governance attacks (e.g. 51% attack)
• Lack of liquidity
• Best practice critiques
• Sybil attacks
• Centralization risks

The following activities are prohibited by this bug bounty program:

• Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
• Any testing with pricing oracles or third party smart contracts
• Attempting phishing or other social engineering attacks against our employees and/or customers
• Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
• Any denial of service attacks
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty