01
Keep a usable backup
Save an encrypted wallet backup, keep its password separately and confirm you can restore the correct address. Account email recovery does not replace this backup.
SECURITY
Protect the key.
Check the evidence.
Security depends on protected signing keys, authenticated network rules and verification of the accepted outcome. Each participant has a part to protect.
Product documentation · Edition 1 ·
WALLET SECURITY
Keep control of spending.
02
Check the destination
Verify the address and network with the intended recipient. Review the actual amount and fee before signing. Never approve a payment merely because an unsolicited message asks.
03
Protect the device
Use a trusted device and release package. Lock the wallet when finished and keep the local wallet port inaccessible from the public internet.
NETWORK SECURITY
Know what a proof establishes.
Authenticated roots and quorum assumptions
Verification begins with an authenticated genesis and policy root. Consensus and checkpoint signatures depend on their respective authorised thresholds. Compromise or collusion at those thresholds changes the security assumptions; multiple endpoints under common administration do not create independent trust.
Fresh state, rollback and conflicting history
Retain the verified head and require a valid continuation. Stale or inconsistent evidence must pause new spending rather than turn an old balance into fresh spendable funds. Keep conflicting signed evidence for diagnosis.
Privacy and public amounts
Payment verification uses public network records. Do not assume that an address hides transaction amounts or that repeated use cannot link activity. Keep personal and contractual details outside public records.
OPERATOR SECURITY
Protect signing state as well as keys.
- 01
Separate identities
Wallet, node connection, registration, validator and checkpoint keys have different permissions. Keep their storage and recovery procedures distinct.
- 02
Avoid duplicate signing
Do not copy an active validator identity or restore an old disk snapshot over its signing journal. A backup procedure must preserve the no-conflicting-signature invariant.
- 03
Update deliberately
Verify the release, stop the process safely and preserve local state. Follow an authorised membership change when replacing a voting key.
WHEN SOMETHING LOOKS WRONG
Preserve evidence. Contain exposure.
Stop issuing new signatures from a suspect device. Preserve the software version, time, network and payment identifiers and relevant public error messages. Keep private keys, passwords, encrypted backups and session tokens out of screenshots and public issue reports.
For an interrupted payment, inspect its original identifier before retrying. For suspected key compromise, recovery of account access is not proof that the spending key is safe.
Issue and recovery guidance →