Last updated
Hinkal is built on a security model with one core guarantee: no sensitive key data ever leaves the secure enclave in raw form. Private keys are generated, stored, and used exclusively inside a hardware-isolated enclave. No component outside the enclave — not the API server, not the database, not Hinkal engineers — ever sees raw key material.
This applies to both products that run on the enclave: the WaaS managed wallets and the Hinkal API. For WaaS, the protected material is the user's managed EVM, Solana, and Tron wallet keys. For the Hinkal API, it is the user's Hinkal shielded key, which decrypts their private balance and authorizes zero-knowledge proofs.
Last updated