USDT WALLET DESKTOP BUILD

Docs · Product & Technical

Documentation for keys, multisig, and secure operation.

This documentation explains how to install the desktop wallet, create and secure single-sig and multisig wallets, route transactions with FREE Gas (Energy), operate in offline or constrained environments, and understand the security model behind local keys.

Docs updated · Oct 14, 2025 Desktop app · Windows · macOS · Linux
DOCUMENT STRUCTURE

1. Overview & scope

This page is the entry point into the docs. It gives you a mental model of the app, how it stores keys (including multisig setups), and which parts of the system talk to the network.

This documentation covers:

  • Installing the desktop app on Windows, macOS, and Linux.
  • Creating wallets, securing seeds, and restoring from backups.
  • Configuring single-sig and multisig wallets and understanding their trade-offs.
  • How FREE Gas (Energy) routing works and when it is applied.
  • Operating in online, constrained, and fully offline environments.
  • The high-level security model and how it relates to your threat model.

For legal details on how we treat data, see the Privacy Policy. For service terms and acceptable use, see the Terms of Use.

2. Installation & first run

USDT Wallet is a native desktop app. There is no browser extension, mobile app, or hosted cloud wallet – everything runs locally on your machine.

2.1 Download & verify

Always download the app from the official website or from a link you can verify:

  • Go to https://tetherwallet.to and navigate to the Download section.
  • Select your platform (Windows, macOS, or Linux distro).
  • Verify the checksum or signature against values published in the changelog.

On Linux, prefer the AppImage or .deb/.rpm builds signed with the official USDT Labs key. In air-gapped setups, transfer installers on trusted media only.

2.2 First launch

On first run, the app will:

  • Ask you to select a UI language and basic appearance (light/dark, font size).
  • Offer to create a new wallet or restore from a seed or encrypted backup.
  • Explain the default security posture and where data is stored locally.

Telemetry and crash reports are off by default. You can enable them later from Settings → Privacy & telemetry.

3. Core concepts

Before you move real funds, spend a few minutes on the vocabulary the app uses.

  • Vault: Encrypted local container that stores keys, seeds, and metadata.
  • Wallet: A named collection of addresses and policies inside a vault.
  • Multisig wallet: An M-of-N policy where multiple cosigners must approve a transaction. See the multisig guide for a step-by-step example.
  • Profile: User-level settings such as language, networks, and UI preferences.
  • FREE Gas (Energy): Routing layer that subsidizes network fees for eligible transfers.
  • Workspace: Optional separation for testnets, QA, or staging funds.

Minimal mental model

Think of a vault as the safe, a wallet as an account inside that safe, and profiles/workspaces as the view you use to look at them. Multisig wallets add an approval policy on top of this: several people or devices must sign before funds move.

4. Keys, backups & recovery

The app is non-custodial. If you lose your seed phrase and all backups, we cannot restore your funds.

4.1 Creating a new vault

When you create your first wallet, the app will:

  • Generate a new seed phrase locally using a secure RNG.
  • Derive keys and addresses from that seed; the seed never leaves your machine.
  • Encrypt the vault using your passphrase and OS keychain / secure storage.

You will be asked to confirm the seed phrase. Do this carefully on a device and network you trust; do not store screenshots in cloud albums or messengers.

4.2 Backup strategies

We recommend a layered approach:

  • Primary: Write down the seed phrase on paper or metal, store in a physically separate location from your device.
  • Secondary: Export an encrypted vault backup to offline storage (USB, encrypted disk image). This includes your wallet metadata and multisig policies.
  • Operational: Use a smaller “hot” wallet for day-to-day funds and keep most funds in a vault you open less often.

4.3 Recovery walkthrough

To restore a wallet on a new machine:

  1. Install the app and launch it.
  2. Select Restore existing wallet.
  3. Choose whether you restore from a seed phrase or encrypted backup file.
  4. Enter your seed / load the backup, then set a new local passphrase.

