2026-11-08 documentation and interface review (unreleased source changes)
- Record owner-reported successful phone send and uncertain carrier/peer
  observations without marking formal release-gate cases passed.
- Reconcile fork/full-node decisions and superseded freeze wording; add a short
  full-node overview and separate historical notes from the build guide.
- Use the existing English translation key for connection-mode parse errors.
- Confirm Android foreground notification uses device-language resources.
- No APK rebuilt, versionCode changed, Core pin moved or release tag created.

0.1.20-preview transition edge cases (2026-11-07, versionCode38): deliver
visibility events for every distinct AppState/focus change, including background
after an earlier blur; suppress duplicate identical events. Track the live node
service and reserve startup before dispatch so old service teardown cannot
silently swallow a new start/rebuild request. Keep stopping state until service
teardown and child exit finish. Refuse premature/duplicate starts with localized
retry guidance; roll back the reservation on dispatch failure. Serialize deletion
intent invalidation and exit/teardown state with startup reservation. No queued
background restart, consensus change or wallet-storage migration. Version name
unchanged. Add targeted visibility and native lifecycle-gate regressions.

0.1.20-preview interruption safety (2026-11-07, versionCode37): patch Android
AsyncStorage to retain databases on open retry, corruption and unsupported
upgrades. Verify the patch before packaging. Add shared active-window/focus
tracking; notification-shade blur locks wallet/setup screens and invalidates
prepared sends synchronously. Preserve credential/document activity exceptions,
but require foreground window focus before using their results. Guard QR signing,
security changes and wallet-management writes with the same visibility state.
Commit a node-running marker before Core starts; clear only after a requested
stop confirms child exit. Retain unexpected-stop evidence across process death
and show a separate localized explanation on the next app launch. Serialize
child-exit state updates with startup/deletion. No automatic chain deletion or
background restart. Signing keys, transaction format, Core binary, dependency
versions and version name remain unchanged.

0.1.20-preview email inquiries (2026-11-07, versionCode36): replace the
privacy-screen repository Support link with Send inquiry email in all9 supported
languages. Display the selectable address tpa1995@naver.com and open its mailto
link. No email is sent automatically and no wallet data is attached. Keep
existing privacy/license guidance. No dependencies, wallet/node behavior or
version-name changes.

0.1.20-preview deletion flow simplification (2026-11-07, versionCode35):
distinguish successful native deletion with optional registration-cleanup failure
from actual preference/shutdown/deletion failure. Persist server selection before
destructive work. Shorten the settings caption while preserving the full final
confirmation. Share one lstat-based file deletion primitive between chain
recovery and full node removal; retain separate root policies and journals.
Use a timed startup lock with one30-second shutdown deadline established before
queueing, so startup-lock waits do not run outside the timeout or reset its
budget. File deletion itself is not subject to the shutdown timeout. Add outcome
boundary tests and native contention/expired-deadline fixtures. No key handling,
consensus binary, dependencies or version-name changes.

0.1.20-preview local node data deletion (2026-11-07, versionCode34): add a
confirmed destructive action at the bottom of connection-mode settings. Unmount
wallet sessions and persist server mode before stopping Core and deleting only
the isolated node directory and public-address cache. Keep signing wallets,
recovery phrases, account discovery state and submission records. Remove only
local Core registration flags after success. Wait for the child process to exit;
never delete while it is alive. Block starts during deletion and invalidate
queued start/rebuild intents. A durable fixed-root deletion marker resumes
partial cleanup before any future Core start. Never follow directory symlinks.
Delete public Core wallet databases too; this action does not download a new
chain. Reuse requires initial synchronization and public-wallet registration.
All new confirmation/progress/outcome text supports the existing9 languages.
Version name remains0.1.20-preview. No dependency or consensus changes.

0.1.20-preview fast local-wallet reopening and distribution notices
(2026-11-07, versionCode33): persist only public script/path hints in atomic
app-private files, outside AsyncStorage and chain recovery data. Reopening and
refresh reuse the index; actual UTXOs are still rederived and live Core balances,
raw transaction provenance and chain identity verified. Full recovery explicitly
rebuilds; missing, invalid or mismatched hints safely rebuild. Never persist
balances or private keys in this cache. Read independent UTXOs two at a time and
deduplicate raw transaction reads within each scan. Server mode is unchanged.
Audit actual Android runtime and bundled dependencies; supplement original
notices and include MPL-covered Public Suffix List preferred source in the APK.
Add reviewed-inventory build checks. See LICENSE-REVIEW.txt. Version name stays.

