Repository navigation
Conversation
|
Downstream build consumer: the OSS Scanner preparation is now in #7044. It should reuse this work, not introduce a second Android toolchain. Enrolment does not need a final WalletScrutiny verdict, the full R4 release, or completion of the separate recoverable-wallet preview. One concrete source mismatch at the inspected head For the scanner handoff, the minimum needed is the reviewed, complete Docker build plus a real network-disabled test run with required sources, caches and synthetic config retained in the image. The current toolchain-only Dockerfile needs a small build adapter preserving Anthropic's |
Codex Cloud continuation handoffState: Ready for Cloud continuation. Draft diagnostic work; no WalletScrutiny verdict or release approval. Workstream and objective: Android app reproducibility for Bitcoin Keeper. Establish a repeatable, independently inspectable Android build and ultimately compare an exact public release build with its distributed APK and Play splits. Keep this work parallel to R4/2.6.4 and Bitkey. Repository and baseline (12 Oct 2026): KeeperCommunity/bitcoin-keeper. Primary draft PR #7043 targets sprint from branch codex/android-repro-independent-20261008. Exact remote and local head: 5a6a1ea. The worktree is clean, with zero commits ahead of or behind its remote. Latest sprint is 6c4e1db; its only subsequent change relevant to this PR is the new root AGENTS.md workflow contract. No newer Cloud commit or source conflict was found on #7043. Read that AGENTS.md before continuing. A separate old-base Android live-config experiment was preserved on remote branch codex/android-repro-release-env-fix-20261009, exact commit 8e29407. It has no PR. It is superseded by the stronger reviewed .env.production guard in R4 draft #7045; do not merge or cherry-pick it into #7043. Other local reproducibility experiments have their intended content in #7043 or are on the already-pushed verification-bootstrap branch. Generated APKs, caches, logs, and private configuration remain outside GitHub. Completed
Partially implemented / remaining
Actual checks and known failures
Dependencies and decisions to preserve
Next Codex Cloud tasks, in priority order
Restrictions: No merge to sprint or release branch, no store submission, deployment, signing with production keys, or release publication without explicit user approval. Do not reset, clean, force-push, overwrite another stream, or commit secrets/generated artifacts. When development is complete, add the repository AGENTS.md “Codex local handoff” section with exact head SHA and targeted Mac checks, then return PR #7043 in NEEDS_LOCAL state for ChatGPT coordination. |
Purpose
Establish the inputs and evidence needed for an independent Bitcoin Keeper Android released-binary comparison. This draft targets
sprintand remains separate from R4 integration, Bitkey, and OSS Scanner enrollment. A release reproducibility verdict is not established.Changes
Verification
At head c12dcdc:
patch-package6.4.7 applies the Realm patch to the SRI-verified npm package. CMake 3.22.1 downloads/extracts all four real pinned archives; a wrong checksum fails before extraction, unknown version/ABI fails, and a non-Android fixture preserves prior behavior. The final whitespace-safe patch produces exactly the tested helper bytes.389F4CADA0785AC0E28A0C181BEBDE261DC3CF62, also published in April 2024 repository documentation. APK SHA-256:a20d934ebd80ece779d3c171c7906bb4aff010337989ec1b826cab55c50eba46.bfa023d99facebafa4a9af22b9e49a13dbbfa3ee825be3da16cca9e3ea1b243a. Packageio.hexawallet.bitcoinkeeper, version 2.6.3, code 626. The seven-field presence audit passes without disclosing values.0x504b4453. This is a tooling test, not a source rebuild.The prior final-head Android run 37937333390 passed, contrary to the stale previous description: 1,096 tasks at checkout
94eb5a53a055e13eaff773f2b8af1551e4026a32, associated with former PR head5a6a1ead6b14a9054c34de28bd2885458d576389. Its downloaded entry manifest matches same-source repeat run 37925672723 exactly: 1,610 APK entries and 1,698 AAB entries, manifest SHA-256390ebdd7481de40ed7d0850a25e5de65ff69edd307507b4978b0a6416b128670. Whole AAB SHA-256 remainsf08727ab342ef8a1b9740cbcdbaa3fc62ae2f0fb022cb06b40e2c78f970effc0. Previous controlled builds located APK byte variance solely in encrypted SDK metadata; retain that metadata.Fresh Android integration run 38212939422 passed: all 1,096 tasks and APK/AAB, ZIP-entry, container, source-audit and apt/package manifest checks succeeded. It tested PR merge checkout
2133fd821c0f3322c8eb4920c5c51eb921b4b9e5, associated with headc12dcdc4a332110e22ca84a1e7f1dc832fd9fe37; record this source distinction when comparing local outputs. Current general Jest CI passed all 183 tests / 17 suites; focused tools and CodeQL also passed. The prior 30 Electrum failures did not recur in this run. Lint itself failed with 4,540 errors and 913 warnings, exactly the same counts as the former head; its job appears successful because the step hascontinue-on-error: true. This corrects the earlier job-status-based lint claim. The local-validation gate remains failing pending Mac validation. Linux Android integration passed; Mac/emulator validation remains outstanding and lint is not clean.Remaining gaps and next steps
react-native-configcan embed additional supplied fields. The diagnostic branch also has a different lockfile and older Android version than v2.6.3. Do not use it as an exact-release candidate or publish unchecked production values.build.sh --binary/COMPARISON_RESULTS.yamlverdict.No production signing, credentials/configuration values committed, release publication, or merge performed. Release inclusion in R4/R5 remains undecided; overlapping R4 files require separate coordination.
Codex local handoff
State: NEEDS_LOCAL
PR: #7043
Base: sprint
Head branch: codex/android-repro-independent-20261008
Head commit: c12dcdc
Goal and acceptance criteria: Validate Android build-input/inspection changes and exact-source comparisons while preserving the not-established release verdict. A placeholder/debug build may validate tooling only.
Changes made: Realm native archive verification; source-input audit; APK container/signing-block inspection; apt dependency evidence and CI retention; authenticated v2.6.3 evidence.
Cloud checks: 49 focused Python tests PASS; shell syntax PASS; staged git diff --check PASS; patch-package 6.4.7 application PASS; CMake 3.22.1 four real ABI downloads/extractions and rejection controls PASS; Docker apt stage PASS; release PGP/checksum/APK-v2/field-presence checks PASS. Current focused CI PASS, general Jest CI PASS (183 tests / 17 suites), CodeQL PASS. Lint command FAIL (4,540 errors / 913 warnings, same as former head, masked by continue-on-error). Fresh Linux APK/AAB CI PASS (run 38212939422, 1,096 tasks plus every output manifest check; checkout 2133fd8 associated with this head). No Mac native build, emulator install, or physical-device test performed.
Required local checks: ANDROID
Local checks requested: Fetch this exact head into a clean isolated checkout. Run the focused Python suite and a clean pinned Android production-flavor APK/AAB diagnostic; verify all retained manifests, SDK metadata scope, and Realm fresh-download checks. Build/install the Android diagnostic on an emulator and smoke-test startup/onboarding with disposable data, recording the invalid-service limitations. For a release comparison, first obtain the reviewed historical input contract; use exact tag 872cbc4 and independently authenticated binaries, not the sprint diagnostic. iOS and hardware checks are not requested because this continuation changes Android build/inspection tools only; report any device tests actually performed.
Risks / known gaps: Historical production configuration unresolved; released source association not attested; dependency resolution/remaining native caches incomplete; no fresh Play split comparison or release AAB; Mac/emulator validation outstanding; lint failures unchanged from the former head. Prior Electrum failures did not recur in current Jest CI. No reproducibility verdict or release approval. Do not merge, production-sign, upload, or publish.