VERIFIABLE RECORD
mrb_df3dc402b18f43da
2026-04-19 17:32:43 UTC
▲Client-side hashed record
This proof establishes that a specific cryptographic hash was registered and signed by Sealison at a given time.
THIS PROOF SHOWS
- ▲ A specific hash was registered.
- ▲ The proof was timestamped.
- ▲ The proof was signed by Sealison.
- ▲ The proof can be re-checked from its exported bundle against Sealison's pinned public key.
THIS PROOF DOES NOT SHOW
- — That the original content was true.
- — That the original content was compliant.
- — That the original content was complete.
- — That the original content is stored or recoverable by Sealison.
ⓘ Sealison stores the hash, not the original content.
CLIENT-SIDE HASHING
Content was not stored on the server.
Only the SHA-256 hash was recorded. The original content remains with the data owner. To verify, reconstruct the original interaction below.
RECONSTRUCT & VERIFY
VERIFY INTEGRITY
Reconstruct the original interaction to verify it matches the recorded hash.
⚠ Spaces, punctuation, and formatting matter. "Refund processed" ≠ "Refund processed "
HASH (SHA-256)
96a7456ed05aa24d37b9155d8cba2a4897c803ab40d31497aa04045806fedb25
▲ This record is part of an append-only chain. Any modification would break the chain integrity.
Logs are claims. Proof is verifiable.
SealisonProof, not logs.