0.1.20-preview interface language review (2026-11-07, versionCode32): route
connection-mode and preference-recovery UI through localized Text/Alert. Add134
fixed messages for node state, recovery, peer health, submission outcomes,
privacy and native errors in all9 supported languages. Keep English fallback
for unsupported device tags. Translate accessibility labels and native node
notification resources. Preserve numeric counts, TXIDs, file names, user wallet
names, secrets and raw diagnostic/legal text. Recognized connection-mode safety
messages are no longer replaced with generic network errors. Keep the existing
license inventory/list structure; preserve every package notice and add embedded
Core COPYING verbatim to project attribution. No runtime translation service,
dependency or Core/transaction/storage logic changes. Version name unchanged.

0.1.20-preview destructive chain resync (2026-11-07, versionCode31): user-
requested chain recovery deletes obsolete chain caches instead of archiving.
Delete blocks, chainstate/snapshots, indexes, mempool cache, corruption latch and
old chain-quarantine copies. Preserve public wallet databases, descriptors,
private keys, recovery phrases and submission records. Commit/validate the
allowed deletion plan first; resume partial deletion before Core starts and
stop on deletion failure. lstat prevents following cache symlinks into wallets.
Resume legacy move journals safely. Check free space after cleanup. Update the
confirmation to explain irreversible deletion. Core consensus binary unchanged.

0.1.20-preview node status wording (2026-11-07, versionCode30): replace
ambiguous stopped/failed labels with local-node off, error interruption, and
Android background-timeout messages. Show server-mode reassurance only for a
healthy off state; fullnode mode shows how to start synchronization. Persist
observed timeout/start/exit failure details across reopening, clearing them on
an explicit new start. Unknown OS termination causes are not labelled timeout.
Version name, Core binary, validation and transaction handling are unchanged.

0.1.20-preview submission safety (2026-11-07, versionCode29): persist the
expected TXID before server/local broadcast, preserve it on lost/malformed
responses and crashes, and block new transactions until explicit user review.
Journal is keyed by public account identity across modes and watch/hot views;
no private keys or signed hex are stored. Confirmed transport success clears
it; pre-submission failures clear only their own marker. Unknown outcomes never
trigger automatic retries or a new transaction. Acknowledgement does not cancel
an existing transaction or prove it was never relayed. Mutations are exclusive.
Invalidate the payment revision when node readiness is lost or session closes;
recheck after authentication and immediately before transport submission.
Core binary, consensus and existing authentication remain unchanged.

0.1.20-preview payment-flow polish (2026-11-07, versionCode28): run local
chain/connectivity/tip-age preflight before requesting PIN/biometric payment
authorization. Keep session/activity checks and repeat readiness/mempool checks
before actual send. Clarify that recovered connectivity or tip/clock conditions
are re-evaluated automatically; no transaction is sent automatically. Retain
two-hour policy, connection count and Core binary. Version name unchanged.

0.1.20-preview peer-health checks (2026-11-07, versionCode27): show peer
connection loss, unknown tip time, stale tip (over two hours), and clock-skew
warnings in fullnode wallet/watch screens and node settings. Local balance reads
remain available. Recheck network and tip age before mempool validation and
immediately before transaction submission; fail closed without server fallback.
Delay is not proof of an attack, and local submission is not proof of relay.
Retain maxconnections=8, Core binary and consensus rules. Correct SECURITY.md
for server versus fullnode trust. Version name remains 0.1.20-preview.

0.1.20-preview simplification (2026-11-07, versionCode26): preserve all527
license notices verbatim in231 identical-text groups; load only on demand and
render a virtualized collapsed list with one expanded document. Move licenses
to global Settings so no wallet unlock is needed. Remove the unused duplicate
Android asset. Share one subscriber-driven node status loop and select only
readiness for wallet consumers; no polling with no interested consumers. Ignore
stale/cancelled results and force fresh status after lifecycle actions. Create
each wallet backend once per session and remove unused declarations. Enable
noUnusedLocals/noUnusedParameters. Network/signing/storage/native recovery and
Core binary are unchanged. Version name remains0.1.20-preview.

0.1.20-preview BlueWallet upstream integration (2026-11-07, versionCode25):
merge upstream master c4874c5aad91a72b8df7e3c72407456c07a47ffe, including the
security library updates bitcoinjs-lib7.0.5 and bip39 3.1.2. Match RN0.88.1,
React19.3.0, codegen/Metro/Gradle plugin, Gradle9.4.1, SDK37 and NDK28.2 while
retaining the minimal Resatoshi dependencies and Android source set. Adapt the
React host/PackageList API and upstream legacy TypeScript condition; remove the
unsupported StatusBar backgroundColor prop. Refresh camera fork and SVG pins
and bundled notices. Full-node mode remains optional, with the same Core binary,
keys, addresses, backups, application ID and signing certificate. Version name
stays 0.1.20-preview. See UPSTREAM-INTEGRATION.txt for verification details.

