> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fluton.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Using the wallet

> Connect, shield and unshield any listed token, pay a shielded address, resume a pending deposit, unwrap an encrypted balance, scan for your notes and share a view key.

The Fluton Pool wallet is the web app at [app.fluton.io](https://app.fluton.io). It talks to the pool, the relayer, the indexer and the backend API, and everything secret stays on your device: proofs are built with snarkjs **in your browser**, and your keys never leave it.

The wallet says **shield** and **unshield**. In the protocol, SDK and reference pages those are a *deposit* and a *withdrawal*, the same two operations under their contract names.

## Connect and unlock

The wallet runs on **Arbitrum One**. Press **Connect Wallet** and sign with an injected wallet: **MetaMask** or another EIP-1193 wallet. The session is remembered and restored silently after a reload, without a prompt, until you press **Disconnect**. If the wallet sits on another chain, the app offers to switch (**Switch to Arbitrum One**) before it signs anything.

Two signatures unlock the two kinds of balance:

**1. Sign to unlock**

One chain- and pool-bound message is hashed into your spend key. The same wallet therefore reproduces the same shielded wallet on any device, so there is nothing to back up beyond the wallet itself.

**2. Unlock your encrypted balance**

An eTOKEN balance is encrypted on-chain, so reading it needs one more signature (a self ACP for Fhenix CoFHE). The Shield form names the token, as in *Sign once to decrypt your encrypted USDC balance. Nothing is sent.*, and **Unlock encrypted** on the home screen's **Wallet** card unlocks every token at once.

## Shield a token

**Shield** moves tokens from your wallet into your private balance.

Pick the token in the **You deposit** selector: **USDC** or **ETH**. When your wallet holds an encrypted balance of that token, a **Pay with** choice appears: the plain ERC-20 (**TOKEN**), or **Encrypted** for its wrapper (**eTOKEN**). Both fields of the card hold the same amount, because shielding costs nothing beyond gas; under **Fees** the card shows **Platform fee (0%)**. See [TOKEN and eTOKEN](https://docs.fluton.io/concepts/token-formats.md) for what each route does on-chain.

The wallet shields no less than **10 USDC** or **0.001 ETH**, in either format. Below that the button reads *Below the minimum shield*.

The pool holds ether as WETH, so the wallet counts your ETH and your WETH as one balance and shows it as ETH. A shield uses the WETH you already hold first and wraps what is missing from your ETH, in a transaction of its own with one more confirmation in your wallet. The wallet keeps some ETH back for gas (*Leave some ETH for the network fee*). Inside the pool the token keeps the name WETH, which is what Unshield and Transfer show.

If you arrived through an invite link, a **Referred by** row names the invite this deposit credits, and you can remove it. See [Invite and referrals](https://docs.fluton.io/wallet/invite-and-referrals.md).

Screening comes first. Every deposit needs a signed screening of the wallet that sends it, so the button waits on the API (*Connecting to deposit screening…*) and blocks when it is unreachable (*Deposits unavailable: screening is offline*). The screening is fetched before anything is approved or proved, so a refused wallet spends nothing and is shown screening's answer rather than a failure. See [Deposit screening](https://docs.fluton.io/concepts/deposit-screening.md).

**Review** freezes the amount, format and referrer; **Shield** then runs the wallet prompts. A TOKEN shield is one pull, plus an approval when the allowance is short and, for ETH, the wrap before both. An eTOKEN shield is token-first: the tokens move into a receipt first and are credited once the pool has verified what it received.

## Unshield to your wallet

**Unshield** pays your private balance out to the connected wallet. Paying any other public address is a **Transfer** instead.

The amount in **You receive** is what the wallet receives. The pool's platform fee and, when one submits, the relayer's fee are spent *on top* of it from the same asset's private balance, and **You unshield** shows that total. The payout arrives as the plain TOKEN unless you switch on **Keep it encrypted in my wallet**, which pays the eTOKEN instead: its balance stays hidden in your wallet and it arrives without a claim step, while your address and the amount you unshield are public either way. [Fees and referrals](https://docs.fluton.io/concepts/fees.md) explains both charges; the platform fee is the withdrawal fee described there.

When a **relayer** is configured it submits the transaction and pays the gas, so your wallet never appears on-chain for the withdrawal. Without one, your wallet submits it and the card shows a **Network fee** instead. If the relayer fails, the app offers to send from your wallet, but only once it has established that the relayer never broadcast those notes; otherwise re-sending could land first and name you as the sender.

A confirmation is a snapshot, and it closes rather than run on values that no longer hold: *Review the transaction again: the relayer fee rose with network gas prices*, *the platform fee changed*, *the asset changed*, *your wallet account changed*. The fee rate is re-read every minute and again right before the transaction runs.

One transaction spends at most 2 notes, so a balance split over many small notes shows *Consolidate first by transferring to yourself*.

A confidential transfer can silently move nothing, so the result screen keeps a **Payout status** panel open until the pool has verified the outcome on-chain: *awaiting confirmation* becomes *confirmed*, and a TOKEN payout also needs its wrapper claim before the panel reads **Payout complete**. The relayer's keeper does this for you, normally within seconds. Two actions let you step in yourself: **Retry**, when an attempt moved nothing, and a claim button that names the token, such as **Claim USDC**, when a claim is still unpaid.

## Pay a shielded address

The **Transfer** page takes a shielded address (`pp-addr:`), a 0x address or an ENS name in its **To** field; the placeholder reads *0x, pp-addr:, or name.eth*. A shielded recipient is confirmed with *Private recipient · stays inside the pool*, and the payment never leaves the pool: no amount, no recipient and no token appear on-chain. A 0x or ENS recipient is a public payout, and pays the platform fee like an unshield; **Send it encrypted** pays them the eTOKEN instead of the plain token. History lists it as a transfer.

Your own shielded address is not refused. It consolidates: *Your own address: this consolidates your notes*.

To be paid, share your shielded address from the **Receive** dialog, which also offers a QR code and a payment link (`/transfer?to=` plus the address) that opens the Transfer page with the recipient filled in. [What stays public](https://docs.fluton.io/concepts/privacy-model.md) sets out what each kind of transaction still exposes.

## Pending deposits

An eTOKEN shield that stops half-way leaves its tokens in a receipt, listed under **Pending deposits** on the Shield page with its own state: *awaiting verification*, *ready to finalize*, *nothing received* or *refunding*. **Resume** authenticates the receipt and finalizes it into notes; **Cancel & refund** returns what the pool actually received, and that refund gets a payout status of its own. Only the depositor can do either, and the list is read from chain state, so it survives a reload or a move to another device.

## Unwrap an encrypted balance

An eTOKEN in your wallet, such as an unshield you kept encrypted, can be turned back into the plain TOKEN without going through the pool. On the home screen's **Wallet** card, **Unwrap** sits beside each encrypted balance once it is unlocked. You enter an amount, review it, and confirm twice in your wallet: the first transaction burns the eTOKEN into a claim, and once the burned amount is decrypted the second claims the TOKEN. Unwrapping makes the amount public.

If the run stops between the two confirmations, nothing is lost and nothing is unwrapped twice. The home screen then shows how much *is waiting to be claimed*, with a claim button that names the token, such as **Claim USDC**, to finish it. That reminder is kept in this browser.

## Scan for your notes

Your balance is not stored anywhere. The wallet rebuilds it by trial-decrypting the pool's note ciphertexts with your key, so one key recovers every note you own: deposits, change and payments received, of every token. The refresh control on the home screen, which shows when the balance was last updated, and **Refresh** on the Notes tab rescan, and the wallet rescans by itself after every transaction it sends.

When the deployment names an indexer, the scan reads it and verifies it against the pool before trusting it; otherwise it reads the chain in RPC-sized pages from the deployment block. An indexer cannot forge or steal a note, but it could hide one, which is why the scan verifies it against the pool and falls back to the chain when that check fails.

## View keys

A **view key** (`pp-view:…`) gives read-only access: balance, history and which notes are spent, but no way to spend. Reveal yours under **Settings** → **Private wallet** → **Back up & share**, confirm the warning, and it is shown for a minute before it blurs again. The spend key sits beside it, with a download that writes a backup file naming the chain, the pool and your shielded address.

**Use a different key** goes the other way. **Use a spend key** takes a `0x…` hex key and keeps it in this browser only. **Watch with a view key** opens the wallet watch-only; a pasted view key is never saved, so it is gone after a reload. [Keys and view keys](https://docs.fluton.io/concepts/keys-and-view-keys.md) explains the split between the two.

## History

The **History** page has two tabs. **Activity** lists the transactions you made from this browser, filtered by **All**, **Shield**, **Unshield** or **Transfer**, 10, 20 or 50 to a page. A payment to a public address is listed under **Transfer**. **Notes** lists every note your key can decrypt, newest leaf first, each marked *Spendable* or *Spent*, with the spendable count and the private balance of each asset above them. When an asset's notes are fragmented it says how much of that token one transaction can spend and suggests transferring it to yourself to consolidate. Both tabs ask you to unlock first, with a wallet signature or a saved key.

## Settings

The **Settings** page holds the **Private wallet** card: where the active key comes from (*Your wallet*, *Imported spend key* or *Imported view key*), whether it is *Unlocked*, *Locked* or *Watch-only*, your shielded address, and the keys panel described above. Below it, **Get more from Fluton** opens the **How Fluton works** tour and **Boost your share**, where referral bonuses are verified and activated.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.