PROMX DEVELOPMENT — MANUAL INSPECTION KIT
NORMAL APK002 SETUP ACCEPTED — CONTROLLED LOCAL-FORWARDING SCOPE

This is an opt-in, zero-economic-value public test account and a read-only h11
inspection configuration. It is not official Genesis Zero, a full product launch,
or a service for new payments. No account is restored or configured automatically.
The ordinary APK contains no embedded public backup or preset signing workflow.

WHAT TO TRANSFER TO AN AUTHORIZED ANDROID TEST DEVICE
- APK: ../PromX-development-arm64-002.apk (outside this small kit)
  262386154 bytes; ARM64; package io.promx.wallet; development/debug signed.
  SHA256 e05cd744914f9e3f6116f697b2f762c52c2461ef12fd1cc638353373d943887b
- public-wallet-fixture.backup
- development-profile-1.json (primary), development-profile-2.json (alternate)
- independent-native-read-trust.json
- PUBLIC-BACKUP-PASSWORD.txt and this README for reference.

The APK is preserved at:
/Users/bigwater/Documents/Codex/2026-10-31/task/artifacts/PromX-development-arm64-002.apk
APK route: https://promx.me/dl/PromX-development-arm64-002.apk .
Verify its SHA-256 above after download. This small kit does not include the APK.
Development signer SHA-256:
f210a0167e4333f0ca5e205b4fa2811342ba23de8fbaacdc0cdebbcdd07ced64
Use only a device where development-app installation is already authorized. This
kit does not alter device security, enroll Tailscale, or install anything for you.
Do not uninstall an existing real wallet to make room or resolve a signer conflict.

ACCESS AND LIFETIME
Primary:   http://100.97.152.45:52521
Alternate: http://100.97.152.45:52522
These are actual Mini listeners reached through an existing authorized Tailscale
route/ACL. Android localhost, Air ADB reverse and closed SSH tunnels are NOT the
route. If the device lacks authorized access, stop and arrange access with the
service owner. Do not substitute a public/legacy server or change security rules.

Owner readiness was observed 2026-11-01 15:09:26 UTC; service expiry is
2026-11-02 15:06:19 UTC (10:06:19 UTC-05). Availability was not re-probed here.
Both endpoints serve retained h11 reads only. There is no fresh-parent service,
ongoing certifier or clock advancement. DO NOT SEND through this service. A future
maintained submission service and its validated setup are separate unfinished work.

ORDINARY ANDROID SETUP (MANUAL; LOCAL-FORWARDED TEST PASSED)
1. Receive the APK and small files through your authorized local transfer route.
   Compare file checksums with SHA256SUMS and independently supplied operator
   checksums. A filename or an RPC response does not establish trust.
2. Open the ordinary APK. Choose “I already have a wallet”, then “Restore from a
   backup key”, then “Choose backup file”. In Android's system document picker,
   explicitly select public-wallet-fixture.backup. Selection fills the form only.
3. Enter the ENTIRE line in PUBLIC-BACKUP-PASSWORD.txt as the backup password,
   including “PUBLIC fixture-only backup PIN (TEST ONLY, zero value): ”. Choose
   Next, then choose and confirm your own local test PIN. This is a public dummy
   account: everyone knows its backup password. Never use it for real assets.
4. Check the restored account is exactly:
   3M4eKxfptx6CosWJZ2hC1mNZzvybv93YMr6vtMm2DA3M
   A restored legacy network label may say mainnet; that label is NOT permission
   to use mainnet. Before network use, explicitly configure this development
   profile and independent trust as follows.
5. Open Settings > Advanced > “Import development profile file”. Pick
   development-profile-1.json. Review the endpoint and chain identifier, select
   “Use file in form”, then separately press “Configure development network”.
   Import alone neither saves a profile nor contacts an endpoint.
   Expected chain identifier:
   9062d61f89f112dd9abfd2f43b9aa09c0bdaace94f6a8f2828aae5cf56b4fa14
6. Obtain independent operator confirmation of the genesis manifest/profile and
   initial roots, using OPERATOR-TRUST-REFERENCE.json and its separately delivered
   checksum. The copy here is a reference, not a new trust authority. The native
   trust file SHA256 is:
   3dd53bee590677402493b56170d8ee05326b74503fc0d8afd25910459f92d201
   In Advanced, select “Import independent trust file” and pick
   independent-native-read-trust.json. Review its genesis/profile details, select
   “Use file in form”, then separately press “Select independent read trust”.
   Native verification remains mandatory. Do not import OPERATOR-TRUST-REFERENCE
   as the native input: it is a different, human delivery schema.
7. Return Home and inspect the account balance/provenance. A successful certified
   read should refer to retained checkpoint h11. Treat “unverified”, a read error,
   mismatch or timeout as unresolved; do not interpret it as zero or verified.
   The alternate profile is an explicit optional switch to the second endpoint,
   using the same import/configure steps and same independent trust. Supplying two
   files does not itself prove the phone contacted or verified both nodes.
8. This backup contains no transaction journal. It does not promise that historical
   Send/Activity records appear after restore. Do not submit a new transfer to
   recreate those records. This kit is only for retained-state inspection.

WHAT IS AND IS NOT VERIFIED
The kit's fixed-file checks bind the unchanged public backup, native profiles,
trust, chain/profile/bootstrap/initial roots and retained h11 metadata. Earlier
APK package/signature checks are referenced. The actual Android system document picker, public backup restore, explicit profile
and independent trust selection, and verified h11 Home read passed in APK002 in
516.94 seconds, using owned ADB reverse and Mini loopback forwards. Cleanup was
clean. This accepts the ordinary setup sequence in that controlled transport scope;
it does NOT verify direct phone Tailscale reachability for the supplied profiles.
No new signing, submission or old journal replay occurred. The successful earlier
two-node transfer remains separate evidence. A later balance text-wrap source fix
is not included in APK002. Fixed-initial-authority development
trust is supported here; production signer rotation is not claimed. Privacy,
private gifts and full product readiness are not established by this kit.

INSPECTION PUBLICATION DOES NOT ESTABLISH SENDING READINESS
Normal setup passed in the controlled local-forwarding scope above. Direct phone
Tailscale access remains unverified. No maintained submission-enabled service is
supplied. Full product release and official Genesis Zero are not claimed.
