Final Wallet User Guide
The essentials of using a Final Wallet: your identity, one address on every chain, sending intents, fees, recovery and post-quantum mode.
Last updated 2026-09-08 · maintained in the Final Wiki
The essentials, kept short. The wallet interface is being rebuilt around this guide, so it describes what the wallet does for you rather than which button does it. Details for the advanced views live in Recovery, guardians, inactivity and claims.
#Your identity is a certificate set
Your wallet is created from a certificate set: a post-quantum identity with a live stage and a recovery stage, each with a public half and a private half. The private halves stay with you, like a seed phrase: offline copies, never uploaded, never pasted. Your address on every supported chain is derived from that identity, so it is the same everywhere.
#One wallet, every chain
Every chain the Final network serves shares your address. The list comes from Final Chain's tree, with Pre-Final Chain built in — the wallet reads it rather than keeping one of its own. You can add a network yourself; one the Final network does not serve is marked Final DeFi unsupported chain. Every asset in the registry is listed on its chain by itself and cannot be removed; tokens you add sit beside them. Balances on the testnets are priced like their mainnet twins; an asset without a price yet (PHI before its listing) is shown as unpriced, not as a fault.
The wallet exists on a chain once it has been created there; creating it elsewhere is one action, taken on the wallet dashboard: Create on more chains in the extension's identity list opens the dashboard of your plane, which asks the extension for the chains, composes one plan and hands it back — you approve once, in the wallet, and it signs. Your first chain is paid for: the wallet is created on the first chain you choose, in the row that carries your first action, from a deposit at that chain's gateway that any wallet can pay — the extension's own EOA account, or a browser wallet on the dashboard's fund page (Final Wallet, MetaMask, Rabby, Coinbase Wallet, Brave Wallet, Trust Wallet, OKX Wallet, Rainbow, Zerion, Phantom, Frame; any other EIP-6963 wallet works untested). Sub-accounts are separate pockets under the same identity, each with its own address, for a protocol, a purpose or a person. A sub-account can pay its own fees from its own budget, a protocol can be bound to one under rules you accept and can leave, and a program acting for you — a bot, an automation, an AI agent — can be given a bounded allowance on one that never reaches your keys or your wallet. All of it: Sub-accounts, controllers and agents.
#Everything you do is an intent
An intent is a signed instruction to your wallet. Which road an account takes depends on what it is:
- A Final Wallet with a Final Identity sends intents only.
- A Final Wallet controlled by an owner key (not yet post-quantum) has a switch in Send: Intent, the default, or Owner transport — a standard transaction from the owner key to the gateway. The switch goes when the wallet turns post-quantum.
- An EOA account — the owner key on its own — is an ordinary account that sends standard transactions and pays its own gas. The rest of this guide is about Final Wallets.
For an intent you do not send the transaction yourself: the protocol carries it to the chain and shows you the fee — a ledger cost, not gas — before you sign. You choose how it executes:
- Now.
- After a second look, which lets you cancel before anything runs.
- At a chosen time. (With the release: the funds and fee are set aside when you schedule, and you can still cancel until 90 seconds before.)
- Privately (with the release): nobody, the operator included, can read it early.
Before execution, outsiders can see the target chain, the deadline and the schedule, never your address or the content. After execution the transaction is public on that chain like any other.
#Reading back what happened
Every intent has a status: pending, included in a block, executed, or why not (expired, cancelled, gas moved too far, or already executed with your row taking no effect). Launch Sale purchases show pending, admitted with the PHI amount, and delivered.
#Fees, briefly
A small fixed floor on every intent, a 10 % ledger surcharge (not gas), published prices for scheduling, cancelling and privacy. Holding PHI locked, on whichever chain you keep it, raises your tier on the particle ladder and discounts service fees. Fee your intent did not use stays on your deposit at that gateway and pays your next intent; floors are never returned. Details: Fees and PHI.
#If you lose access
Your recovery stage, the recovery authority or your own guardians can restore control after a period of inactivity and a delay. Funds left untouched for the inactivity period can be routed to a destination you chose, by default the protocol's vault, where they wait for your claim. Recovery cannot help against a stolen key; for that you rotate your keys — a separate path, live today, that does not wait for inactivity. All of it: Recovery and guardians.
#Final Chain, briefly
The records behind your wallet live on the state plane. Today that is the Pre-Final Chain, a temporary build that only the protocol writes to; Final Chain itself is still in development. When Final Chain is released, everything moves over and nothing changes for you.
#Post-quantum mode
New wallets start post-quantum. Older wallets can switch once, at any time; the switch cannot be reversed and closes the owner-key lanes.
#The extension (with the release)
The browser extension and the wallet dashboard are one wallet on two surfaces, the way MetaMask and its portfolio site work together. The extension holds the keys and the everyday wallet: accounts, balances, send and receive, activity, connected sites, the network, quick settings. The wallet dashboard of your plane (wallet.final-de.fi; test-wallet.final-de.fi in Testnet mode) carries the longer flows — creating the wallet on more chains, the fund page, identity details — and works with the extension as a site does: it asks, the extension shows the request for approval and signs; no key and no signature leaves the extension. The plane is one setting for both: switching Testnet mode in the wallet, or accepting a switch the dashboard asks for, moves everything at once, and your identity is registered on both planes so it is valid wherever the wallet points. The extension is downloaded from the wallet dashboard and nowhere else, and it updates through your browser's store; in Testnet mode it also offers a newer set from the wallet dashboard. It shows its version and the newest it knows of. A button in its header switches between the browser's side panel and a floating window; the toolbar button opens whichever you used last, and approvals always open as their own popups. Every link it opens lands on the wallet host, which resolves onward to the chain's explorer.
#Three rules
- Never share the private halves of your certificate. Nobody at Final DeFi will ask.
- Check the address you send to; an intent does exactly what you signed.
- Cancel scheduled or gated intents you no longer want; they otherwise run when their conditions are met.