Recovery uses the same derivation paths as initial creation; balances and labels will re-appear after the app syncs with the network. For multisig setups, make sure all required cosigners (or their backups) are also available.

5. Daily operations

Most users spend 99% of their time on a small set of actions: checking balances, receiving funds, and sending transactions.

  • Checking balances: The Overview screen aggregates balances across wallets and accounts.
  • Receiving funds: Share receive-only addresses or QR codes; do not share your seed or private keys.
  • Sending funds: The send flow shows fees, routing, and final confirmation before broadcasting.
  • Multisig approvals: For M-of-N wallets, additional cosigner approvals are requested before a send is finalized.
1. Select wallet and account.
2. Paste or scan the recipient address.
3. Enter amount and (optionally) a memo or label.
4. Review fee / FREE Gas routing details.
5. Confirm with your local passphrase (and collect multisig approvals, if required).

6. Network & FREE Gas routing

FREE Gas (Energy) routing is designed to reduce friction for routine transfers without giving us control over your funds.

6.1 What FREE Gas can and cannot do

Can Subsidize or optimize network fees for supported transfers.
Cannot Move funds without your explicit, locally signed transaction (single-sig or multisig).
Selection Choose between multiple routes (direct, relayed, batched) based on cost and latency.
Controls Per-wallet toggles and advanced overrides in Settings → Network & Routing.

For a deeper dive into endpoints, trust boundaries, and routing policies, see Networking & endpoints.

7. Offline & air-gapped flows

In high-security setups you may want one machine that never touches the network. USDT Wallet supports an offline signing workflow for this.

7.1 Typical offline setup

  • Online machine: Prepares unsigned transactions and broadcasts signed ones.
  • Offline machine: Holds the keys and signs transaction payloads.
  • Transfer medium: USB drive, QR codes, or another agreed offline channel.

The offline machine never needs to access the Internet. Keep its OS and the app updated via trusted, verified installers only.

7.2 Signing flow (high-level)

  1. On the online machine, create a transaction and export a signing pack.
  2. Move the pack to the offline machine.
  3. On the offline machine, review details and sign the transaction.
  4. Move the signed payload back to the online machine and broadcast.

8. Security model (overview)

The objective is defense in depth: compromise of a single layer should not be enough to drain funds.

  • Keys and seeds are generated and stored locally, encrypted at rest.
  • Multisig policies can distribute signing authority across multiple devices or people.
  • Network communications use TLS and can be pointed at your own infrastructure.
  • Least-privilege defaults: the app requests only what it needs for core wallet functions.
  • Build pipeline focuses on reproducible, signed binaries.

For a more formal threat model and hardening checklist, see the dedicated Security model page.

9. Telemetry & privacy

You control whether diagnostic data is sent. The app runs fully without telemetry.

  • Default: Telemetry and crash reports are disabled.
  • When enabled: Only high-level environment and usage signals are sent.
  • Never included: Seeds, private keys, passphrases, or full transaction payloads.

The exact legal framing of what we collect and why is described in the Privacy Policy.

10. Troubleshooting

Common issues usually fall into three buckets: connectivity, local state, or OS-level permissions.

10.1 Checklist

  • Ensure your system clock is roughly correct; large skews can break TLS.
  • Check that firewalls or VPNs are not blocking outbound connections to your node or defaults.
  • Try switching networks (home / office / mobile tethering) to isolate connectivity problems.
  • As a last resort, create a fresh profile and re-import your vault to rule out local UI state issues.

If you need to contact support, avoid sending screenshots that reveal full addresses or balances. Describe symptoms and environment; we’ll ask for details if needed.

11. Release channels & updates

You can choose between stable, beta, and (optionally) nightly builds depending on your risk appetite.

  • Stable: Default channel for production use and larger balances.
  • Beta: Early access to features; more frequent updates.
  • Nightly (opt-in): For contributors and QA only.

Updates are checked from within the app and compared to signed release metadata. You can also subscribe to release notes via email and RSS from the main site.

For the exact legal terms around updates and distribution, see the Terms of Use.