INTEGRITY RECORD

This archive publishes daily cryptographic integrity proofs.

Each record represents a deterministic snapshot of submitted entries.
From this snapshot, a Merkle root is computed and anchored to a public blockchain.

Only cryptographic hashes are included in the snapshot and on-chain data.
No statements or personal data are stored or transmitted to the blockchain.

All proofs can be independently verified without relying on this website.

Latest anchor: 2026-04-24 / confirmed

No new entries recorded since this date.

2026-04-24

merkle_root:

dcb6d13389a91dd8abe1ba7454da19001b171e257290ac3e0ddb7ce742621df0

snapshot_hash:

325c4a99e449bcc54d1479ee5227271e333a45e30fdd2cb34c390bcb3352452f

snapshot (permanent verification URL):

https://savethecivilization.com/api/snapshots/2026-04-24

transaction:

https://polygonscan.com/tx/0x16bf9d60c7b42f67afccadd209e17a54ebe52c18f2f90ad28db57710b2d73267

verify (independent, local):

npx tsx scripts/verify-integrity.ts --snapshot https://savethecivilization.com/api/snapshots/2026-04-24 --expected-root dcb6d13389a91dd8abe1ba7454da19001b171e257290ac3e0ddb7ce742621df0 --expected-snapshot-hash 325c4a99e449bcc54d1479ee5227271e333a45e30fdd2cb34c390bcb3352452f
2026-04-22

merkle_root:

03bf1472728bc8fc833009f385e865cfc3b5433e2702fc1d1a3d64fe468ea108

snapshot_hash:

3aa72799e964df610c647c11555b650536c6d7d671e6d57c0f16cd9d19f443f0

snapshot (permanent verification URL):

https://savethecivilization.com/api/snapshots/2026-04-22

transaction:

https://polygonscan.com/tx/0x89113952bea4946eb343e7cc840a0c9bd2c0efb3e1edf9791b9852a006981118

verify (independent, local):

npx tsx scripts/verify-integrity.ts --snapshot https://savethecivilization.com/api/snapshots/2026-04-22 --expected-root 03bf1472728bc8fc833009f385e865cfc3b5433e2702fc1d1a3d64fe468ea108 --expected-snapshot-hash 3aa72799e964df610c647c11555b650536c6d7d671e6d57c0f16cd9d19f443f0

HOW TO VERIFY

1. Download the snapshot file from the URL above.

2. Run the verification command locally:

npx tsx scripts/verify-integrity.ts \

--snapshot <path> \

--expected-root <merkle_root> \

--expected-snapshot-hash <snapshot_hash>

3. Confirm the output:

✔ Snapshot hash verified

✔ Merkle root verified

✔ Integrity proof valid

NOTES

- Verification is deterministic: identical inputs always produce identical outputs.

- No trust in this website is required for verification.

- Any mismatch indicates tampering or data inconsistency.

THREAT MODEL / GUARANTEES

This system provides the following guarantees:

- Integrity

Once a Merkle root is anchored on-chain, the corresponding snapshot cannot be altered without detection.

- Inclusion

Any entry included in the snapshot can be proven to be part of the anchored dataset.

- Tamper detection

Any modification to the snapshot or individual entries results in a hash mismatch.

- Determinism

Given the same input data, the snapshot, leaf hashes, and Merkle root are reproducible.

The system does NOT guarantee:

- Data correctness

The system proves that data has not been altered after anchoring, not that the data is true.

- Completeness

It does not prove that all possible entries are included, only that included entries are consistent.

- Availability

If snapshot files or endpoints are unavailable, verification may be temporarily blocked.

THIRD-PARTY VERIFICATION

An independent verifier can validate this system without relying on this website.

Procedure:

1. Obtain the snapshot file using the published URL.
The file must be retrieved as raw data without modification.

2. Compute the SHA-256 hash of the snapshot file.
The result must match the published snapshot_hash.

3. Extract all leaf_hash values from the snapshot.
Recompute the Merkle tree using the same deterministic ordering.

4. Compare the resulting Merkle root with the published merkle_root.
The values must match exactly.

5. Verify the blockchain transaction.
Confirm that the published merkle_root is included in the transaction data.

Verification outcome:

- If all values match, the dataset is cryptographically consistent and untampered since anchoring.

- Any mismatch indicates data alteration, corruption, or an invalid proof.

No trust in the operator, infrastructure, or user interface is required for this verification process.