Summary: Quadrata is a privacy-preserving identity-and-compliance passport layer for public-blockchain applications. Its current first-party surface centers on a non-transferable onchain passport that can expose reusable DID, AML, country, business, investor-status, and credit-score attributes, with both smart-contract and API/SDK integration paths for onboarding and querying users across multiple EVM chains.
What it does:
Issues a Quadrata Passport as a non-transferable NFT attached to a wallet
Lets integrators request and query reusable passport attributes such as DID, AML score, country, business status, accredited-investor status, and Cred Protocol score
Supports both consumer and business onboarding flows, including KYB-style business verification in addition to individual identity checks
Exposes onchain contracts for governance, passport minting/onboarding, and attribute reading
Exposes SDK and API flows for checking onboard status, consent requirements, and which attributes still need to be claimed before access is granted
Positions the passport as a privacy-preserving access layer for compliant web3 applications rather than as a one-off KYC widget
Key claims:
The official homepage calls Quadrata the “Single Sign-On for Compliant Web3” and describes the passport as a privacy-preserving soulbound token that can unlock an ecosystem of applications without storing PII onchain
The homepage and docs together show that the passport goes beyond simple KYC by supporting AML screening, wallet screening, country verification, age verification, KYB/business status, accredited-investor checks, sybil resistance, and an onchain credit-reputation field
The docs say DApps can query the passport through either smart contracts or APIs, which is a strong clue that Quadrata is middleware/control-plane infrastructure rather than only an identity frontend
The smart-contract docs define a three-contract surface — QuadGovernance, QuadPassport, and QuadReader — and publish production addresses across Ethereum, Polygon, Avalanche, Arbitrum, Optimism, Evmos, Kava EVM, zkSync Era, and Base
The SDK docs expose fetchOnboardStatus and related parsing helpers for determining attribute-claim and consent state, reinforcing that the project is packaging a reusable integration workflow rather than only a badge/NFT
The docs emphasize that the DID is sybil resistant and that country / AML / investor-status attributes are represented in standardized machine-queryable forms, which makes the passport usable as application policy input
Whitepaper: No canonical standalone Quadrata whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official site plus the integration, attribute, smart-contract, and SDK/API docs; see ../whitepapers/quadrata-primary-sources-2026-04-30.md.