0.1.20-preview detailed review fixes (2026-11-07, versionCode24): distinguish
pruned-history/unknown RPC failures from explicit corruption before replacing
a public wallet cache. Corrupt per-wallet repair records are preserved and
rewritten after live DB validation. Corrupt historical-scan proofs are preserved
and reset without moving the chain; a persistent scan epoch invalidates old app
completion markers. Pending chain-move journals still fail closed if unreadable.
Remove the redundant public-descriptors.json cache from the production path.
Unify service shutdown around its owned process, finish the foreground service
promptly on timeout, preserve startup errors, and prevent overlapping Core use.
Cancel wallet operations when local readiness is lost; check cancellation after
the final header RPC before returning a snapshot. Version name stays 0.1.20.

0.1.20-preview public-cache isolation (2026-11-07, versionCode23): Core starts
without wallet autoloads and with P2P paused. Each public wallet cache loads
independently; invalid caches are journaled and quarantined with all sidecars,
then recreated as blank, private-key-disabled descriptor wallets. Their old
scan attestations are invalidated before replacement. Opening the affected
account must register descriptors and complete historical discovery; pruned
history still requires fresh-chain recovery. Healthy wallets remain usable.
Transport failures and unsupported loaded wallet types do not move databases.
Old quarantined data is retained. App signing storage is unchanged.

0.1.20-preview review fixes (2026-11-06, versionCode22; version name retained):
refused pruned historical scans preserve an already valid registration; public
script derivation yields in batches and is cached per wallet session; manual
chain recovery journals/quarantines only chain data and the corruption latch,
loads and verifies actual public wallets with P2P paused, then synchronizes a
fresh chain. Recovery proofs persist across restart. App signing keys and Core
public wallet databases are preserved. Older chain caches remain quarantined.

0.1.20-preview (2026-11-06, versionCode21): server mode remains the initial
and upgrade default. Optional full-node mode routes hot/watch-only wallet
queries and broadcasting to the on-device index-mode pruned Core node.
Public descriptor wallets only; signing and existing backups remain in the app.
Mode changes close sessions and prepared payments; local failures do not fall
back to server queries. Registered public wallets load at node startup.
Interrupted imports are not treated as completed scans. Pruned recovery needs
explicit full reindex with descriptors registered before rebuilding. Local
history is capped at the latest 1000 entries; balance uses all available UTXOs.
See FULLNODE-PROTOTYPE.txt and FULLNODE-VALIDATION.txt for scope and evidence.

0.1.19-preview UI follow-up (2026-10-22): remove the sync-status notice, last
full-scan time and duplicate Full recovery scan action between Refresh and
transaction history on the hot-wallet balance screen. Wallet Settings retains
Full recovery scan. Discovery policy is unchanged.

0.1.19-preview (2026-10-22, versionCode20): distinguish the current build from
yesterday's 0.1.18-preview. Includes the review fixes and initial/manual-only
full recovery policy below. Package and Android version metadata updated;
key derivation, application ID, signing identity and backup formats unchanged.

Discovery policy change included in 0.1.19 (2026-10-22): full change-address search runs
only on initial synchronization (no valid account discovery hints) or explicit
Full recovery scan. Remove daily expiry, clock rollback and lower-tip triggers.
Valid hints survive restarts without expiry. Current live balance/history reads,
receive gap20, full change0..1999 coverage and backup formats remain unchanged.

Review fixes included in 0.1.19 (2026-10-22, based on 0.1.18-preview): shared per-wallet
operation lock across password changes/removal, device-auth policy, rename,
deletion, balance refresh and sending. Overlapping work is rejected, not queued
with stale credentials. Security changes re-read the original credential before
commit; management operations also check component lifetime and foreground.
Protection migration/rollback at the 100-wallet limit excludes its temporary
credential from interrupted-addition discovery, retaining the real 100-wallet cap.
Android document-provider I/O runs on a dedicated worker, not the activity UI
thread; the pending operation remains exclusive until completion or invalidation.
Balance/watch-only/payment screens disclose server-reported status. Balance and
watch-only views show the last full change-address scan; the hot-wallet balance
view also offers Full recovery scan. All nine UI languages are supported.
No independent chain-validation claim, recovery-bound/format change or backend
deployment is part of these fixes.

