> For the complete documentation index, see [llms.txt](https://hinkal-team.gitbook.io/hinkal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hinkal-team.gitbook.io/hinkal/hinkal-wallet/getting-started.md).

# Getting Started

### Wallet Setup

Hinkal Wallet supports three ways to access and manage funds:

* connect an existing external wallet
* create a new wallet with a 12-word recovery phrase
* import an existing hinkal wallet

You’ll learn what each path means for recovery, privacy, and day-to-day convenience.

### **Account Model**

Hinkal Wallet uses a dual-account model:

* **Private account,** where funds are held within a confidential balance in the Hinkal smart contract
* P**ublic account**, which behaves as a standard on-chain wallet

Users can move assets between these accounts using:

* **Shield** (public → confidential)
* **Unshield** (confidential → public)

This model allows users to switch between public and confidential activity depending on the use case.

### Gas Tokens

Hinkal Wallet supports gas abstraction.

Users can pay transaction fees using supported tokens such as SOL, ETH, USDC, USDT, or DAI.

A relayer submits the transaction on-chain and covers the native gas cost. The equivalent value is deducted from the user’s selected token.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://hinkal-team.gitbook.io/hinkal/hinkal-wallet/getting-started.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.