Documentation and interface review — 2026-11-08 (unreleased source)
Changes: formal gate remains incomplete; owner-reported phone send and network
observations are recorded separately. Carrier blocking is unconfirmed. Current
decisions supersede the historical freeze/extraction plan. Notification title,
status, channel and Stop action already use Android device-language resources
(nine locales, English fallback); no native behavior changed. Connection-mode
parse failure now uses its existing English translation key.
Validation: strict TypeScript passed; all 133 Resatoshi tests passed;
git diff --check passed. No new physical-device test was performed. No APK was
rebuilt and no website deployment, Core pin/tag, wallet tag or versionCode was
changed. Existing implementation and test evidence below remains historical.

Wallet source publication review — 2026-11-07, internal build38

Target repository: https://gitlab.com/tpa1995/resatoshi-wallet.git, branch main.
The local feature branch descends from the fetched origin/main; publication is
an ordinary fast-forward, with no force push. Core and BlueWallet remotes are
not publication targets. All implementation commits are already recorded.

Fresh checks:133 active-app tests, strict TypeScript and packaged distribution
license/source/Core checks pass. Build38 ARM64 build/lint, signature/version,
API35 native lifecycle/corruption/deletion fixtures and Desktop APK checksum
were verified during implementation. No runtime changes were made in this final
review; docs now reflect build38, embedded-binary build prerequisites and the
confirmed email contact. Existing physical-device/OEM validation limits remain.

Outgoing-history review: all new implementation Git blobs were scanned for
private-key headers and common provider credential patterns; none matched. This
includes the large upstream network-security XML. Changed paths were checked
for wallet databases, credentials, production signing material and generated
APK/native artifacts. Public test vectors and third-party license/source data
remain intentional. This is scoped review, not a universal secret-scan guarantee.
The source upload does not publish a new APK release or change the website.

Visibility and node restart boundaries — 2026-11-07, versionCode38

Distinct blur and later background events both notify consumers even when the
interactive boolean remains false. Repeated identical events are ignored.
A live service blocks a new start even if its child has just exited. Startup is
reserved atomically before dispatch; duplicate requests fail with retry guidance.
Dispatch exceptions restore the prior phase. Teardown, child exit and deletion
intent invalidation cannot overwrite a newly reserved startup state.

Native fixture models child-dead/service-still-closing, stopping, duplicate
startup and dispatch failure without launching Core or using production wallet
data. Existing deletion, corruption preservation and recovery fixtures are kept.
PASS:133 active-app tests, strict TypeScript, ARM64 Preview build/lint and signed
APK/version/Core/license checks. API35 x86_64 native fixtures pass. Native gate
cases cover closing-service presence, both child/service teardown orders,
late old-owner cleanup versus reserved/attached replacement, duplicate starts,
and dispatch-failure rollback. Existing corruption/deletion/recovery fixtures
also pass. Logs accompany ../android-wallet-0.1.20-transition-fixes-20261107/.
This is a controlled lifecycle regression, not an OEM-wide stress certification.

Interruption safety — 2026-11-07, versionCode37

AsyncStorage open retries retain the database. A non-destructive SQLite
corruption handler prevents the framework's default database deletion. Unknown
upgrades fail instead of resetting data. A preBuild gate requires all patches.
Native fixtures use an isolated temporary database path: corrupt-file retention,
schema-open error retention, preserved pending-record contents, normal persisted
read/reopen, and running-marker presence/clear. Production wallet storage is not
modified by fixtures.

Shared visibility covers active/background and Android focus/blur independently.
Wallet/setup/session/QR/security operations check it. Losing ordinary focus
invalidates send revisions even if focus returns before component teardown.
Native credential and document flows keep their existing shields; credential
results wait for foreground focus after both authorization and Keystore access.

