From 0956b1368ade61cccc11f86fee81851473ef08b4 Mon Sep 17 00:00:00 2001 From: SkateSpots Date: Sat, 26 Sep 2026 23:19:47 +0700 Subject: [PATCH] docs(escrow): exact Android test-build steps for on-device verification Add 'Producing a test build' (android:init -> android:sync -> assembleDebug -> adb install) to the ESCROW.md checklist, plus the two-account requirement. The mint-touching paths still need a real device run. --- ESCROW.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/ESCROW.md b/ESCROW.md index 7efa194..f0aa05b 100644 --- a/ESCROW.md +++ b/ESCROW.md @@ -92,6 +92,21 @@ Escrow is native-only and its mint paths are unverified — run this on a real device with **tiny amounts** before trusting it. Check every box; anything that fails is a bug to fix (or a mint that doesn't support P2PK — note which). +### Producing a test build +```bash +# First time only — generates android/ (gitignored) +npm run android:init + +# Build the web assets + sync into the native project +npm run android:sync + +# Debug APK (debug keystore — no release secrets needed) +cd android && ./gradlew assembleDebug +adb install -r app/build/outputs/apk/debug/app-debug.apk +``` +To test both sides you need **two accounts** — easiest is one device (this build) +plus one other client/device with a different key. + ### Preconditions - [ ] Latest Android build installed (`npm run android:build`), logged in. - [ ] Cashu wallet initialised and a reachable, trusted **mint** added (Wallet).