Manifest of Record — Immutable Filing Verifier

Manifest of Record Immutable Filing Verifier

Record (authoritative)

Pending validation… CID & Path unchecked SHA-256 unchecked Date unchecked

Derived Links

ipfs://

–

Gateway

–

Artifact

–

Direct by CID

–

Alt Gateways

–

Quick Checks

CID ↔ Path

–

SHA-256 format

–

Size (bytes)

–

Filing Date

–

Local File Verification (optional)

Select artifact (DeedOfRecord.pdf)

Computed SHA-256

–

Local Size

–

No file selected

Hashing done in-browser using SubtleCrypto.digest. No data leaves this page.

Command-line Verification

Compute SHA-256 of DeedOfRecord.pdf locally:

Linux / macOS

shasum -a 256 DeedOfRecord.pdf | awk '{print $1}'

openssl dgst -sha256 DeedOfRecord.pdf | awk '{print $2}'

Compare with the sha256 value above; must match exactly.

Publishing Requirements

Every record must include a verifiable sha256 (64-character digest of the actual file bytes).
A fixed artifact_path pointing to the immutable IPFS asset.
A clear jurisdiction_note and filing_date for lawful provenance.

Once published, never alter the JSON — immutability is part of its integrity.
Future attestations can be added separately with version tags (v1.0, v1.1, etc.) but the base record remains immutable.