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
  • zkSNARKs
  • Stealth Addresses
  1. TECHNICAL DESCRIPTION

Overview

Restoring control over your on-chain data

PreviousMedia KitNextSetup

Last updated 3 months ago

Hinkal supports any ERC-20 token for any transaction or dApp interactions without reference to the original deposit address. Each user holds a private address where tokens are stored after depositing.

zkSNARKs

In 2012, Bitansky and colleagues introduced, or zkSNARK for short, which provides the ability for one party to prove to another that they have knowledge of something, without revealing what that is in order to provide the proof.

Hinkal uses zkSNARKs to send confidential transactions. A user can generate proof of validity of the transaction without revealing key transaction parameters such as the origin/destination addresses or the amount of the transaction.

Stealth Addresses

Vitalik Buterin created a on his website describing a steath address system that would allow the recipient of a transaction to keep their identity secret.

Hinkal uses stealth addresses to return the overhead gas fees and slippage to the users. Changes in token amounts are pre-determined before a transaction is submitted and costs for the transaction are covered by the user. Stealth addresses are generated before the transaction swap is submitted. This enables the protocol to execute the transaction, cover the transaction costs, and send back to the user’s private address any difference between the expected and the actual cost.

Zero-Knowledge Succinct Non-Interactive Argument of Knowledge
post