governance/constitution/ConstitutionVoting

governance/rootNodes/RootNodesSlashingVoting

governance/rootNodes/RootNodeSlashingEscrow

governance/validators/ValidatorsSlashingVoting

governance/validators/ValidatorSlashingEscrow

governance/experts/EPQFI_MembershipVoting

governance/experts/EPQFI_ParametersVoting

All smart contracts of Q Blockchain can be found at [https://gitlab.com/q-dev/system-contracts](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.

The Q Blockchain is the universal governance layer for the decentralized world.

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)

Any governance voting result manipulation

Direct theft of any user funds in pools, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds in pools

Protocol insolvency

Execute arbitrary system commands

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)

Taking down the application/website

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.

Subdomain takeover with already-connected wallet interaction

Direct theft of user funds

Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions

Unintended chain split (Network partition)

Transient consensus failures

Theft of unclaimed yield in pools

Permanent freezing of unclaimed yield in pools

Temporary freezing of funds for at least 4 hours

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.

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.

Improperly disclosing confidential user information such as email address, phone number, physical address, etc.

Subdomain takeover without already-connected wallet interaction

Smart contract unable to operate due to lack of token funds

Block stuffing for profit

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Theft of gas

Unbounded gas consumption

Any of the above impacts that have been reported and fixed in the q-client upstream repository (https://github.com/ethereum/go-ethereum) more than 6 months ago.

Any of the above impacts that have been reported and fixed in the q-client upstream repository (https://github.com/ethereum/go-ethereum) more than 6 months ago

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 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, with payments processed in [QGOV](https://coinmarketcap.com/currencies/q-protocol/) token and paid out on the Q Protocol Network.

Q Blockchain

Resources & Documentation