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. TECHNICAL DESCRIPTION
  2. Transactions

Transfers

PreviousSwapsNextRisks

Last updated 3 months ago

Transfers enable the transmission of up two commitments of the same asset between two parties by nullifying the previous commitments and creating up to two new commitments.

To ensure a recipient receives the secret information required to spend their commitments, the sender encrypts the secrets of the commitment sent to the recipient.

A Transfer ZK Proof proves that the prover has nullified up to two old commitments which existed in the Merkle Tree, created a new one, and encrypted its information for the recipient.

In either case, the information broadcasted on chain will be that an Ethereum address has nullified commitments amongst the commitment pool owned by the transmitter, and that new commitments have been created. Information on the new owner, which commitments were spent or the amount transferred remain discreet. Check out Hinkal's current used to fairly compensate for the costs.

fee structure