Error Messages

Desktop maps backend errors to short codes in desktop-client/src/utils/errors.ts. CLI often prints the raw Rust message.

Wallet & auth

CodeMessageTypical cause
AUTH_001Incorrect passwordWrong unlock password
AUTH_002Please enter your passwordEmpty password field
WALLET_001Wallet is lockedUnlock before send/sync
WALLET_002No wallet foundCreate or restore first
WALLET_003Invalid recovery phraseBad mnemonic word or order
WALLET_005Wallet already existsCreate on machine that already has one

Send

CodeMessageTypical cause
SEND_001Insufficient balanceAmount + fee > spendable
SEND_002Invalid recipient addressNot a valid unified Orchard address
SEND_003Invalid amountNon-positive or unparsable amount
SEND_004Transaction failedRPC, proving, or expiry error

Network

CodeMessageTypical cause
NET_001Cannot connect to nodeZebrad down, wrong URL, RPC disabled
NET_002Request timed outSlow or overloaded node
NET_003Network errorGeneric fetch failure
NET_004Node unavailableRPC error from Zebrad

Sync & proving

CodeMessageTypical cause
SYNC_001Sync failedNode unreachable or scan error
PROVE_001Proving failedMissing or corrupt proving params

Backend

CodeMessageTypical cause
BACKEND_001Feature not availableTauri command not registered; rebuild app
RUNTIME_001Use desktop windowBrowser preview without Tauri IPC

CLI-specific messages

MessageMeaning
Failed to parse config.jsonInvalid JSON or UTF-8 BOM — fix config.json or upgrade (BOM stripped in current load_config)
Orchard witness is N blocks behindSync/witness catch-up required
nExpiryHeight / -25Transaction expired before broadcast — sync and retry
No spendable notes foundScan not run or wrong profile

Zebra RPC codes

nozy maps connect failures to structured codes via zebra_connect_api_code() for API clients. Use nozy test-zebra for a human-readable diagnosis first.


Fix guides: Common Issues | Zebra Node Setup