Web Wallet

tdc.cash  is Tidecoin’s hosted web wallet. It is designed for quick access without installing Tidecoin Core. Keys are generated and held client-side in the browser, access uses a nickname and password, and the wallet applies a flat 0.005 TDC transaction fee.

Use the web wallet for convenience balances. For larger balances, long-term self-custody, or independent validation, use Tidecoin Core.

This page is for users of the hosted web wallet. It is not the Core wallet or PQHD integration specification.

Access Flow

1. Open https://tdc.cash/ directly or from an official Tidecoin link.
2. Create or unlock the wallet with the nickname and password flow.
3. Complete the wallet’s backup or export step before receiving meaningful funds.
4. Receive a small test amount.
5. Send a small test transaction and confirm the fee and destination handling.

Bookmark the correct URL after verifying it. Do not follow wallet links from ads, direct messages, copied comments, or lookalike domains.

Backup and Recovery

A nickname and password are not a complete recovery plan unless the wallet’s documented recovery flow says so. Before using the web wallet for real funds, confirm what export or recovery material it provides and store that material offline.

If the wallet offers WIF export, Tidecoin Core can import WIF private keys with importprivkey:

tidecoin-cli -rpcwallet="main" importprivkey "<wif-private-key>" "web-wallet-import" true

If the wallet offers another format, test compatibility with Core before moving meaningful value.

Hosted-App Trust Model

Client-side key generation reduces custody risk, but it does not remove all web wallet risk. Each visit loads application code from the hosted site. A malicious or compromised site, phishing domain, browser extension, or local malware can still steal secrets or change transaction details.

Practical rules:

• verify the URL before unlocking;
• use a dedicated browser profile for meaningful balances;
• disable unnecessary extensions;
• keep only convenience balances online;
• move larger balances to Core or an offline signing setup;
• export or recover the wallet before relying on it.

Sending and Receiving

When receiving, use a fresh address if the wallet provides one and wait for confirmations appropriate to the amount. When sending, verify the destination, amount, and displayed fee before confirming. For a new recipient, send a small test transaction first.

The web wallet fee policy can differ from Core’s dynamic fee behavior. If a transaction is time-sensitive or unusually large, compare behavior with Core or a controlled node.

Moving Funds to Core

The simplest migration path is an on-chain send:

1. Create a fresh receive address in Core.
2. Send a small test amount from the web wallet.
3. Wait for confirmation.
4. Back up the Core wallet.
5. Send the remaining amount when you are satisfied with the result.

Use key export only when you understand the exact exported format and have tested Core import with a small amount.

See also: Import and Export Keys, Security Model, Desktop Core Wallet, Recover Your Wallet.