Features
Hinkal Send enables private value transfers between public wallets on major public blockchains without requiring users to migrate liquidity, adopt new wallets, or interact with privacy-specific workflows.
Unlike systems that rely on persistent shielded balances or separate privacy networks, Hinkal Send operates as a confidential routing mechanism: assets are temporarily routed through Hinkal’s infrastructure and delivered to standard public addresses.
From the user’s perspective, a private transfer feels identical to a normal on-chain send.
User Experience
A user initiates a private send by:
Connecting an existing public wallet
Specifying a recipient address, token, and amount
Selecting an optional execution window
Executing a “Send Privately” action
No new wallet is created, and no long-lived shielded balance is required.
On-Chain Behavior
Under the hood, Hinkal Send:
Routes the transaction through Hinkal’s aggregated smart contract
Prevents the sender’s public wallet from appearing in the transfer path
Delivers funds to the recipient’s public address
On-chain observers see contract-originated transfers rather than direct wallet-to-wallet payments, reducing attribution of outbound activity to a specific wallet.
Privacy Properties
Privacy in Hinkal Send is achieved by reducing observability of transaction flows:
Recipient dispersion: Distributing value across multiple recipients reduces direct correlation between a single sender and an aggregate amount.
Execution window: Users may define a time window during which the transaction executes, reducing linkage between intent and settlement.
Randomized execution: Transfers are dispatched at non-deterministic times within the selected window, limiting deterministic pattern matching.
These mechanisms make it more difficult for third parties to reliably reconstruct payment intent, transaction history, or wallet behavior from public ledger data.
Last updated