Get started in seconds: visit the app, enter a strong passphrase and an optional secondary code, and you have a working wallet without creating an account. The app derives your secret key locally using irreversible cryptographic hashing, and it never writes that secret to disk. Close or refresh the tab and your session disappears. For a reliable setup, choose a long passphrase (multiple random words) plus a short numeric/code add-on. Save them in a trusted password manager or memorize them; there’s no recovery email or seed phrase to bail you out.
Daily use is straightforward. To receive funds, open the app, unlock with your passphrase, copy your address, and share it. To send, paste the destination address, set the amount, review fees, and sign. The signature is created in the tab, so your secret stays on your device. You can also sign plain messages to prove address ownership for marketplaces or support desks. Because nothing persists between sessions, you’ll re-enter your passphrase whenever you return—quick, consistent, and predictable across devices.
Working on the go? Use it on any modern browser—your keys are re-derived on demand, so switching machines is painless. If you’re on a shared computer, open a private/incognito window, disable clipboard history, and close the tab when done; there’s no residual data left by the app. Security hygiene still matters: keep your device malware-free, avoid public Wi‑Fi when authorizing payments, and consider a dedicated profile solely for financial tasks. If your passphrase is the single point of access, treat it like a vault door: long, unique, and stored safely.
Power users can organize multiple accounts by pairing the same passphrase with different short codes (e.g., “spend”, “save”, “testnet”), producing distinct addresses on demand. This makes it easy to separate budgets, try features, or isolate risk without juggling exported files. Builders can generate deterministic keys for testing, sign payloads for integrations, and quickly validate flows without managing seed backups. Prefer tighter control? Load the app on an offline machine to sign data, then move signed outputs to an online device via copy‑paste. The core workflow is consistent: derive locally, act, and leave no trace.
Comments