Past visits
Trashed visits
Site
Operator
Kiln & feedstock are recorded per batch in the live log (each burn is its own batch).
Weather (optional)
Observer
Visit summary
Recommended workflow / what each button does
- 🔍 Verify chain locally — sanity-check that this device's chain is internally consistent (event hashes match, signatures valid). No network needed. Safe to run any time.
- ⚓ Anchor (RFC 3161 + Rekor) — request external attestations of the current chain head from two audited CAs (DigiCert + Sectigo, RFC 3161 timestamps) and Sigstore Rekor (transparency log). Requires network. Each click adds 3 entries to
chain.anchors— those are the receipts, not duplicate proofs. Recommended once, when service returns after the visit. - 📦 Export bundle (ZIP) — package the visit (events, media, chain, anchors) into a ZIP for the recipient. Do this last.
Re-anchoring: safe but rarely useful. Anchoring records an anchor_recorded event in the chain, which advances the head — so a second anchoring proves a slightly later state than the first. Useful only if you reopen the visit and add events, then want fresh attestations. The original attestations remain valid for the head they covered.
Forward account
Not signed in.
We'll email a sign-in link. Sign-in is optional until Forward requires it.
Have a link already?
On iPhone the emailed link opens in a browser, not this app. If so, copy the link (or the code from the email) and paste it here to finish signing in.
Data already on this device
Back up this device
Read-only. Sign in to capture again. Export each visit as a ZIP bundle, then keep the file somewhere safe — the bundle verifies on its own, with verify.html.
Forward cloud sync
Where “Send to Forward” posts your closed visits (cloud backup + web viewing). Leave blank to disable. For phone testing this must be a URL your phone can reach (a tunnel or your deployed backend), not localhost.