Wallets

Tidecoin wallets differ in validation, key storage, recovery flow, and operational trust. Choose the wallet that matches the amount you hold and the work you need to do.

This section is not the protocol reference. For consensus details, use Protocol. For RPC schemas, use Reference.

Wallet comparison

Wallet	Best for	Validation	Key custody	Use for meaningful value?
Desktop Core	Full-node users, operators, developers, advanced recovery	Local full-node validation	Local wallet file, PQHD seeds encrypted by the wallet when wallet encryption is enabled	Yes, with backups and secure device practice
Browser Extension	Browser-based daily use	Remote or app-provided chain view	Local encrypted browser profile data	Small to moderate balances, depending on browser/device security
Android	Phone-based receive/send	Remote chain state	Local device wallet storage	Small to moderate mobile balances
Web Wallet	Quick browser access	Hosted web app and remote chain view	Client-side browser key material	Convenient for small balances; avoid treating it like cold storage
iOS	Native iPhone/iPad wallet	Planned	Planned	Not available yet

Recommended starting points

Use Desktop Core if you want maximum control, self-validation, RPC access, or infrastructure-grade behavior.
Use the Browser Extension when you need a browser wallet and understand browser-profile backup and malware risk.
Use Android for phone payments.
Use Web Wallet only after understanding its hosted app delivery and recovery model.

Configuration and operation

Using PQHD — manage post-quantum HD wallets.
Multi-Seed & Schemes — run multiple seeds with per-scheme policy.
Import & Export — move keys between wallets.
Security Model — what each wallet protects.
Migration from Legacy Wallets — upgrade pre-PQHD wallets.

Backup rule

Back up before receiving. For Core, the wallet backup is the primary recovery artifact; descriptors alone do not replace PQHD seed material. For lighter wallets, record the recovery phrase or export material shown by that wallet.