A durable marker inside the node directory precedes Core launch. Requested stop
clears it only after child termination; unexpected lifecycle teardown leaves it.
A stopped app with that marker shows an interruption explanation, preserving
failure/known-timeout precedence. Marker presence does not authorize deleting or
skipping validation. Whole-node deletion already removes it with the node root.
PASS:132 active-app tests, strict TypeScript, ARM64 Preview build/lint and signed
APK/version/Core/license checks. API35 x86_64 native fixtures pass, including
corrupt and schema-error databases remaining intact. A separate prepare stage,
adb force-stop of the test package, and a new-process verify stage confirm the
saved TXID, wallet sentinel and running marker survive. This uses public fixture
data, without production signing keys, Core mainnet startup or broadcasts.
Logs accompany the APK in ../android-wallet-0.1.20-interruption-safety-20261107/.
Physical abrupt-power-loss, OEM task-killer and long-duration sleep tests remain
separate from the simulated/fault-injected fixtures recorded with this APK.

Deletion result handling and shared removal — 2026-11-07, versionCode35

The operation reports completed native deletion even if optional registration
metadata cleanup fails. Preference persistence failure never invokes deletion;
native failure never proceeds to registration cleanup. Server selection remains
saved across native/cleanup failures. Settings text is shorter; the full final
confirmation and all9 device-language variants are retained.

The common file-removal primitive still uses lstat and never follows symlinks.
The two callers keep independent root policies and interrupted-operation records.
A ReentrantLock replaces the startup monitor; deletion tries it with remaining
budget from an absolute deadline set before queueing. Startup contention and
process shutdown share that deadline. Actual filesystem deletion can take longer.
Native fixtures check held-lock timeout and already-expired deadline without
entering deletion, plus the existing process-stop, interruption, permission and
wallet-isolation cases. PASS:128 active-app tests, strict TypeScript, ARM64
Preview build/lint, signed APK/version/Core/license checks and API35 x86_64 native
fixtures. Logs accompany the APK in
../android-wallet-0.1.20-delete-simplification-20261107/.

Local node data deletion — 2026-11-07, versionCode34

124 active-app tests and strict TypeScript pass, including device-language
coverage for new deletion confirmation, progress and outcome messages.
ARM64 Preview build and lint pass. Packaged license/source/native-library checks
pass; Core binary hash and dependency inventory remain unchanged.
Native deletion fixtures cover partial deletion/resume, fixed-root isolation,
unknown files within node roots, absent-data retries, damaged-marker path
isolation, permission failures retaining intent, and symlink non-traversal.
The bridge fixture uses a disposable sleep process in the separate test app to
check stop-before-delete, queued-start generation invalidation, node/cache
removal and preservation of an app-data sentinel. No signing keys or mainnet
transactions are used. PASS on the API35 x86_64 emulator. Logs accompany the
APK in ../android-wallet-0.1.20-node-delete-20261107/.

Server mode is persisted before destructive native work; wallet sessions are
unmounted while progress is shown. A failure retains server mode if its write
succeeded; failure to write that preference never begins node deletion. Partial
native deletion resumes before the next Core start. Only the two compiled node
roots are removed; other noBackup files, Keychain, submission/discovery state and
app preferences are kept except Core-only completion markers. Reinitializing a
node after deletion can require historical public-wallet discovery again.

Fast local-wallet reopening — 2026-11-07, versionCode33

124 active-app tests and strict TypeScript pass, including disk-cache poisoning,
wrong-account/duplicate rejection, forced recovery and canceled-session tests.
Actual disposable Core tests cover reopen balance/coins and sibling-UTXO source
read deduplication, retaining signing and recovery checks. Native fixture tests
exercise atomic cache save/load and schema/path rejection without production
wallets or mainnet transactions. PASS on API35 x86_64 emulator.
ARM64 Preview build/lint, signed APK/version/Core checks and packaged license/
source equivalence checks pass. Logs accompany the APK in
../android-wallet-0.1.20-fast-reopen-20261107/.

Host-only public-index benchmark: first build2077ms/250 derivation batches,
reopen2ms/0 batches, same-session refresh0 batches; forced rebuild1960ms.
This measures the address-index step, not phone UI or total balance load time.
Core synchronization, network/disk latency and large UTXO sets still take time.
After upgrading, an existing wallet builds its cache once; a missing/corrupt
cache also rebuilds. No stale cached balance is used for speed.

