Awinel

Past visits

    Trashed visits

      Site

      First offline fix can take 30–60s. Hold the phone outdoors and stay still.

      Operator

      Kiln & feedstock are recorded per batch in the live log (each burn is its own batch).

      Weather (optional)

      Observer

        Visit summary

        Duration
        —
        Events
        0
        Photos
        0
        Est. size
        —
        Recommended workflow / what each button does
        1. 🔍 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.
        2. ⚓ 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.
        3. 📦 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.