Q Blockchain
The Q Blockchain is the universal governance layer for the decentralized world.
PoC required
KYC required
Rewards by Threat Level
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 web/app and blockchain/DLT bug reports, as well as all Critical/High/Medium severity smart contract 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.
In addition, all Critical severity bug reports must come with a suggestion for a fix in order to be considered for a reward.
Rewards for critical smart contract vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum reward of USD 25 000 for Critical smart contract bug reports.
Q Blockchain requires that all bug bounty hunters who are eligible for a reward submit an invoice to Q Development AG, which administers and pays out bounty rewards. Please note that Q Development will need to perform a KYC check on the bug bounty hunter claiming the reward. Information typically required in a KYC check includes the name and address of the bug bounty hunter and a copy of the passport, or in case of a corporation, a trade register excerpt or similar. Please also note that Q Development AG cannot make payments to officially sanctioned/blacklisted countries. If in doubt, please feel free to get in touch with the team prior to submitting a reward payout claim.
Payouts are handled by the Q Blockchain team directly and are denominated in USD. However, payouts are done in USDC.
Program Overview
The Q Blockchain is the universal governance layer for the decentralized world.
Q’s unique dual-layer node architecture provides an unparalleled level of security against malicious attacks.
Q combines the benefits of a public, open and decentralized ledger with the transparency of enforceable private contracts. Whether you want to interact with other businesses, build decentralized applications or simply send and receive tokens: Q is for you.
For more information about Q Blockchain, please visit https://q.org/.
KYC required
The submission of KYC information is a requirement for payout processing.
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- 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 that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Any other actions prohibited by the Immunefi Rules
Feasibility Limitations
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.