Importing a wallet is also how you sign in: there is no separate account. If Zoide recognises the wallet you bring, you are signed in; if it does not, the account is created.
Every Zoide wallet has two keys
This surprises people coming from other wallets, and it is why some import forms ask for two things:
| Key | What it is for |
|---|---|
| Payment key | Holds and spends your BSV: it pays for purchases, fees and network costs |
| Ordinals key | Holds your pieces. Signing with it is what moves or sells a piece |
Separating them is the norm in the ordinals world: it means the key that spends money is not the key that holds your collection.
Each one has its own address, shown like this in your wallet — and the reason to always ask which address somebody means:
The six sources
| Source | What you provide |
|---|---|
| Zoide seed phrase | 12 words |
| WIF | Both private keys directly, payment and ordinals |
| Zoide JSON export | The file you get when you export from Zoide |
| RelayX | Its seed phrase |
| Aym | Its JSON export |
| SatOrdinals | Its JSON export |
With WIF, both keys are validated before anything else happens: if either is not a valid key you are told which one, and the import stops there rather than half-completing.
Whitespace and line breaks are trimmed from what you paste, because a copied key almost always drags a newline along and that alone would make a perfectly good key look corrupt.
Derivation paths
If you ever want to recover your Zoide wallet somewhere else, these are the paths. Publishing them is the point: a wallet you can only open in one place is not really yours.
| Source | Payment key | Ordinals key |
|---|---|---|
| Zoide (seed phrase) | m/0'/1/0 |
derived alongside it |
| RelayX (seed phrase) | m/44'/236'/0'/0/0 |
m/44'/236'/0'/2/0 |
| Zoide / Aym / SatOrdinals (JSON) | already in the file | already in the file |
236 is the BIP44 coin type for Bitcoin SV, so the RelayX paths are the standard BSV ones.
What happens after the import
Your keys are encrypted with the password you choose and stored in your browser. They are not sent to Zoide, not at import and not later. That is why:
- nobody at Zoide can move your pieces or spend your funds,
- nobody at Zoide can recover your wallet for you,
- and clearing your browser's site data deletes it.
Export it and keep the export somewhere safe before you put value in it. That sentence is the whole security model in one line.
Biometric unlock
If your device supports it, you can unlock the wallet with your fingerprint or face instead of typing the password every time. Two conditions:
- the site has to be served over HTTPS — it does not work on a plain local address, by design of the browser API and not of Zoide;
- it is an unlock, not a replacement: the encrypted wallet is still what it was, and the password still works.