ReSatoshi Wallet recovery contract — version 1 (existing wallets)

Network: Resatoshi mainnet, never Bitcoin.
Genesis: 0000000379813245fcdd4600969c6f74684f14433badf837be5b8ffa560174ec
Phrase: English BIP39; generated wallets use 24 words (256-bit entropy).
BIP39 passphrase: NFKD-normalized, case and leading/trailing spaces preserved.
Use the exact chosen passphrase; empty is a different valid wallet. Back it up.
Account derivation: m/84'/19333'/0'
Receive branch: account/0/index. Change branch: account/1/index.
Script: native SegWit P2WPKH. Address HRP: rsat (not bc).
Extended-key version: standard xpub/xprv; this alone does not identify the network.
19333 is a fork-local coin type convention, not a registered SLIP-0044 allocation.

Recovery discovery in the current app
Receive: stop after 20 consecutive unused addresses, cap indices 0..1999.
Change recovery: scan all indices 0..1999, including unused gaps. The QR signer
accepts those indices; full recovery must find every accepted change destination.
Full recovery runs only for initial synchronization (without valid account-specific
discovery hints) or when Full recovery scan is selected. Elapsed time, clock
rollback and a tip below the last full scan do not trigger full recovery.
Missing, invalid or foreign hints require initial synchronization again; valid
hints never expire. Public hints never replace live balance queries.
Normal refresh rechecks each branch from index 0 through the highest historically
used index plus 20 addresses, extending while another used address is found.
It does not search arbitrary unused gaps beyond that window. If another device
uses a distant change index, run Full recovery scan to find it immediately.
Receive still uses gap20/cap2000; this is not arbitrary-gap receive recovery.
A gap-only replacement for full change recovery is NOT compatible with this
contract. Addresses outside these bounds require a compatible recovery tool.
Derivation, accepted paths and full recovery coverage remain unchanged.

Also record: this document/version, first receive address for comparison, whether
a BIP39 passphrase was used and the separate wallet/backup password if enabled.
The wallet password protects storage and encrypted backup files. It does not
change addresses and is not the BIP39 passphrase. If only an encrypted backup
survives, its wallet password is required. A phrase plus its BIP39 passphrase can
rederive keys independently of that backup file, within the discovery rules above.
Never put your actual phrase, passphrase, password or xprv in Git or issue reports.

Interoperability
Core wallet files are not BIP39 recovery phrases. Switching to coin type 0 does
not automatically import an existing Windows/Core wallet. Core pairing needs its
actual receive/change descriptors, key origin and supported script/network rules.
QR pairing is currently the versioned resatoshi-watch / resatoshi-psbt /
resatoshi-signed envelope transported by rsatqr1 fragments, not BC-UR.
Do not change derivation, normalization, network, script or discovery semantics
without reviewing existing recovery vectors and a migration/import design.
This contract is normative; historical implementation notes do not override it.

Android interrupted operation handling (internal build37)
The metadata database must never be automatically discarded when it cannot open.
Storage errors block operations until repaired; do not clear app data to work
around them. Keychain retains signing wallets separately. Keep recovery backups.
Notification-shade focus loss closes sensitive screens and cancels prepared
work, with narrowly scoped native authentication/document exceptions. A node
running marker detects missing clean shutdown across restarts; users start the
node explicitly so Core can validate/recover its own storage. It never causes
automatic chain deletion. TXID journals and chain/deletion journals remain in use.