Distribution review and source obligations: see LICENSE-REVIEW.txt and
THIRD-PARTY-INVENTORY.json. The older license-review limitation below describes
build32 and is superseded for the reviewed build33 runtime inventory.

Device-language review — 2026-11-07, versionCode32 (0.1.20-preview)

Connection-mode and preference-recovery screens now use the shared localized
Text/Alert components.134 supplemental messages cover node state, recovery,
peer health, submission records, current privacy and native errors in existing
en/ko/zh/ja/vi/th/fr/es/ru locales. Other language tags retain English fallback.
Native node notification strings use Android resources in the same9 locales.
Known safety guidance is preserved by alert sanitization; unknown raw network
errors retain the earlier generic-error behavior. Numeric templates and message
prefixes preserve counts, file names and TXIDs. Raw logs, wallet-owned names,
secrets and legal notices explicitly bypass translation.

PASS:119 active-app tests; all supplemental locale rows and placeholders,
Korean-source fallback coverage, no raw native Text/Alert imports in active UI,
safety-message recognition and unchanged identifiers. Strict TypeScript.
PASS: ARM64 Preview build and lint/resource validation. APK signature/version/
Core hash verification is recorded with build logs in
../android-wallet-0.1.20-device-language-20261107/.

License review:527 notices /231 distinct-text groups are intentionally broad,
including installed transitive and build-tool packages. List structure is kept.
All npm package name/text pairs are unchanged; the project attribution group
adds the pinned embedded Core COPYING verbatim and corrects the obsolete asset
reference. This is not certification of every Maven/NDK license requirement.

Translations are static data; drafts used public interface text only, with
technical terminology and key payment/deletion warnings corrected. No runtime
translation service or user/secret data transmission is introduced. Full device
language-switch/layout testing and native-speaker proofreading remain manual.
Core binary, recovery, signing, wallet data and submission logic are unchanged.

Delete-and-resynchronize recovery — 2026-11-07, versionCode31

Explicit chain recovery now deletes only allowlisted chain caches and previous
chain-quarantine copies instead of retaining another chain. Wallet databases,
public descriptor records, wallet-repair metadata, signing secrets and submission
records remain in place. A validated AtomicFile deletion plan precedes cleanup;
missing/partially deleted entries resume safely. lstat unlinks symlinks without
following them. Deletion or journal-cleanup failure prevents Core startup. Old
move journals are compatible. The 3 GiB startup-space check follows cleanup.
The confirmation explains irreversible deletion and subsequent fresh download.

PASS:115 active-app tests and strict TypeScript.
PASS: real two-Core-node test deletes disposable regtest chain files, compares
wallet DB bytes immediately after deletion, then downloads a fresh chain over
P2P and recovers wallet/funds; signing/QR/pruning/corruption guards also pass.
PASS: Android emulator fileOnly instrumentation exercises the production native
helper: interrupted deletion/resume, symlink isolation, legacy partial move
journal migration, deletion permission failure/resume, full-plan validation,
wallet/signing-fixture/descriptor preservation, and public-wallet repair tests.
PASS: ARM64 Preview build/lint and x86_64 Fullnode/instrumentation build.
Packaged signature/version/Core hash verification and logs are retained in
../android-wallet-0.1.20-chain-delete-20261107/.
The Core binary/consensus rules are unchanged. Real-device storage pressure and
full UI recovery still require device validation. Earlier archive-based recovery
results below describe previous builds and are superseded by this update.

Node status wording — 2026-11-07, versionCode30 (0.1.20-preview)

Normal stopped state is labelled local-node off, with server-mode reassurance
only when no error, read failure, missing binary or recorded interruption exists.
Fullnode mode instead explains how to start synchronization. Known failures and
Android dataSync timeouts have separate labels. Observed failure/timeout details
are stored in private preferences and cleared on a new explicit start. Unknown
OS process termination is not inferred to be a timeout. Existing stop mechanics,
Core binary, signing, submission journal and consensus rules are unchanged.

PASS:115 active-app tests, including stopped-state reassurance exclusions,
error/timeout precedence and shutdown-in-progress wording. Strict TypeScript.
APK build/lint and metadata/signature/Core-hash checks are recorded with
artifacts in ../android-wallet-0.1.20-node-status-20261107/.
The actual Android timeout callback and reopening persistence need device
validation; the test suite covers state-to-text behavior, not those OS events.

Submission safety update — 2026-11-07, versionCode29 (0.1.20-preview)

Expected TXID/timestamp records are persisted before server/local submission.
Lost responses and unexpected returned IDs retain an explicit confirmation gate.
Normal accepted responses clear the record; failed cleanup stays conservative.
Corrupt/unreadable storage blocks new payments rather than ignoring the record.
The same public-account key is used for hot/watch and server/fullnode views.
User acknowledgement warns that missing history is not proof of failed sending
and does not cancel the earlier transaction. Nothing is automatically resent.
A payment revision invalidates pending authorization on node-readiness loss;
node recovery cannot reactivate it. Session and late transport guards remain.

PASS:113 active-app tests including response loss after acceptance, mismatched
IDs, restart persistence, blocked second submission, explicit acknowledgement,
malformed/write/cleanup failures, cancellation while saving, concurrent journal
instances, node invalidation during authorization and late transport guards.
PASS: strict TypeScript and actual two-Core-node signing/P2P/QR/pruning/recovery.
Build/lint and APK metadata/certificate/Core-hash checks are retained with
artifacts in ../android-wallet-0.1.20-submission-safety-20261107/.
New React UI, storage persistence and PIN/biometric interaction still require
physical-device validation. Core/native implementation is unchanged.

Payment-flow polish — 2026-11-07, versionCode28 (0.1.20-preview)

Local wallet send now calls the same chain/peer/tip-age readiness check before
PIN/biometric payment authentication. Session/activity is checked before opening
the prompt. Existing checks after authentication and around mempool validation
remain in place. Server-mode preflight is a no-op; no fallback transport added.
Recovery notices explain automatic readiness re-evaluation. Transactions still
require explicit user action and authentication; no send is queued on recovery.
The two-hour policy, maxconnections=8, Core binary and native code are unchanged.

PASS:105 active-app tests, including same-backend recovery from disconnected
and stale-tip states, read-only preflight, and late connectivity/sync/lock guards.
PASS: strict TypeScript and real Core two-node local discovery/signing/P2P relay,
QR PSBT, pruning, corruption rejection and fresh-chain wallet reconstruction.
Build/lint and final APK verification logs are retained with artifacts in
../android-wallet-0.1.20-payment-polish-20261107/.
Physical PIN/biometric interaction and new recovery wording still need device
validation. Historical evidence for earlier builds follows.

Peer-health update — 2026-11-07, versionCode27 (0.1.20-preview)

Fullnode wallet/watch screens and node settings now warn when peers are absent,
network activity is off, tip time is unavailable, or the tip timestamp differs
from the phone clock by more than two hours. Old tips explicitly warn that
balances/confirmations may be stale. These are availability checks, not proof
of malicious peers, freshness of the best network chain, or transaction relay.
Read-only local balance/history lookup remains available under these warnings.
Local broadcasts check chain identity/sync, peer connectivity and tip age before
mempool validation and again before sending, with session cancellation guards.
Failure never switches to Electrum. maxconnections=8 and Core binary unchanged.

PASS:104 active-app tests, including clock boundaries, invalid timestamps,
disconnected peers, healthy local broadcast, and connectivity/sync/clock changes
or locking between validation and send. TypeScript passes with unused checks.
PASS: real Core two-node local descriptor discovery, signing/P2P relay/mining,
QR PSBT, pruning, corruption rejection and fresh-chain wallet reconstruction.
Android builds/lint and packaged artifact verification are recorded alongside
APK artifacts in ../android-wallet-0.1.20-peer-health-20261107/.
New UI warning states have not been exercised on a physical Android device.
Previous native recovery/UI test results below remain historical evidence.

BlueWallet upstream integration follow-up — 2026-11-07
Version0.1.20-preview retained; internal versionCode25.
Upstream master c4874c5aad91a72b8df7e3c72407456c07a47ffe integrated with
RN0.88.1, React19.3.0, bitcoinjs-lib7.0.5 and bip39 3.1.2.
See UPSTREAM-INTEGRATION.txt for exact versions and compatibility decisions.
PASS:97 active-wallet tests, strict TypeScript, actual two-node Core integration,
ARM64 assemblies/Preview lint, x86_64 instrumentation, existing-wallet update
install, registered security/Keychain/full-node bridges, no auto Core launch,
metadata/corrupt-cache recovery, mainnet sync and fresh recovery/restart.
PASS: actual Android TLS hostname validation and Electrum genesis verification.
Original signing certificate and embedded Core binary are retained.
Physical-device camera/PIN/thermal behavior remains a release check.

Previous build24 validation (historical evidence):
------------------------------------------------
Detailed review follow-up — 2026-11-07
Version name 0.1.20-preview retained; internal versionCode24.

Implemented
- Automatic public-cache replacement is limited to invalid/missing format (-18)
  and explicit Wallet corrupted (-4). Pruned-history and unknown -4 failures
  preserve the database and remain account-specific; pruned history gives the
  explicit fresh-chain recovery instruction.
- Optional corrupt proof/repair metadata is preserved under invalid-metadata
  and atomically rewritten. The invalid source remains until replacement commits.
  A proof reset preserves the chain and rotates the persisted scan epoch, so old
  app completion markers cannot skip a new historical scan. Pending chain-move
  journals still fail closed rather than guessing filesystem move history.
- Removed redundant public-descriptors.json production reads/writes. Actual live
  Core descriptors remain the authority during fresh-chain recovery.
- Shared service-owned shutdown, prompt foreground-service teardown on timeout,
  preserved startup errors, and guard against an overlapping Core process.
- Readiness loss cancels local sessions; final header RPC checks cancellation.

Validation
PASS: all 21 TypeScript unit/regression files and strict TypeScript compilation.
New cases reject a stale registration after scan epoch rotation and reject a
snapshot cancelled during the final header read.
PASS: final ARM64 Preview/Fullnode build, Preview lint, x86_64 native/test build,
APK CRCs, unchanged embedded Core hash and both existing signing certificates.
PASS: actual two-node Core test: local signing, P2P relay/mining, QR PSBT,
pruning, corruption gate and fresh-chain reconstruction preserving wallet funds.
PASS: Android 35 file/RPC regression tests: interrupted cache/chain moves,
malformed JSON/schema, invalid proof reset with chain/signing fixture preserved,
invalid wallet journal repair, pruned/unknown failure isolation, explicit
corruption repair, unsupported private-key refusal, and original DB/WAL bytes.
PASS: actual Android Core with malformed/unfinished wallet caches, corrupt scan
proof and corrupt repair journal on a healthy wallet. Existing healthy public
descriptors preserved, scan epoch rotated, invalid metadata/DB bytes preserved,
blank public-only caches recreated, and shared service stop completed.
PASS: final Android native mainnet smoke synchronized at height15177, then
fresh-chain recovery and another restart restored the actual public descriptor
attestation without the obsolete cache. No private keys entered Core; native
mainnet smoke was read-only. See fresh-smoke.log for the result.
Physical ARM64 thermal/battery behavior and real Android timeout scheduling are
not simulated by these checks. No mainnet signing or broadcasting was performed.

Previous build23 validation (historical evidence):
------------------------------------------------
Public-cache isolation follow-up — 2026-11-07
Version name 0.1.20-preview retained; internal versionCode23.
Core starts without wallet autoloads and loads each account independently with
P2P paused. Invalid unopened caches and all sidecars are preserved under
wallet-quarantine. Repair moves use an AtomicFile journal and resume after
interruption. Previous scan attestations are invalidated before replacement.
Recreated caches are blank, private-key-disabled descriptor wallets; opening
an affected account must complete descriptor registration and historical scan.
Pruned historical gaps still require fresh-chain recovery. Transport failures
and successfully loaded unsupported/private-key wallets never trigger a move.
Wallet RPC waits for initialization; account errors and repair notices are shown.
Stop can interrupt a long startup wallet rescan without waiting in its queue.