0.1.18-preview (2026-10-21): current-password-verified password removal, preserving
wallet keys, passphrase and Android keychain target/authentication policy. Existing
backup file passwords do not change. Transaction history shows verified wallet
net change, green positive/red negative, including outgoing fees and owned change;
amount details use two background readers after balance discovery. Missing details
show a dash instead of a guessed zero. Wallet opening yields a frame for its loading
overlay before password KDF/account derivation. No KDF weakening, balance policy,
connection sharing, receipt ownership, recovery-bound or server-setting change.

0.1.17-preview (2026-10-21): restore separate receipt-monitor and balance/send
connections, including fresh verified connections per lookup/send as in 0.1.15.
Monitor retry/unmount closes only its own socket. Retain 0.1.16 languages,
multiwallet UI, default endpoint, receipt cache and batched reads. Discovery
bounds, backup/secret formats and signing remain unchanged. Experimental native
derivation, query optimizations and a global 60-second deadline are not included.

0.1.16-preview (2026-10-20): incremental/lazy receipt ownership cache;
read-batched monitoring over a shared verified connection; automatic project
endpoint and no endpoint UI; nine Android-following languages; renamed GitLab
namespace; cancel pending sends when the wallet closes before broadcast.
0.1.15-preview: simple isolated multiple wallets, per-wallet deletion,
three separate backup checks, optional authentication/settings, Korean/English.
0.1.14-preview: TextDecoder initialization fixes Android startup crash.

ReSatoshi Wallet source change log

0.1.13-preview: discovery performance fix. Bounded read batches, validated public
account-specific search hints, current UTXO/history rechecks and explicit Full
recovery scan for hot/watch-only wallets. First/daily/manual full recovery retains
change indices 0..1999. No key derivation, secret format or QR protocol change.
53 regression tests and all 10 real backend checks pass; see DISCOVERY-PERFORMANCE.txt.

Backend baseline follow-up (after 0.1.12): feature freeze, recovery/user/threat/device docs
split; isolated Core and real ElectrumX TLS compatibility harness. No Android
wallet feature, network constant, derivation, storage or QR format change.

Earlier source commits (oldest first):
aed8eb05d feat: add isolated Resatoshi Android wallet preview
f09d564b4 feat: scan recipient QR addresses in Resatoshi Android wallet
8671f3bd8 feat: support BIP39 passphrases with legacy wallet compatibility
ccc8859be fix: handle wallet creation failures and use async Android entropy
93f071aa9 feat: add physical dice creation and password-encrypted wallet backups
8467f18f7 feat: add numbered mnemonic recovery and QR airgap signing
2d3ff058c fix: offer QR signing without persistent offline mode
f2b609b17 feat: import a plain address as a read-only watch wallet
1f21a0c5d refactor: keep watch wallet pairing to account public-key QR
7e823eb79 fix: require fresh device approval and recover every accepted change path
bb1621c0a feat: show provisional incoming payments from live Electrum notifications
d11578673 feat: use English throughout Resatoshi wallet preview
1d80d00cf fix: prepare wallet privacy and attribution for source publication

Historical full-node implementation notes (moved from build guide)
================================================================
Public-cache isolation update (2026-11-07, versionCode23, same 0.1.20 name)
Core starts with -nowallet and networking disabled, then loads public caches
individually through RPC before enabling P2P. Failed unopened caches are moved
under wallet-quarantine/<generation>/<wallet> with an AtomicFile repair journal.
Original DBs and sidecars remain on device. Interrupted moves resume. The old
wallet's historical-scan proof is removed before creating a blank public-only
cache; the affected account must register its xpub and complete discovery.
Pruned historical gaps still require fresh-chain recovery. RPC transport errors
do not trigger quarantine; successfully loaded private-key wallets are unloaded
and blocked. A per-account preparation failure does not block healthy accounts.
Quarantines consume additional storage and are not automatically deleted.

Detailed review update (2026-11-07, versionCode24)
- Only missing/invalid-format caches (-18) and explicit Wallet corrupted errors
  trigger automatic cache replacement. Pruned-history failures preserve the DB
  and direct the user to fresh-chain recovery; unknown -4 failures stay isolated.
- Invalid optional proof/repair metadata is copied under invalid-metadata before
  atomic replacement. It remains at its original path until replacement commits,
  so interrupted metadata repair cannot silently restore old scan trust.
- Proof reset rotates a persisted scan epoch. App completion markers use that
  namespace; a successful new scan or actual fresh-chain attestation is required.
- Pending chain-move journals remain mandatory; their contents are never guessed.
- The old public-descriptors.json file is ignored and no longer written. Fresh
  recovery verifies actual loaded Core descriptors before allowing P2P traffic.
- Stop/timeout share one service-owned process shutdown path. Foreground service
  teardown is prompt, Core uses SIGTERM flushing, and startup errors stay visible.
- Readiness loss closes local sessions; cancellation is checked after the last RPC.
