Quadrata
Quadrata Web3 Passport is a privacy-preserving, sybil-resistant technology that brings identity, compliance, and reputation to DApps built on public blockchains.
PoC required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
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
Out of scope
Program Rules
- Avoid using web application scanners for automatic vulnerability searching which generates massive traffic
- Make every effort not to damage or restrict the availability of products, services, or infrastructure
- Avoid compromising any personal data, interruption, or degradation of any service
- Don’t access or modify other user data, localize all tests to your accounts
- Perform testing only within the scope
- Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
- Don’t spam forms or account creation flows using automated scanners
- In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity.
- Don’t break any law and stay in the defined scope
- Any details of found vulnerabilities must not be communicated to anyone who is not an ImmuniFi employee without appropriate permission
Disclosure Guidelines
- Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization
- No vulnerability disclosure, including partial is allowed for the moment.
- Do NOT publish/discuss bugs
Eligibility and Coordinated Disclosure
We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward:
-
You must be the first reporter of a vulnerability.
-
The vulnerability must be identified before it is discovered internally by the team.
-
The vulnerability must be a qualifying vulnerability
-
Any vulnerability found must be reported no later than 24 hours after discovery and exclusively to Immunefi Platform Dashboard
-
You must send a clear textual description of the report along with steps to reproduce the issue, including attachments such as screenshots or proof of concept code as necessary.
-
You must not be a former or current employee of us or one of its contractors.
-
Provide detailed but to-the point reproduction steps
-
Monetary rewards will not be provided to persons or organizations who violate the Program Rules and Disclosure Guidelines
-
Best practice critiques
-
Theoretical vulnerabilities without any proof or demonstration
-
Old compiler version
-
The compiler version is not locked
-
Vulnerabilities in imported contracts
-
Code style guide violations
-
Redundant code
-
Gas optimizations
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers