Fractal is the market leader in identity verification in the blockchain space. Our community has grown to 1M users, almost half with fully verified, reusable identities. What makes us different is that we first mastered the hard and “boring” work of identity verification before moving to improve the technical layer.
Fractal - Become the gatekeeper of your data
Identity is not just for KYC/AML. Making identity simple and secure is how we bring the next billion people into the space. Identity helps bring much needed legitimacy to crypto. It’s a powerful feature that allows you to:
We have a community of 1 million crypto users, each only a click away from your product, your dApp, your token, your DAO.
Using Fractal, you can authorize user actions based on verified uniqueness, reputation, and KYC/AML status — all this without needing to access or manage personal data.
Our products sit on a decentralization spectrum. The further to the right, the more control users have over their own data, and the less intermediation by Fractal.
We encourage you to go as far right as you’re comfortable with, but we understand decentralization is a process. We’re pragmatic and offer you several products to choose from depending on your needs, ethos and technical stack.
The OAuth API provides a familiar flow for web applications. It behaves similarly to Login with ... from providers like meta and google except that an authorization token is returned to your application only if the user has a verified credential with us. So, your dApp can use OAuth API to verify the credential of your user. However, this cannot be used to provide on-chain credential verification by your smart contracts - you must build this functionality yourself. See Credentials API and DID Registry products below to get credential verification for both your dApp and your smart contract.
Our Credentials API enables you to verify the credentials associated with a wallet address in your smart contract (on-chain) or in your dApp. Your dApp makes a call to the API with a wallet address and the API replies with a credential proof, if it exists, associated with that wallet address. Your dApp includes the proof with the transaction sent to your smart contract.
🔗 docs 🔗 developer demo 🔗 user demo
Our DID Registry enables you to verify the credentials associated with a wallet address in your smart contract (on-chain) or in your dApp. The Registry is a smart contract Fractal has deployed that contains two public methods your dApp and smart contract can call to verify a credential. Registries are deployed on Karura, Avalanche, Gnosis (soon), Aurora (soon) and Polygon. Registries will be deployed on other chains on a demand basis.
⚠️ This product might not yet be feature-complete for your needs. Please get in touch with [email protected] for more information on our plans.
Decentralized and self-sovereign identity: users own their data and are fully in control of sharing.
| OAuth API | Credential API | DID Registry | |
|---|---|---|---|
| Overview | |||
| Description | A ubiquitous flow that all users know |
Federated verified identity provider (“log in with Fractal”) | One-click wallet flow all crypto users know
User verification proofs that only require a wallet like MetaMask | A no-touch flow that feels like magic to crypto users
A privacy-preserving identity verification commons | | Flow | Users are redirected to Fractal to authorize KYC status and/or data sharing, and then redirected back.
Use our API to get their access token and query their KYC status and/or personal data. | Users sign an authorization with their wallet. Send it to our API to get a KYC proof.
Include this proof in their transactions to inform your smart contract decisions. | Users do nothing. Look up their KYC status of their address in the DID Registry.
Your smart contracts can look up the transaction sender in the DID Registry to inform decisions. | | Links | | | | | Demo | demo.fractal.id | credential-api.demo.fractal.id | did-registry.demo.fractal.id | | Docs | GitBook | GitBook | GitBook | | Data access | | | | | KYC status | Available via API and Dashboard | Available via API and Dashboard | Available in DID Registry and Dashboard | | Country of residency and/or nationality | Available via API and Dashboard | Include a list of banned residencies and/or nationalities in API call, and it tells you if there’s a match; also available in Dashboard | Available in Dashboard | | Personal data | Optionally available via API and Dashboard | Optionally available via API and Dashboard | Optionally available via API and Dashboard | | Comparison | | | | | Decentralization | 🔴 KYC status and/or data access requires API call 🟡 Users can't easily download their data | 🔴 KYC status and/or data access requires API call 🟡 Users can't easily download their data | 🟢 KYC status available in the registry 🟡 Users can't easily download their data | | Integration | 🟢 OAuth is a widely adopted standard 🟡 A back-end is needed 🟡 KYC status and/or data access requires user interaction 🔴 Compatible with web2 only | 🟢 Single API call 🟢 No back-end needed 🟢 Compatible with web2 and web3 🟡 KYC status and/or data access requires user interaction | 🟢 Single blockchain lookup 🟢 No back-end needed 🟢 Compatible with web2 and web3 🟡 Data access requires user interaction | | Privacy | 🟢 Data access is optional 🟢 Users can delete their data | 🟢 Data access is optional 🟢 Users can delete their data | 🟢 Data access is optional 🟢 Users can delete their data | | User experience | 🟡 All users must be redirected (once) through Fractal to authorize sharing of KYC status and/or personal data | 🟢 Users can authorize sharing of KYC status and/or personal data using wallet 🟢 Approved users don’t need to be redirected through Fractal | 🟢 No interaction needed for approved users |
The Fractal Protocol is built for a multi-chain world. It aggregates verified identities from any dApp and provides a trustless cross-chain synchronization mechanism.
Using the Fractal Protocol enables any dApp on any chain to leverage identity verification.
