Though only the proxy contracts are listed as in-scope, current implementation and any further updates to the implementation contracts are considered in scope. When reporting a bug, please make sure to select the relevant proxy smart contract as the target.

Only those listed in the Assets in Scope table are considered to be in-scope of the bug bounty program. 

Bugs found in contracts across multiple chains will only count as a single vulnerability.

All smart contracts of Quadrata can be found at [https://github.com/QuadrataNetwork.](https://github.com/QuadrataNetwork) However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.


Quadrata Web3 Passport is a privacy-preserving, sybil-resistant technology that brings identity, compliance, and reputation to DApps built on public blockchains.

Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results

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

Can permanently block Passport minting

Can permanently block reading of Passport values

Passport manipulation such as changing attribute values, minting on behalf of an issuer and burning of passports

Unintended alteration of what the NFT represents (e.g. token URI, payload, artistic content)

Unauthorized transaction

Transaction manipulation

Quad Unit payment bypass

Rewards are distributed according to the impact of the vulnerability based on the  [Immunefi Vulnerability Severity Classification System V2.3.](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-3/) 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. 

__Reward Payment Terms__

Payouts are handled by the Quadrata team directly and are denominated in USD. However, payouts are done in ETH or USDC, at the discretion of the team.

__PoC Requirement and Guidelines__

All 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.

All PoCs submitted must comply with the Immunefi-wide [PoC Guidelines and Rules.](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules) Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

For the purposes of determining report validity, this is a Primacy of Rules Program. 

Quadrata adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms stated in this page.

Learn more about report validity best practices here: [Best Practice - Primacy of Impact vs Primacy of Rules. ](https://immunefisupport.zendesk.com/hc/en-us/articles/12340245635089-Best-Practices-Primacy-of-Impact)

__Responsible Publication Policy__

Quadrata adheres to category 3. This Policy determines what information whitehats are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our [Responsible Publication](https://immunefi.com/responsible-publication/) page.

__Known Issue Assurance__

Quadrata commits to providing Known Issue Assurance to bug submissions through their program. This means that Quadrata will either disclose known issues publicly or at the very least privately via a self-reported bug submission in order to allow for a more objective and streamlined mediation process to prove that an issue is known. Otherwise, assuming the bug report itself is valid, it would result in the bug report being considered in-scope and due 100% of the reward with respect to the bug bounty program terms.

__Restrictions on Security Researcher Eligibility__

Security researchers who fall under any of the following are ineligible for a reward
- OFAC-sanctioned country or region
- Does not pass Quadrata Identity Verification process (not able to mint a Quadrata Passport)

Known issues previously highlighted in the following audit reports are considered out of scope: 
- [Quantstamp](https://github.com/QuadrataNetwork/passport-contracts/blob/develop/audits/quantstamp-passport-final-2022-07.pdf)
- [Certik](https://www.certik.com/projects/quadrata)


Quadrata

Resources & Documentation