Skip to content
An Indefinite ntegral Evidence. Questions. Everything.
--:--:--

Sealed Prediction hr.temporal-object.0001

Lot 1: Banksy

A bounded prediction frozen as ciphertext and committed before a later opening and outcome record.

Record
Active
Disclosure
Sealed
Proof
Cross-checked
Outcome
Unsettled
Custody
Instruction sent · no acknowledgement recorded

Custody boundary: Instruction sent; no acknowledgement is recorded. No acceptance, retention, or operational test is claimed.

Created
Registered
Next review
Latest opening

Open at the first declared occurrence or no later than 14 July 2036.

  1. Predicted Scene The predicted scene occurs.
  2. Practice Ended An authoritative record establishes that the relevant practice ended without the predicted scene.
  3. Absolute Deadline 14 July 2036 is reached.
Rule type
Opening
Latest date

Evaluation: All five frozen conditions are required for fulfilment; fewer than five is partial, while an end-of-practice record or the deadline without all five is failure and still requires opening.

What the integrity record establishes

This can show that the exact committed file existed no later than a stated public anchor. It does not reveal hidden contents or prove that a claim is true.

Current revision
ots-1
Proof state
Cross-checked
Anchor
Bitcoin Block 957995
Reported timestamp
Last cross-check

What happened, and when it was recorded

  1. Commitment Recorded

    Committed plaintext SHA-256 recorded.

    Boundary: The commitment does not reveal or prove the truth of the prediction.

    Recorded 14 July 2026, 12:48 +02:00
  2. Sealed

    Ciphertext SHA-256 recorded and exact readback completed.

    Boundary: The ciphertext does not prove authorship or future outcome.

    Recorded 14 July 2026, 12:56 +02:00
  3. Timestamp Submitted

    Original proof revision hash recorded.

    Boundary: Submission alone was not yet a completed Bitcoin attestation.

    Recorded 14 July 2026, 13:00 +02:00
  4. Custody Instruction Sent

    Dennis confirmed that a unilateral custody instruction was sent through Proton.

    Boundary: The exact Proton send timestamp and message identifier were not independently read. No acceptance, retention, identity confirmation, or operational test is claimed.

    Recorded 14 July 2026, 13:12 +02:00
  5. Standalone Candidate Recorded

    A standalone TID release candidate was prepared locally.

    Boundary: The standalone candidate was not uploaded or live.

    Recorded 14 July 2026, 13:24 +02:00
  6. Proof Upgraded

    Current proof SHA-256 and four Bitcoin block-header attestations recorded.

    Boundary: The upgraded proof was not the proof attached to the earlier custody message.

    Recorded 16 July 2026, 21:26 +02:00
  7. Objects in Time Candidate Recorded

    Lot 1 was migrated into the local Objects in Time registry candidate with its exact public commitments.

    Boundary: Local registration is not publication and assigns no public parent TID ID.

    Recorded 20 July 2026, 16:15 +02:00
  8. Published

    Objects in Time was published as T0001 / hr.tool.0001 with Lot 1 as its first nested record.

    Boundary: Publication establishes public availability of the record and files; it does not establish truth, authorship, custody acceptance, or fulfilment.

    Recorded 20 July 2026, 17:11 +02:00

Downloads and exact commitments

Exact hashes remain selectable. On narrow screens, scroll the table sideways to inspect each value without breaking it apart.

ObjectFile or algorithmSHA-256
Ciphertext lot-1-banksy-v1.md.gpg d67e08f52ed2e83328d9e3cfe69f2db71807de2ac5f25ace2d97b0bc37ecf942
4932 bytes
Current proof lot-1-banksy-v1.md.gpg.ots 04c39a4acefe9e144eb8b5e2068bd9a53b832e82e7bedd43a6cd58b59b36fd21
Plaintext commitment SHA256 27e010c0db482cc041317c3284718f42eeef0cc8b3b874dd24c8c153df301d3a

Proof revisions

  • ots-0 Submitted eef534d0fb41897d31cfdfa357d4340765151ad40a4e72ed07c3bdb5c25573ac
  • ots-1 Cross Checked · current 04c39a4acefe9e144eb8b5e2068bd9a53b832e82e7bedd43a6cd58b59b36fd21

Pest Control

State
Instruction sent · no acknowledgement recorded
Acceptance claimed
No
Retention claimed
No
Operational test claimed
No

Assignment alone does not establish acknowledgement, retention, identity confirmation, or operational readiness.

Context without rewriting the record

Report a correction