How Hinkal prevents illicit parties with reusable attestation and KYC(B)
To ensure no illicit parties can interact with the protocol, users can access Hinkal after passing KYC (B) verification. As a result, no users or wallets belonging to sanctioned lists can pose a pool contamination risk.
It is a common misconception that KYC (B) verification compromises privacy and pseudonymity. All information provided stays with the KYC (B) provider and remains off-chain. Users’ privacy is preserved on-chain.
To make the onboarding process seamless, Hinkal has integrated several KYC (B) providers. Users can reuse their KYC (B) attestation, from major CEXs and other KYC (B) protocols, and proceed directly to Access Token minting. Otherwise, they can choose their preferred provider and verify their identity. The process is simple and can be completed in under 3 minutes.
Let’s see what the process looks like:
