Umarise Anchored POC
This repository demonstrates verifiable provenance for ML artefacts using independent timestamping. The files below were anchored before publication; their hashes can be verified against an independent time foundation.
What is anchored
The hashes of the files below were registered with Umarise and timestamped on the Bitcoin blockchain via OpenTimestamps. Anyone can independently verify that these exact bytes existed at the recorded time, without trusting Umarise, HuggingFace, or any single party.
The artefacts are intentionally heterogeneous: one ML model file and one IETF draft, anchored by the same primitive.
Anchored artefacts
| File | SHA-256 | origin_id | Anchored at (UTC) | Bitcoin block | Verify |
|---|---|---|---|---|---|
model.txt |
4c36812da5a784d06e4557285b7110f58134684d350b1cdcfb4b67780f065ed0 |
0abef79e-6eba-4804-842c-c8db325a351d |
2026-04-28T17:45:03.509+00:00 | 947045 | verify · .ots |
draft-fassbender-scitt-time-anchor-01.txt |
59440720a019f5ef7771841fbd1bb5fcc281f0a4e6733031127f1c97d0f3d974 |
e6a07ff3-6a01-484c-9015-3340867d130d |
2026-04-28T17:45:04.169+00:00 | 947045 | verify · .ots |
How to verify yourself
# 1. Recompute the hash locally
sha256sum <file>
# 2. Compare to the SHA-256 in the table above (must match exactly)
# 3. Download the .ots proof from the verify link, then independently verify
# against a public Bitcoin node:
ots verify <file>.ots
If steps 1 and 2 match and step 3 returns a valid Bitcoin attestation, the file existed before the recorded block was mined. No further trust required.
Boundary
This repository is a publication-time anchoring artefact. It does not demonstrate training-time hooks, model accountability, or model explainability. It demonstrates one thing only: this exact artefact existed before this point in time.
Umarise
Umarise provides a time foundation for verifiable digital artefacts. What you create stays with you. What you anchor can be independently verified later.
Generated: 2026-04-28