LogoLogo
  • Introduction
    • Whitepaper (Preface)
    • Investors
  • Community Pre-Sale
    • Overview
  • How to create a wallet
  • How to buy $HINK
  • HINKAL WALLET
    • Features
    • Hinkal Points
    • Points Eligibility
    • Compliance
  • Developers
    • Hinkal SDK
    • SDK Integration
    • Smart Contract Addresses
  • ECOSYSTEM
    • Supported Chains
    • Media Kit
  • TECHNICAL DESCRIPTION
    • Overview
    • Setup
      • Keys and Shielded Addresses
      • Nullifiers & Commitments
    • Smart Contracts
      • Unexpected Relay Costs Accounting - Stealth Addresses
      • Extensibility with Hooks
    • Compliance & Security
      • Access Tokens and User Authentication
    • Transactions
      • Deposits & Withdrawals
      • Swaps
      • Transfers
    • Risks
  • Anonymity Staking
  • FAQ
Powered by GitBook
On this page
  1. Developers

SDK Integration

PreviousHinkal SDKNextSmart Contract Addresses

Last updated 2 months ago

Content Security Policy

The Hinkal SDK depends on , a powerful library that enables local zero-knowledge proving in both browser and Node.js environments. Snarkjs leverages to perform complex cryptographic computations efficiently.

As a result, any client-side application integrating the Hinkal SDK must adjust its Content-Security-Policy to allow the ‘wasm-unsafe-eval’ directive under the script-src setting. This configuration ensures that the cryptographic processes can execute properly.

snarkjs
WebAssembly