Wallets
Terminal has a wallet of its own. It is where your bots' money lives, and it is not the wallet you signed in with — that one only proves you hold a licence.
Open it from the wallet icon; it slides in from the right edge, over whatever you were doing.
Accounts and wallets — the two words
- An account is one recovery phrase. Everything derived from it can be brought back with those words alone.
- A wallet is one address. Either derived from an account — as many as you like, each with its own label — or imported on its own from a private key.
One Terminal holds several accounts, and the wallet panel groups them exactly that way: the account, that account's wallets, and separately anything you imported. The grouping is not decoration — it tells you at a glance which addresses your recovery phrase will restore and which it will not.
Creating your first account
Press Create account. Terminal generates a recovery phrase on your machine, from your operating system's randomness, and shows it to you once. You confirm it by typing words back, and it is then sealed on this machine.
Write it down on paper. Terminal will not put it on your clipboard — not once, not with a button — because a clipboard is read by every application you run.
Importing an account
Press Import account and type an existing recovery phrase into the box. Twelve or twenty-four words; Terminal checks the phrase and, if a word is wrong, tells you which position failed rather than just refusing.
This is import account, not import seed phrase, because what arrives is the whole account — the phrase and every address under it, present and future.
Adding wallets
The Add wallet bar sits at the bottom of the list and stays there while the list scrolls above it. It offers three things:
| A new wallet under this account | The next address derived from your recovery phrase. Restoring the phrase restores it |
| Import a private key | A standalone address, labelled imported everywhere it appears. Your recovery phrase will not bring it back — that key is the only copy |
| A new account | Its own recovery phrase, its own family of wallets |
Any wallet can be renamed. A label is local to your Terminal and is what you type in commands instead of an address.
The password — there is only one
The password you set when you first opened Terminal is the same password your wallet is sealed with. There is no second passphrase to remember. This is how MetaMask works, and the reason is the same: two passwords for one machine is not twice the security, it is one password people write down.
What follows from it:
- Changing your password re-seals everything — every account and every imported key — before anything else happens.
- You cannot remove your password while an account exists. Removing it would not open Terminal; it would close your wallet. Terminal says so before you press the button, not after.
- "Remember on this computer" opens the screen, not the vault. Nothing anywhere stores the password itself, so a remembered password still cannot decrypt a key.
- Revealing is asked for every time. Your recovery phrase and any private key are shown only after you type the password, however long Terminal has been open. Somebody who sits down at your unlocked machine gets nothing.
Underneath: your phrase and imported keys are put through Argon2id and encrypted with AES-256-GCM, then handed to your operating system's own secret store — Keychain on macOS, Credential Vault on Windows, libsecret on Linux. Both the machine and the person are needed. The plaintext never touches disk.
Sending and receiving
Receive shows the address and a QR code.
Send takes an amount, a token and a destination, shows you the whole transfer, and waits for you to confirm it in a modal. ERC-20 tokens on the chains the platform knows, and NFTs including the licence collections.
Balances read live. A balance Terminal could not read shows as —, never as 0 — a zero you believe is more dangerous than a dash you can investigate.
Locking
Locking Terminal clears the password from memory and pauses your bots, with wallet locked as the reason on screen. They resume when you unlock. This is not a limitation to work around: a bot that could trade while your wallet is locked would be a bot that holds your key.
What this wallet refuses
- Dapp connections. No injected provider, no WalletConnect as a wallet. It will not sign a transaction for a website.
- Contract calls beyond transfers and the platform's router. Including approvals: the router is the only thing it will approve.
- A send typed as text. Every transfer goes through the modal, where you can read it.