Wallet Product Guide
Use the Talero Wallet as a control plane for everyday funds, privacy, and guarded operations
Talero Wallet combines standard account management with guided sending, privacy tooling, security controls,
operational notifications, explainable decision screens, evidence downloads, treasury organization, recovery planning,
and mode-based advanced workspaces. The product is designed so that ordinary users can stay in familiar flows while teams
and operators can move into more specialized control surfaces when needed.
Web wallet
EOA
Smart Wallet
Enterprise
Validator
Live entry point
https://wallet.talero.info
The browser wallet is the main user interface for TLRO accounts, transfers, monitoring, and guided control flows.
How to read the wallet
Everyday pages stay focused on balances, receiving, and sending, while advanced pages add wallet-side policy,
review steps, evidence, recovery, and operator workflows when they are relevant.
Some actions can be delayed, queued, or require extra confirmation when the wallet sees higher cost, unusual destinations,
emergency controls, or additional approval requirements. Treat those states as part of the normal workflow rather than as an error.
Start here
Most users follow the same first-session pattern: open the wallet, unlock or create a vault, choose the mode that matches the job,
confirm the active network, and then move into the account or send screens.
| Step |
What happens in the wallet |
Best use |
| Open the wallet |
The login view appears before the main workspace and establishes the active local vault session. |
Use it as the primary way to access TLRO accounts in the browser. |
| Select a mode |
After login, the wallet presents mode-based entry points so users can stay in the right feature set. |
Start with EOA for ordinary use, then switch only when you need a specialized workflow. |
| Review the dashboard |
The dashboard summarizes network status, shortcuts, and the most relevant next actions for the active workspace. |
Use it as the landing page for the current session. |
| Open wallets or send |
Wallets covers account inventory and receiving, while Send covers transfer preparation and guarded execution. |
These are the two screens most users visit first. |
Good first-session routine: verify the displayed addresses, generate a fresh receive address when needed,
and use a small test transfer before moving larger value through a new workflow.
Workspace rule: the wallet keeps everyday, security, privacy, compliance, treasury, and recovery features
visible as separate pages so you can focus on the job at hand.
Modes and workspaces
Talero Wallet is organized around role-aware workspaces. The mode selector keeps the navigation relevant to the kind of account
and operational model you are using.
| Mode |
Main pages |
When to use it |
| EOA |
Wallets, Send, privacy pages, security pages, receipts, activity, notifications, diagnostics. |
Normal personal usage, day-to-day receiving, and standard outgoing transfers. |
| Smart Wallet |
Wallets plus guardian management and smart-wallet deployment. |
Users who want guardian-based recovery and a more programmable account model. |
| Enterprise |
Enterprise controls, treasury, review flows, exports, and policy-oriented surfaces. |
Teams that need stronger approval discipline and operational oversight. |
| Validator |
Validator operations, rewards, and role-specific operator actions. |
Operators managing validator-oriented wallet tasks. |
The shared pages such as Activity Center, Notifications, and Diagnostics stay useful across modes, while role-specific pages appear only where they add value.
Accounts and receiving
The Wallets page is the main place to create, import, inspect, and organize addresses stored in the encrypted local vault.
It is also where users confirm receive addresses before sharing them.
| Function |
What the wallet does |
Typical use |
| Create or import accounts |
Add addresses into the local wallet vault and make them available to the active mode. |
Set up a new wallet or recover an existing operational address. |
| Balance and transaction view |
Show current balances and recent account history in the wallet workspace. |
Confirm that the expected funds and activity are present before sending. |
| Fresh receive addresses |
Support receive workflows that reduce unnecessary address reuse. |
Share a new destination with a counterparty or public channel. |
| Stealth-oriented receiving |
Expose privacy-oriented receiving tools in the dedicated privacy pages. |
Reduce visible address reuse and improve inbound privacy hygiene. |
The simplest habit that improves both organization and privacy is to generate a fresh receive address when practical, especially for new counterparties.
Sending and approvals
The Send page is more than a transfer form. It combines destination review, amount and fee checks, approval prompts,
hold or queue states, and optional detail panels for more sensitive actions.
| Flow |
What the wallet shows |
Why it matters |
| Transfer preparation |
Source account, destination, amount, and fee context before final confirmation. |
Lets the user verify the exact action before submission. |
| Guarded send |
Fee review, destination review, risk hints, step-up prompts, or extra confirmations when required. |
Keeps unusual or expensive sends from looking identical to routine transfers. |
| Held or queued send |
Status can shift from immediate submission to hold, queue, or delay when policy or conditions require it. |
Preserves user intent while giving the operator or user a chance to review. |
| Transaction Capsule |
A prepared transaction can be turned into a capsule for later controlled execution. |
Useful when approval and execution should not happen in one click. |
| Rehearsal promotion |
Simulation-oriented flows can be promoted into an executable path after review. |
Provides a deliberate bridge between preview and action. |
If a send does not execute immediately, review the current status inside the wallet first. A queued, delayed, or held action often means a guardrail is doing its job.
Activity and notifications
Talero Wallet keeps operational context visible through the Activity Center, the Notifications page, and Diagnostics.
Together, those pages make it easier to understand what happened, what needs attention, and where a workflow originated.
| Page |
What you see |
Best use |
| Activity Center |
A cross-feature timeline with categories, feature filters, badges, and source navigation. |
Review recent execution, receipts, routing, privacy, treasury, and recovery events in one place. |
| Notifications |
Persisted critical notifications with read state, source links, timestamps, preferences, and test notification support. |
Track events that require acknowledgment rather than just passive browsing. |
| Diagnostics |
Backend, module, storage, and wallet diagnostics with shortcuts into related controls. |
Support, troubleshooting, and operator review of the current wallet environment. |
Unread badge: the shell highlights unread notifications so critical events remain visible even when you are working elsewhere in the wallet.
Source links: when available, notifications and activity entries link back to the page or workflow that created them.
Privacy tools
Privacy tooling lives in its own section of the wallet so users can improve on-chain hygiene without turning every transfer
into a specialist workflow.
| Tool |
What it does |
When to use it |
| Stealth |
Supports privacy-oriented receiving and inbox review. |
Use when you want to reduce address reuse and inbound linkability. |
| Privacy score |
Highlights the main drivers that are lowering privacy hygiene. |
Use it as a quick readout of current wallet habits. |
| Privacy Healer |
Turns privacy findings into a practical remediation plan. |
Use when you want concrete next steps instead of just a score. |
The privacy pages are most useful when they become routine: check the score, rotate receive paths where appropriate,
and apply remediation actions gradually instead of waiting for a perfect one-time cleanup.
Security controls
Talero Wallet separates security features by purpose so users and operators can apply only the controls they need.
Some controls act before execution, some shape approval behavior, and others create operational guardrails around the session itself.
| Control |
Main purpose |
How it appears in the wallet |
| Fee Guardian |
Prevent bad timing under hostile fee conditions. |
Can recommend waiting, hold a send, or change how a transfer is approved. |
| Route Autopilot |
Plan safer or more suitable routes for execution. |
Shows route planning details and can expose an explanation panel before execution. |
| Rehearsal |
Preview execution paths before acting. |
Produces an advisory report that can later be promoted into a capsule or controlled action. |
| Tx Guardian |
Apply pre-send warnings, holds, or hard stops. |
Shows explicit reasons when the wallet wants stronger review. |
| Contract Risk |
Inspect contract interactions before approval. |
Exposes contract-oriented risk findings and linked guardrail actions. |
| Freeze List |
Block or hold activity toward listed destinations. |
Appears as a dedicated emergency-list control surface. |
| Watchtower |
Manage timed panic windows and duress protections. |
Acts as the fast-access control page for emergency posture. |
| Duress Mesh |
Evaluate suspicious context and record overrides or check-ins. |
Shows scored context and an explanation panel when available. |
| Guardian Sessions |
Issue delegated session access with explicit scope and limits. |
Tracks created, rotated, and revoked sessions directly in the wallet. |
| Counterparties |
Attach local labels and heuristic scoring to known destinations. |
Provides a wallet-side memory layer for recurring counterparties. |
These controls are strongest when combined. For example, a send can pass through destination review, fee review, step-up confirmation, and a decision explainer before it is executed.
Decision explainer and honest review states
Sensitive workflows in the wallet can expose a decision explanation panel. That panel is designed to help users understand why an action was
allowed, delayed, queued, routed, blocked, marked partial, or flagged as sensitive.
| Layer |
What it represents |
How to read it |
| Final wallet explanation |
The summary the wallet presents to the user for the current action. |
This is the product-facing outcome to read first. |
| Wallet rules |
Local and backend-enforced wallet policy that shaped the outcome. |
Use this section to see which guardrails or workflow rules were active. |
| Node signals |
Technical advisory signals that can enrich context for the wallet. |
These help explain context, but they are not the final wallet decision by themselves. |
| Partial / precision / warnings |
Metadata that tells you whether the explanation is complete, approximate, or carrying extra cautions. |
If the wallet marks an explanation partial, treat it as an informed view rather than a complete one. |
Where users encounter the explainer
- Send and guarded transfer flows.
- Transaction Capsule review and execution context.
- Route Autopilot planning and supported execution paths.
- Duress Mesh evaluation screens.
Read the explainer as a structured review aid. It is there to clarify context, not to replace the user’s own approval step.
Receipts, attestations, and exports
The wallet includes evidence and export surfaces for support, audit, and controlled information sharing. These tools are grouped so that
users can reach the right level of detail without turning every workflow into a data-export task.
| Surface |
What you can produce |
Typical use |
| Receipts |
Finality receipts and settlement-oriented evidence. |
Share confirmation-oriented data with a counterparty or support process. |
| Attestations |
Reserve-oriented attestations generated from the wallet surface. |
Provide a structured statement for trusted review flows. |
| Compliance B2B |
Controlled audit-ready packages and filtered disclosure views. |
Prepare business-facing review material from the wallet. |
| Export buttons |
Activity, security, treasury, and inheritance JSON exports from their respective pages. |
Capture a snapshot for support, internal review, or follow-up analysis. |
Export pages surface the same honesty markers used elsewhere in the wallet. If an export carries warnings or partial metadata, the download area reflects that before and after the file is generated.
Treasury and recovery
Talero Wallet includes dedicated pages for treasury organization and continuity planning. These are kept separate from ordinary sending
so operators can work with buckets, rules, reviews, and recovery steps in a more deliberate context.
| Page |
What it covers |
Best use |
| Treasury |
Bucket organization, wallet-side rules, allocations, and treasury reports. |
Manage internal spending structure and oversight for larger holdings or team operations. |
| Inheritance |
Check-ins, trigger states, confirmations, and continuity planning workflows. |
Maintain a practical recovery and continuity process inside the wallet workspace. |
Treasury exports: the treasury page includes a dedicated export action so teams can capture the current wallet-side rule and allocation state.
Inheritance exports: the recovery page can export the current continuity plan view for controlled follow-up and recordkeeping.
Specialized workspaces
Beyond the everyday wallet, Talero includes dedicated workspaces for smart-wallet, enterprise, and validator-oriented operations.
Those pages are available when the selected mode makes them relevant.
| Workspace |
What users do there |
Who it is for |
| Guardians Smart Wallet V1 |
Manage guardian thresholds, recovery permissions, and related smart-wallet controls. |
Users operating a guardian-backed smart wallet. |
| Deploy Smart Wallet |
Deploy the smart-wallet contract set from a selected EOA. |
Users setting up a new smart-wallet instance. |
| Enterprise Controls |
Handle enterprise approval and multisig-oriented operations. |
Teams that need stronger control separation and review flows. |
| Validator Ops |
Manage validator-oriented wallet actions, staking-related steps, and rewards views. |
Operators working with validator-linked wallet responsibilities. |
Users who only need a normal wallet can safely remain in the EOA path and ignore these specialized workspaces until a real operational need appears.
FAQ
| Question |
Answer |
| Which mode should I start with? |
Start with EOA unless you already know that you need guardian recovery, enterprise approvals, or validator-specific tooling. |
| Where do I find the most important events? |
Use Activity Center for the cross-feature timeline and Notifications for persisted critical alerts that need acknowledgment. |
| Why does a send sometimes wait instead of submitting immediately? |
The wallet can queue, hold, or delay actions when cost conditions, approval rules, or other control surfaces recommend review before execution. |
| How do I understand a guarded decision? |
Open the decision explanation panel when it appears. It separates wallet-side rules, advisory signals, and the final wallet summary. |
| Can I export what I am seeing? |
Yes. Activity, security, treasury, and inheritance pages include export actions, and receipts or attestations are available on their dedicated pages. |
| Do I need every security feature enabled at once? |
No. The wallet is designed so you can adopt the controls that fit your workflow, then layer more review or approval steps as your needs grow. |