Skip to content

R13 — Ordinary cameras, fragmented QR and restore errors

Status: NOT EXECUTED as a complete hardware procedure — T2B1 and T3B1.

Use the shared acceptance record, with a separate result for every required model/OS. Host and emulator output remains separate evidence.

Preconditions

Two different ordinary phones/cameras; physical 128×64 screen on both revisions; disposable identities including a PIV/RSA key or largeBlob requiring many frames.

Steps

  1. Export a short OTP as otpauth; photograph the real screen and decode offline using an independent QR application. Compare every parameter. Repeat with a long OTP triggering encrypted fallback.
  2. Export an encrypted identity with Large modules, then Dense QR. Record lighting, distance, phone, autofocus, attempts and timing. Photograph every frame and independently check ID/index/total/CRC. Emulator screenshots are not a substitute.
  3. Check previous/next/finish, held-left cancellation and hiding after 60 seconds. Finish only after all frames are photographed. Test full export and its identity/QR counts.
  4. Prepare supported baseline JPEG/PNG ≤256 KiB and ≤1024 pixels. Restore over MSC, copying files individually out of order and with identical duplicates. Enter the local passphrase, confirm and verify real cryptographic use of the restored identity.
  5. Repeat with a missing frame, changed CRC, conflicting duplicate, mixed IDs, wrong passphrase and modified ciphertext/tag. No active identity may change. Copy the valid missing frame and verify progress without leaving import mode.
  6. Repeat sequences and both profiles with both cameras and both revisions. Unreliable readability blocks acceptance: fix and retest instead of waiving it.

Expected result

QR codes decode from physical screens; complete sequences restore; malformed inputs reject without mutation; reliable controls/timeouts. Theoretical QR encoding capacity is insufficient.

Evidence to retain

Private original photos, camera models/conditions, success rates/time/frame counts, independent decodes/hashes, before/after error states and proof of restored use. Publish only redacted evidence.

Per-identity reception and copy retries

Copy all frames of one identity before Continue, then wait for the message allowing the next identity. During confirmation/KDF, WRITE(10) must explicitly reject with NOT READY 04/07 and full residue. Verify the OS reports failure and the same file succeeds after resumption. Keep MSC mounted between identities, finish explicitly, verify exact totals and completeness, then eject. A late failure retains completed identities without changing an incomplete/corrupt identity. Repeat retries on each OS; this behavior is not yet physically qualified.