Quadrata

• Name: Quadrata
• URL: https://quadrata.com/
• Category: identity and compliance-attestation middleware / reusable onchain passport layer / EVM policy input
• Tags: ethereum-ecosystem
• Summary: Quadrata is reusable identity-and-compliance passport middleware for EVM apps. The NFT wrapper is incidental. What matters is reusable attestations applications can query for onboarding, gating, and policy.
• 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 and 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 multiple applications without storing PII onchain
  • The docs show the passport goes beyond simple KYC by supporting AML screening, wallet screening, country verification, age verification, KYB and business status, accredited-investor checks, sybil resistance, and an onchain credit-reputation field
  • DApps can query the passport through either smart contracts or APIs, which is the real reason this note matters: Quadrata is middleware, not just an identity front end
  • 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 helpers for attribute-claim and consent state, reinforcing that Quadrata is packaging a reusable integration workflow rather than a badge
• 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.
• Sources:
  • https://quadrata.com/
  • https://docs.quadrata.com/integration
  • https://docs.quadrata.com/integration/introduction/passport-attributes.md
  • https://docs.quadrata.com/integration/how-to-integrate/query-attributes
  • https://docs.quadrata.com/integration/additional-information/smart-contracts.md
  • https://docs.quadrata.com/integration/how-to-integrate/quadrata-sdk/advanced/api-libraries/api-service-libraries/fetch-onboard-status.md

Internal linkages

• Reusable identity-stack comparison: spruceid.
• When credit or trust scoring becomes the real policy input: cred-protocol.

Control surface

• Practical authority sits in passport issuance, attestor policy, consent-gated query flows, chain deployment, and which claims integrators decide to require.

• Read Quadrata as reusable policy middleware for EVM apps, not as a magical identity primitive.

• Last reviewed: 2026-06-16 UTC