ReSatoshi Wallet Android preview — user guide

Create or import
Install the latest preview as an update without clearing app data. Set an Android
screen lock. Create with device SecureRandom, enter 128 physical die rolls, import
BIP39 words, or restore an encrypted backup. Record the recovery contract and
phrase offline. If enabled, back up the exact BIP39 passphrase separately.
A wallet-file password is separate and protects stored/exported secrets.

Connect and receive
The app connects automatically to the project service over verified TLS.
No hostname or port entry is needed. Compare the receive
address before sending a small test amount. Unconfirmed incoming payments are
provisional, excluded from spendable balance and may disappear or be double-spent.
Even confirmations can be reversed by a 51% attack/reorganization.

Address search and recovery
Initial connection searches the full supported change range. Later refreshes
recheck previously used ranges plus 20 next addresses and always query current
balances/history. There is no daily or time-triggered full scan. If another wallet/device used a
distant change index or funds seem missing, select Full recovery scan in wallet
Settings or the watch-only screen. Receive recovery still requires gap20 within
indices 0..1999. The public discovery cache is optional, not a wallet backup.
The watch-only screen shows when the last full change-address search ran.
The balance screen shows transaction history directly below Refresh. Use Full
recovery scan in wallet Settings when needed: a quick refresh can miss distant
change first used by another device.
The displayed scan time is local search metadata, not proof of a correct balance.
Balances and confirmations are reported by the service. The app checks TLS,
network identity and transaction contents but does not independently validate
the chain or prove transaction inclusion.

Send
Refresh, enter/scan recipient, amount and fee rate, review address/amount/fee,
then authorize with device authentication. The app does not implement fee bumping
or guarantee settlement. Check history before retrying an ambiguous broadcast.

Two-device QR workflow
Keep the signing phone disconnected from all networks for actual airgap use.
Sign transaction QR / Export public key -> Export watch-only public key to online
phone. On the online phone choose Watch-only wallet / Connect with public-key QR.
Scan every fragment and compare both first receive addresses before saving.
Online: prepare unsigned QR -> offline: review/sign -> online: scan signed QR,
review and broadcast. No private key is transferred. Physical phone validation
is still pending; no generic hardware-wallet/Core QR compatibility is claimed.

Privacy and help
Read Privacy and data handling before unlock or under Settings, and ../PRIVACY.txt.
Read ../SECURITY.md before reporting issues. Do not share secrets, real backup
files or identifying wallet data. Preview guidance is not a production-service
privacy policy or guarantee. See THREAT-MODEL.txt and DEVICE-VALIDATION.txt.

0.1.16-preview update: Android language settings select English, Korean, Chinese
(simplified), Japanese, Vietnamese, Thai, French, Spanish or Russian. Recovery
phrases and names are not translated. Long-press a wallet card to rename/delete
only that wallet. Existing device authentication remains enabled unless changed.
There is no offline send queue. Closing the wallet or backgrounding before
broadcast cancels pending sending; already broadcast transactions are unaffected.
Inquiries: tpa1995@naver.com . The in-app email button opens your email app;
the visible address can also be copied. Never submit wallet secrets.

0.1.17-preview update: restore independent payment-monitor and balance/send
connections. Refresh and sending start with a fresh verified project connection.
Wallet data, backup phrases, addresses and language settings are retained.

0.1.18-preview update:
- To remove a wallet password: open the wallet, go to its security settings,
  enter Current wallet password and select Remove wallet password. Confirm the
  change, then reopen. Device authentication remains as configured. This does
  not remove passwords from previously exported backup files.
- Transaction IDs have a signed amount on the right: green is a net increase,
  red is a net decrease including fees. Self-transfers normally show only the
  fee as a decrease. Amount details load after the balance; a dash means they
  could not be verified/retrieved. Unconfirmed status remains visible separately.
- An Opening wallet indicator is displayed before password/account work.

Unreleased source improvements (2026-10-22):
- Finish the current wallet operation before changing another setting. Password,
  device-authentication, deletion and sending operations cannot run concurrently.
- Changing device authentication at the 100-wallet limit and retrying an
  interrupted change preserve the wallet list and the other wallets.
- A slow cloud backup provider no longer blocks the app UI. File-provider work
  may still take time; another backup operation waits until it finishes.

Remove local node data (0.1.20-preview, internal build34)
At the bottom of connection-mode settings, choose Delete local node data and
confirm. The app closes wallet sessions, saves server mode, stops the node and
removes downloaded/validated node data and public node caches. Wallet keys,
recovery phrases and submission records remain. The operation does not start
a new download. Reusing full-node mode requires a fresh initial synchronization.
Chain resynchronization is separate and retains public Core wallets for recovery.
