LogoLogo
  • Introduction
    • Whitepaper (Preface)
    • Investors
  • How to create a wallet
  • How to buy $HINK
  • HINKAL WALLET
    • Features
    • Getting Started
      • Creating your first wallet
      • Account Management
      • Gas Tokens
    • IMPORTANT - Protecting Tokens
    • Receiving Tokens
    • Sending Tokens
    • Swapping
    • Connecting to dApps
    • Settings
  • Developers
    • Hinkal SDK
    • SDK Integration
    • Smart Contract Addresses
  • ECOSYSTEM
    • Supported Chains
    • Compliance
    • 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
  • Never use these addresses to receive tokens
  • Scenario 1 — On-ramp with wallet connection
  • Scenario 2 — On-ramp that asks for an address
  • Scenario 3 — Someone sends to the contract address
  • Scenario 4 — KYC or identity checks on dApps
  • Quick Checklist before receiving or onramping
  1. HINKAL WALLET

IMPORTANT - Protecting Tokens

Making sure you don't lose tokens in different instances

PreviousGas TokensNextReceiving Tokens

Last updated 15 days ago

Never use these addresses to receive tokens

This is Hinkal’s smart-contract address: 0xe1Cc1A5b0C5CE2cB7589287071F9510Db5E2C399

This is Hinkal’s relayer address: 0x1fE5F9eC3fB9a09eEBc6da6d677d8442Fcc58ef8

  • It’s a contract that holds everyone’s private funds.

  • If tokens are sent there with a regular onchain transfer, the relayer (which handles all transactions going in and out of the smart contract) will not be able to identify the recipient, resulting in lost funds.

  • Hinkal cannot reverse these transactions and is not liable for lost funds.

  • Anything you copy from Etherscan, a 3rd party dApp console, or elsewhere places you at risk of losing tokens.

  • ONLY receive assets through Receive → Payment Link / Proxy Address / Private Address inside the wallet.

Scenario 1 — On-ramp with wallet connection

(e.g. Uniswap’s “Buy” → Connect Wallet → choose Main Account)

What goes wrong
How to avoid it

The on-ramp sees the Main Account (which is the contract), so it pays the contract itself. Funds have no owner and will never appear in your Main Account balance.

Connect your Proxy instead. The Proxy can accept regular onchain transfers simillar to any Ethereum address. Copy the address from the "Receive" screen.

Scenario 2 — On-ramp that asks for an address

(no wallet connection step, paste address)

Wrong input
Result
Correct input

Hinkal contract address (copied from Etherscan or a dApp)

Tokens strand inside the contract, lost.

Proxy address from Receive → Proxy Address screen.

Scenario 3 — Someone sends to the contract address

If you share the contract’s 0x… string with a friend, their standard ERC-20 transfer will drop tokens into the contract with no recipient. Funds lost.

Tell senders to use:

  1. Payment link for public transfers to your Main Account

  2. Proxy address for public transfers to your Proxy

  3. Private address for shielded transfers between Hinkal users.

Scenario 4 — KYC or identity checks on dApps

Completing KYC with the Main Account links your real-world info to the privacy contract. Always switch to Proxy before submitting personal details.

Steps to stay safe

  1. Open extension → click account switcher → choose Proxy.

  2. Confirm the top-right badge shows Connected next to Proxy.

  3. Proceed with the dApp’s KYC flow.

Quick Checklist before receiving or onramping

  • Receiving? Copy address from Receive inside Hinkal—never from a block explorer.

  • On-ramp? Use Proxy address or connect with the Proxy account.

  • KYC? Proxy only.

  • Friend paying you? Send them your Payment link, Proxy address or Private address.

  • Never paste or share the Hinkal contract or relayer addresses.