# Features #### **Public and Private Accounts** Hinkal Wallet includes two account modes within a single interface: * a **public account**, which functions as a standard on-chain wallet * a **confidential account**, where balances and transactions are not exposed on-chain Users can switch between these accounts at any time. Assets can be purchased from a public account, through MoonPay integration - Apple Pay, Google Pay, or Credit Card (minimum purchase $20 worth of any asset). \ \ After purchase: * **shield** from the public into the private account * **unshield** back to the public account when needed Incoming funds can also be **auto-shielded**. *** #### **Privacy** The private account enables transactions without exposing on-chain activity. Within the private account: * balances are not publicly visible * transfers do not expose sender, recipient, or amount on-chain Transfers between confidential balances remain fully confidential on-chain. Transfers from a private account to a public wallet are executed as standard on-chain transactions, while the sender, original confidential balance and prior activity remain private. *** #### **Transactions** From the wallet, users can: * send and receive funds from both public and confidential accounts * execute transfers between confidential accounts * swap and bridge assets within the wallet All actions can be performed using any assets and supported networks (Solana, Ethereum, and major EVM chains). *** #### **Composability** Hinkal Wallet connects to decentralized applications in the same way as standard wallets. Users can: * connect their wallet to any dApp * interact using their public account (standard on-chain interaction) * use confidential balances when privacy is required For additional separation, users can generate temporary accounts for specific dApp interactions and then move funds into their confidential balance. *** #### **On-Chain Visibility** Wallet activity is executed through the Hinkal smart contract As a result: * confidential balances are not visible on-chain * private-to-private transfers don't expose sender, recipient, and amounts * private-to-public transfers keep sender wallet confidential *** #### **Self-Custody** Hinkal Wallet is fully self-custodial. * users retain full control of private keys and assets * no third party can access or move funds * all transactions are signed by the user *** #### **Compliance** Hinkal Wallet supports reporting and audit workflows. * transaction history can be exported by preferred timeframe * users can disclose activity when required The system is designed to support confidentiality by default, with optional transparency when needed. --- # 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/hinkal-wallet/features.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.