Verify this record yourself

You do not have to trust this website, and none of the checks below use it after the download. They need only standard tools.

1. Download the bundle

curl -L -o makare-a0e1508c69e1cb64.zip https://makare.3sb.io/download/a0e1508c69e1cb6435c62f93b7a7899ff76075763d989c20414ba73480797414
unzip makare-a0e1508c69e1cb64.zip -d makare-record && cd makare-record

2. Check the files

Every document's SHA-256 is listed in manifest.json. Hash the files yourself and compare.

shasum -a 256 documents/*

3. Check the timestamp

proof.ots commits to the exact bytes of manifest.stamped.json, which lists those same hashes. Drop both files onto opentimestamps.org, or use the official client. A Bitcoin attestation proves the manifest, and so every file it names, existed by that block.

ots verify proof.ots -f manifest.stamped.json

A gateway serving these bytes is not by itself evidence of permanence. Only confirmation in an Arweave block is, which is what the status above reports.