Verified humans. Clean wallets.
Keys the user controls.
KYC, wallet screening, and transaction intelligence for exchanges, protocols, and tokenized-asset platforms, built so that proving a real person is behind an address never means handing their identity to a central database.
What protocol teams are up against
Identity turned into a hard requirement for crypto products, and neither the bank vendors nor the crypto-native ones solved it.
Regulators stopped treating crypto as an exception
MiCA in the EU, FATF Travel Rule enforcement by VASPs worldwide, and registration regimes in Canada, Singapore, Hong Kong, and the UAE all require verified counterparties and screened flows. Compliance vendors built for banks are retrofitting; vendors built for crypto have no identity layer.
Sybil and bot accounts drain airdrops, governance, and liquidity
One person, countless wallets. Proof-of-humanity schemes prove a human exists; they do not bind that human to the keys that act.
Tokenized real-world assets need permissioned holders
Permissioned-token standards require an identity registry; without verified, revocable credentials behind it the registry is a spreadsheet with extra steps.
What goes live
The modules you can turn on in the current product, without a platform migration first.
Identity Verification
Document and liveness KYC via Web SDK, QR handoff to mobile, or REST API; global document coverage; auto-approve, auto-reject, and manual-review thresholds.
On-Chain Intelligence (KYT / KYA)
Wallet and transaction screening tied to the verified identity.
Sanctions & PEP screening
Real-time checks on every onboarding and re-screen; restricted-jurisdiction enforcement and IP-based geo-blocking.
Verifiable Credentials
Issue a KYC-passed credential the wallet holds; verify it on demand; selective disclosure via zero-knowledge proofs.
The same deployment, on the trust layer
One human, one identity, any number of wallets
Keys derived from a verified identity make Sybil resistance a property of the key, not a heuristic applied afterward.
Compliance without custody of PII
The platform verifies a credential signature; the user keeps the data. Your audit trail is cryptographic, your breach surface is smaller.
Permissioned tokens with real revocation
Credentials expire and revoke; the on-chain registry reflects the off-chain truth.
Quantum-safe signatures for assets meant to last
Keys issued today use the NIST post-quantum standards; the tokens you mint now do not need re-keying when the threat lands.
Where teams start
Each one runs on the modules above — pick the one that matches the quarter you are in.
- Exchange and broker onboarding with Travel Rule counterparty attestation
- Airdrop and governance eligibility bound to a verified human, with no wallet-to-identity link exposed on-chain
- RWA issuance: KYC credential → permissioned-token whitelist → ongoing re-screening
- DAO treasury and multisig signers with human-anchored, revocable credentials
- Stablecoin issuer and distributor compliance
What we build on, and what we claim
Open specifications, named without the version churn. Every status below is a different promise.
W3C Verifiable Credentials and DIDs
NIST post-quantum standards
OpenID Connect
FATF Travel Rule
eIDAS
We do not claim compatibility with on-chain agent-registry proposals.
On-chain credibility,off-chain obligations.
Ship compliant onboarding this sprint with the SDK, then let every verified user carry a credential across your products and chains. Talk to our team about your protocol, or start in the sandbox today.