# Connecting to dApps

## Connecting to a dApp

From the dApp or from the hinkal wallet (active seesion detection).\
Both result in the same connection.

You can initiate a connection:

* From a **dApp**
* Or directly from your **Hinkal Wallet**

### Step-by-step

1. Open a dApp
2. Click **Connect Wallet**
3. Select **Hinkal Wallet**

<figure><img src="/files/CfnDrHFdITJ6sXRDTsTl" alt=""><figcaption></figcaption></figure>

4. **Hinkal opens and shows a connection request**
5. **Review:**

* dApp name
* URL
* Network

<figure><img src="/files/mcLRSUGrH40JPADozjOu" alt=""><figcaption></figcaption></figure>

6. **Choose account:**

* Select an existing **Public account**
* Or click **New account** to create one instantly

<figure><img src="/files/lMof9BHKa2PjCir5hbTs" alt=""><figcaption></figcaption></figure>

7. (Optional) Top up account\
   Preserve confidentiality with **private funding.**&#x20;
8. **Click:**

* **Connect**
* or **Fund & Connect**

<figure><img src="/files/vO6SMgXs2HB3CT8ilV0v" alt=""><figcaption></figcaption></figure>

### Result

* The dApp is now connected
* It interacts with your **Public account only**
* Your **Private balance remains confidential**

## Method 2: From Hinkal Wallet

Use this when you already have a dApp open in your browser.

### Step-by-step

1. Open Hinkal extension
2. Click the **web icon (top right)**
3. Select the active dApp session
4. Click **Connect**

<figure><img src="/files/PrgNJkg2p6kM7kYZ3Mev" alt=""><figcaption></figcaption></figure>

### Result

* Connected via **Public account**
* Private account remains confidential.&#x20;

## Connecting via WalletConnect

Use this when a dApp doesn’t detect Hinkal directly.

#### Step-by-step

1. In the dApp, click **Connect Wallet → WalletConnect**

<figure><img src="/files/SDnAcGokig885iSr3OvB" alt=""><figcaption></figcaption></figure>

2. Copy the **pairing code**

<figure><img src="/files/aMNzEgYwYsPKts4gArqD" alt=""><figcaption></figcaption></figure>

3. Open Hinkal Wallet
4. Click the **web icon**
5. Select **WalletConnect**

<figure><img src="/files/DuM4zpy07f5rRgHhVMFW" alt="" width="345"><figcaption></figcaption></figure>

6. Paste the pairing code
7. Click **Connect**

<figure><img src="/files/K6U8BdjjX86Cau6XfvyH" alt="" width="351"><figcaption></figcaption></figure>

8. Choose or create a **Public account**

<figure><img src="/files/1pg9yAgi0Cp8NGxVLexQ" alt="" width="348"><figcaption></figcaption></figure>

9. (Optional) Top up account\
   Preserve confidentiality with **private funding.**&#x20;
10. Click **Connect**

<figure><img src="/files/vO6SMgXs2HB3CT8ilV0v" alt=""><figcaption></figcaption></figure>

## Interacting with dApps

Once connected, dApps can request actions.

### Types of requests

#### Transaction

Execute on-chain action

#### Token approval

Allow contract to spend tokens

#### Signature

Sign a message (no gas)

### What you’ll see

Before confirming, Hinkal shows:

* dApp name
* Account used (Public)
* Network
* Token / amount

## Managing connections

1. Click the **web icon**
2. Open **Manage Connections**

<div><figure><img src="/files/NwJvhqrsdCjPsS3yIMnu" alt=""><figcaption></figcaption></figure> <figure><img src="/files/wBDmVNvyiL1ERAPiVL7G" alt=""><figcaption></figcaption></figure></div>

You can:

* Disconnect a specific dApp
* Disconnect all sessions

## Key rule

dApps always interact through **Public accounts**

## What this means

* Your **Private balance is never exposed to dApps**
* You can:
  * Create a fresh Public account per dApp
  * Fund it privately
  * Use it for interactions
  * Move funds back to Private afterward

Privacy is preserved by design, not by user effort.&#x20;


---

# 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/connecting-to-dapps.md?ask=<question>
```

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.
