Bring Institutions
to DeFi
Permissioned access to DeFi pools, launchpads, and governance without sacrificing decentralization.
Who this is for
100%
On-chain verification
No centralized gatekeeper
0 PII
Data transmitted
Zero raw data exposure
30+
Chains supported
Omni-chain by design
< 2s
Credential check
At smart contract level
Compliance at the contract level, privacy at the user level.
User Verifies Once
The user completes zkKYC on their device. A zero-knowledge proof is generated — no raw data leaves the device.
Credential Issued On-Chain
A tamper-proof credential is written to the blockchain. The user holds it in their zkMe Identity Wallet.
Protocol Checks Credential
When the user interacts with a permissioned pool or launchpad, the smart contract checks for a valid credential.
Access Granted or Denied
The contract receives a yes/no signal. No personal data is transmitted. The user's identity remains private.
Four ways to deploy
permissioned DeFi.
Select a use case to explore the problem, solution, and outcome.
Institutional capital cannot enter DeFi because pools have no way to enforce KYC/AML requirements without a centralized gatekeeper.
zkKYC credentials gate pool access at the smart contract level. Only wallets holding a valid credential can deposit — verified on-chain, no PII stored anywhere.
Protocols satisfy regulatory requirements and unlock institutional TVL. Users participate without revealing identity to the protocol or to zkMe.
DAO governance is vulnerable to Sybil attacks — one actor controlling many wallets to manipulate votes. Token-weighted voting alone does not solve this.
Proof of Personhood credentials ensure each governance participant is a unique, verified human — without revealing who they are.
Governance votes reflect genuine community consensus. One person, one vote models become viable on-chain for the first time.
FATF Travel Rule and AML requirements apply to VASPs operating in DeFi, but existing solutions require storing transaction data centrally or blocking entire wallet addresses.
KYT monitors transaction patterns and assigns risk scores on-chain. AML checks happen at the credential layer — no transaction data is stored.
Protocols demonstrate FATF compliance without becoming surveillance infrastructure. Users transact freely; only risk signals are shared, never raw data.
Token sales face regulatory scrutiny over investor eligibility, jurisdiction restrictions, and anti-money laundering obligations — but traditional KYC creates friction and data liability.
zkKYC verifies investor eligibility and jurisdiction at the wallet level. Launchpads receive a yes/no signal — no raw KYC data collected or stored.
Launchpads run compliant token sales globally, reduce legal exposure, and deliver a frictionless experience for verified participants.
The credentials that power permissioned DeFi.
Each credential plays a specific role. Composable — use one or combine several.
