ReSatoshi Android full-node overview
===================================
Current preview: 0.1.20-preview; Android versionCode 38.

Server mode is the default, including upgrades. Optional full-node mode uses
on-device Resatoshi Core for local validation, balance/history lookup and
transaction submission. It never silently falls back to the server. Private
keys and signing remain in the app; Core stores public watch-only descriptors.

Core uses expiry index mode and a 1 GiB block/undo pruning target, not a total
storage cap. Initial synchronization downloads and validates historical blocks;
chainstate, expiry index and wallet caches need additional disk space. Recent
block retention can exceed the pruning target. Pruning does not weaken consensus
validation, but historical wallet recovery can require a fresh synchronization.

The foreground service is explicitly started by the user, has a persistent
notification, and does not auto-start at boot. Android may stop it. Server mode
works without running Core. Node deletion preserves app signing wallets; chain
resynchronization also preserves registered public Core wallets.

The notification title, status, channel name and Stop action use Android string
resources in nine languages, with English fallback. Korean is selected on a
Korean-language device; it is not forced for all devices. App interface messages
also follow device language. Translation catalogs intentionally retain Korean.

Build, pinned Core revision, RPC restrictions and recovery details:
FULLNODE-PROTOTYPE.txt. Change history: CHANGELOG.txt. Automated/native evidence:
FULLNODE-VALIDATION.txt. Physical-device observations and incomplete release
gate: DEVICE-VALIDATION.txt. Existing evidence is retained, not discarded.

Source review and emulator tests do not establish real-phone performance,
carrier reachability, successful backup recovery or production readiness.
