Exact bytes and commitment field scope
Reproduce the digest without adding fields that were never committed.
No. SHA-256 equality compares entered content to a digest. Time needs a separately verified attestation.
Verification methods and user-led checklists. No provider has been certified by this site; declared coverage counts are not independently checked.
No. SHA-256 equality compares entered content to a digest. Time needs a separately verified attestation.
No. Existence of bytes is not evidence that each subscriber received an actionable instruction in time.
No. Duplicates can offset missing records. Reconcile exact IDs, versions and periods as well as totals.
Reproduce the digest without adding fields that were never committed.
Keep calendar acceptance, completed proof and chronology interpretation separate.
Reconcile identities and status rules before interpreting a proof percentage.
No. The file checker computes SHA-256, the ID checker compares declared records and the chronology checker compares supplied UTC labels. No .ots parser, chain verification or real provider transcript is implemented. OpenTimestamps documentation is linked for an appropriate actual verification environment. No personal-computer production verifier is created.
Its labels were authored for teaching. Real preimages, receipts, subscriber arrival and broker fills are null. A complete population comparison checks membership consistency, not the source roster's truth. The calculators and release tests are software checks. They cannot be cited as an independent audit or strategy-validation sample.