Sample record · Digital-asset custody

A multisig signer approves what the screen showed

Signer 2 of 3 approves a 250 ETH transfer described on screen as a routine rebalance. The record holds the displayed summary and the fingerprint of the payload that was actually signed.

Fictional scenario, real seals. No company, person or transaction here is real. Each record was sealed on Verdict’s public sandbox and logged on Sigstore Rekor, a public log Verdict does not run. This chain was sealed in one sitting, so its log times are seconds apart; in a live deployment each step is logged when it happens.
What the log time settles in a real case

What the signer was shown at the moment of signing, fixed before any later dispute over the transaction.

  1. Step 1 of 1 · Signer 2 of 3 approvesHuman approved

    Signer 2 of 3 (fictional, treasury operations) approves the transaction as displayed. Approval recorded with the displayed summary and the fingerprint of the payload that was signed, at the time of signing.

    Logged on Rekor
    2026-10-13 17:42:22 UTC
    Log index
    3245480599
    Record id
    ser_551466d5c3348b2f0178071ccc89d5b8
    Verify in your browser →Open the Rekor entry ↗Download the record

How to check the time yourself. Open the Rekor entry and compare its logged hash with the SHA-256 of the record’s commitment, which the verifier shows. If they match, the entry’s integrated time is the earliest moment this content is proven to have existed. Log times above were read from Rekor on 2026-10-15.

A record proves what it says has not changed since it was logged. It does not prove the event happened as described, or who made the record. What Verdict proves, and what it doesn’t →

All sample records →