Q Blockchain
Submit a BugProgram 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/.
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 50 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.
Blockchain/DLT
- Critical
- Level
- USD $50,000
- Payout
- High
- Level
- USD $25,000
- Payout
Smart Contract
- Critical
- Level
- Up to USD $200,000
- Payout
- High
- Level
- USD $25,000
- Payout
- Medium
- Level
- USD $5,000
- Payout
- Low
- Level
- USD $1,000
- Payout
Websites and Applications
- Critical
- Level
- USD $10,000
- Payout
- High
- Level
- USD $5,000
- Payout
Assets in scope
- Blockchain/DLT - Blockchain/DLTType
- Smart Contract - tokeneconomics/DefaultAllocationProxyType
- TargetSmart Contract - common/CompoundRateKeeperType
- Smart Contract - common/AddressStorageType
- Smart Contract - tokeneconomics/ValidationRewardProxyType
- Smart Contract - tokeneconomics/RootNodeRewardProxyType
- Smart Contract - tokeneconomics/QHolderRewardProxyType
- Smart Contract - tokeneconomics/QHolderRewardPoolType
- Smart Contract - tokeneconomics/ValidationRewardPoolsType
- Smart Contract - tokeneconomics/QVaultType
- Smart Contract - tokeneconomics/VestingType
- TargetSmart Contract - tokeneconomics/PushPaymentsType
- TargetSmart Contract - defi/TokenBridgeAdminProxyType
- Smart Contract - defi/token/StableCoinType
- Smart Contract - defi/BorrowingCoreType
- Smart Contract - defi/SavingType
- Smart Contract - defi/SystemBalanceType
- TargetSmart Contract - defi/LiquidationAuctionType
- TargetSmart Contract - defi/SystemSurplusAuctionType
- Smart Contract - defi/SystemDebtAuctionType
- Smart Contract - governance/constitution/ConstitutionType
- Smart Contract - governance/constitution/ConstitutionVotingType
- TargetSmart Contract - governance/rootNodes/RootsType
- Smart Contract - governance/rootNodes/RootsVotingType
- Smart Contract - governance/rootNodes/RootNodesSlashingVotingType
- Smart Contract - governance/rootNodes/RootNodeSlashingEscrowType
- Smart Contract - governance/validators/ValidatorsType
- Smart Contract - governance/validators/ValidatorsSlashingVotingType
- Smart Contract - governance/validators/ValidatorSlashingEscrowType
- Smart Contract - governance/experts/EPDR_MembershipType
- Smart Contract - governance/experts/EPDR_MembershipVotingType
- Smart Contract - governance/experts/EPDR_ParametersType
- Smart Contract - governance/experts/EPDR_ParametersVotingType
- Smart Contract - governance/experts/EPQFI_MembershipType
- Smart Contract - governance/experts/EPQFI_MembershipVotingType
- Smart Contract - governance/experts/EPQFI_ParametersType
- Smart Contract - governance/experts/EPQFI_ParametersVotingType
- Smart Contract - governance/experts/EPRS_MembershipType
- Smart Contract - governance/experts/EPRS_MembershipVotingType
- Smart Contract - governance/experts/EPRS_ParametersType
- Smart Contract - governance/experts/EPRS_ParametersVotingType
- Smart Contract - governance/EmergencyUpdateVotingType
- Smart Contract - governance/GeneralUpdateVotingType
- TargetSmart Contract - governance/VotingWeightProxyType
- TargetSmart Contract - tokeneconomics/SystemReserveType
- Smart Contract - governance/ContractRegistryUpgradeVotingType
- Smart Contract - governance/ContractRegistryAddressVotingType
- TargetWebsites and Applications - Web/AppType
- TargetWebsites and Applications - Web/AppType
All smart contracts of Q Blockchain can be found at https://gitlab.com/q-dev/system-contracts. Only those specifically in the contracts folder with the git tag ‘mainnet’ are considered assets in scope.
If any Critical impact can be caused to any other asset managed by Q Blockchain 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.
Impacts in scope
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.
Blockchain/DLT
- Network not being able to confirm new transactions (Total network shutdown)CriticalImpact
- Unintended permanent chain split requiring hard fork (Network partition requiring hard fork)CriticalImpact
- Direct loss of fundsCriticalImpact
- Permanent freezing of funds (fix requires hardfork)CriticalImpact
- Unintended chain split (Network partition)HighImpact
- Transient consensus failuresHighImpact
Smart Contract
- Any governance voting result manipulationCriticalImpact
- Direct theft of any user funds in pools, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Permanent freezing of funds in poolsCriticalImpact
- Protocol insolvencyCriticalImpact
- Theft of unclaimed yield in poolsHighImpact
- Permanent freezing of unclaimed yield in poolsHighImpact
- Temporary freezing of funds for at least 4 hoursHighImpact
- Smart contract unable to operate due to lack of token fundsMediumImpact
- Block stuffing for profitMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Theft of gasMediumImpact
- Unbounded gas consumptionMediumImpact
- Smart contract fails to deliver promised returns, but doesn’t lose valueLowImpact
Websites and Applications
- Execute arbitrary system commandsCriticalImpact
- Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys(this does not include non-sensitive environment variables, open source code, or usernames)CriticalImpact
- Taking down the application/websiteCriticalImpact
- Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as, changing registration information, commenting, voting, making trades, withdrawals, etc.CriticalImpact
- Subdomain takeover with already-connected wallet interactionCriticalImpact
- Direct theft of user fundsCriticalImpact
- Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactionsCriticalImpact
- Injecting/modifying the static content on the target application without Javascript (Persistent) such as HTML injection without Javascript, replacing existing text with arbitrary text, arbitrary file uploads, etc.HighImpact
- Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as email or password of the victim, etc.HighImpact
- Improperly disclosing confidential user information such as email address, phone number, physical address, etc.HighImpact
- Subdomain takeover without already-connected wallet interactionHighImpact
Out of Scope & Rules
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)
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
Websites and Apps
- Theoretical vulnerabilities without any proof or demonstration
- Attacks requiring physical access to the victim device
- Attacks requiring access to the local network of the victim
- Reflected plain text injection ex: url parameters, path, etc.
- This does not exclude reflected HTML injection with or without javascript
- This does not exclude persistent plain text injection
- Self-XSS
- Captcha bypass using OCR without impact demonstration
- CSRF with no state modifying security impact (ex: logout CSRF)
- Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
- Server-side non-confidential information disclosure such as IPs, server names, and most stack traces
- Vulnerabilities used only to enumerate or confirm the existence of users or tenants
- Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
- Lack of SSL/TLS best practices
- DDoS vulnerabilities
- Feature requests
- Issues related to the frontend without concrete impact and PoC
- Best practices issues without concrete impact and PoC
- Vulnerabilities primarily caused by browser/plugin defects
- Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
- Any vulnerability exploit requiring browser bugs for exploitation. ex: CSP bypass
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