Compliance & Security
Last updated
Last updated
To mitigate smart contract risks, Hinkal has integrated three pillars of security:
1) Audits: zkSecurity, Zokyo, Quantstamp and Secure3
2) Real-Time Protection and wallet screening: Hexagate
3) Bug Bounties: Immunefi
Only users with >$1k in assets must verify their complience through the following flow:
Hinkal checks if the user has a Binance Account Bound Token (BABt), Galxe Passport, or soulbound tokens from zkMe in the connected wallet. (If one of the above tokens is detected, the user is automatically verified)
If the user does not have one of the above tokens, they must verify the ownership of a CEX account without revealing any data to Hinkal. This is enabled by Reclaim protocol via zero-knowledge proofs. Users prove ownership by logging in to the CEX account and generating zk-proof, and then Hinkal accepts this proof as evidence that the user is not part of any sanction lists. Accepted attestations from exchanges are Binance, Coinbase, OKX, Gate, Kucoin, HTX, and MEXC.
Once the user's PII has been verified, they mint a non-transferable token with their first deposit (the ‘Access Token’) that confirms user's attestation.
