# Whitepaper (Preface) Hinkal brings universal privacy to stablecoin payments, settlements, and payouts across Ethereum, Polygon, Solana, Tron, and major EVM networks. It enables institutions, payment platforms, applications, and individuals to operate on-chain without exposing balances, counterparties, or treasury activity - all within the same wallets, assets, and workflows they already rely on. Public blockchains provide global, neutral settlement - but their default transparency creates material risks: revenue leakage, counterparty mapping, balance surveillance, and operational exposure. Hinkal addresses this by embedding protocol-level confidentiality directly into on-chain execution, without requiring private blockchains, custodial intermediaries, or liquidity migration. Privacy is not limited to a single chain, wallet, or use case. It extends across every on-chain action, ensuring both sender and recipient remain confidential. Rather than relying on privacy-specific networks, mixers, or application-level obfuscation, Hinkal integrates directly into existing wallets, payment stacks, and workflows - preserving composability and public-chain finality. It is non-custodial by design. Users retain full control over their assets while transactions are executed through confidential routing and shielded settlement, removing public attribution. Privacy is enforced by default, while [compliance](https://hinkal-team.gitbook.io/hinkal/introduction/compliance) and auditability are preserved through selective disclosure, viewing keys, and downloadable transaction history when required. Hinkal brings complete, compliant privacy into everyday on-chain operations - defining the scale of stablecoin adoption. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://hinkal-team.gitbook.io/hinkal/introduction/whitepaper-preface.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.