PASS: strict TypeScript; all 21 existing tests; Kotlin and test compilation;
ARM64 Preview/Fullnode assemblies; Preview lint; ZIP CRC; existing signing
certificate and unchanged packaged Core hash. Version/application ID verified.
PASS: actual Core startup using -nowallet retains wallet RPC; empty and malformed
wallet folders fail individually, are preserved, and permit blank public-only
recreation while a healthy wallet and a funded wallet remain available.
PASS: actual two-node Core test of local signing, P2P, QR PSBT, mining, pruning,
corruption rejection and fresh-chain reconstruction with preserved funds.
PASS: Android 35 x86_64 recovery tests: interrupted moves resume; DB and WAL
bytes preserved; stale proofs invalidated; transport/private-key cases isolated.
PASS: actual Android Core startup with malformed and unfinished public caches;
original bytes quarantined; blank public-only wallets recreated; RPC usable
after startup. No mainnet transaction was signed or broadcast.
Physical ARM64 performance and extended device behavior remain untested here.

Previous build22 validation (historical evidence):
-----------------------------------------------
ReSatoshi Wallet 0.1.20-preview review fixes — 2026-11-06
=======================================================

Version name retained: 0.1.20-preview. Internal Android versionCode: 22.
The Preview artifact updates org.resatoshi.wallet. The separate test artifact
uses org.resatoshi.wallet.fullnode. Server mode remains the default.
APK and native hashes are recorded beside this report. ZIP CRC and packaged
Core hash match were checked. Core consensus source/binary is unchanged.

Fixes
1. A rejected historical scan on a previously complete pruned wallet preserves
   its completed-registration marker. Normal balance refresh still succeeds.
2. Fresh recovery journals and renames only chain caches and the corruption
   latch into chain-quarantine/<generation>. Wallet databases and app signing
   storage remain in place. Old chain caches are retained, requiring additional
   space. A committed interrupted move resumes before Core starts.
   P2P starts disabled; actual loaded public wallets are verified at height zero
   before networking is enabled. The JSON cache is not an authority. Verified
   recovery metadata persists across restart and incomplete download can resume.
3. Public script derivation yields every 16 addresses and caches the completed
   index per wallet session. Interrupted builds are discarded. Balance, UTXO,
   mempool and tip checks still run on every refresh. On the build host, first
   build was 2578ms with 249 timer ticks; cached access was 0.083ms. These are
   host measurements, not physical-phone performance claims.

Validation
PASS: strict TypeScript; git diff --check; all 21 unit/regression test files.
New regressions cover preserved registration after a refused recovery scan,
cooperative public derivation/cache reuse, cancellation and private-key refusal.
PASS: ARM64 Preview/Fullnode assembly and Android Preview lint (no errors).
PASS: actual two-node Core regtest: signing, P2P relay, mining and QR PSBT;
actual pruning; corruption-latch startup rejection; quarantine only chain data;
fresh chain reconstruction over P2P; existing public wallet and nonzero funded
balance preserved; ordinary refresh remains usable after rejected manual scan.
Regtest identity/xpub-prefix and native attestation envelope are adapted only
in the host test; UTXOs, mempool acceptance, P2P, actual pruning and replay are real.
PASS: Android 35 x86_64 emulator: interrupted rename journal resumes; synthetic
public-wallet/signing-storage fixtures preserved; real mainnet index/pruned
node sync; real public descriptor wallet; fresh recovery with corruption latch;
verified recovery metadata survives node restart with memory attestation cleared.
Native smoke reported mainnet height 15172 and fresh recovery/restart=true.
Mainnet smoke was read-only: no mainnet signing or broadcasting.

Remaining checks
Physical ARM64 battery/thermal/storage behavior, extended workload, device
credential/camera workflows, arbitrary hardware I/O failures, and Android service
timeouts remain release checks. Quarantined old caches are not automatically
deleted. No GitLab push, public deployment or production signing was performed.
