Regulatory evidence, sealed.
Every pack is an append-only artifact with a hash of its own. In a deployment you check it against the signed root for that day and get an inclusion proof for the record plus a check of the chain around it. Below, the same digest, computed by your browser on a file of your choosing, so the method is not something you have to take on faith.
Evidence pack registry
| Artifact | Period | Coverage | State |
|---|---|---|---|
| Q3_SOC2_PACK.zip0x7F2A...9B1C | 2024-Q3 | 98.4% | Sealed |
| ISO27001_AUDIT.pdf0x3E1B...4C8F | 2024-H1 | 100.0% | Signed |
| GDPR_COMPLIANCE_SEP.xmlPENDING_SYNC | 2024-09 | 92.1% | Syncing |
| FINANCIAL_LEDGER_Q2.csv0x9A4D...1E2B | 2024-Q2 | 99.9% | Sealed |
- Artifact
- Q3_SOC2_PACK.zip0x7F2A...9B1C
- Period
- 2024-Q3
- Coverage
- 98.4%
- State
- Sealed
- Artifact
- ISO27001_AUDIT.pdf0x3E1B...4C8F
- Period
- 2024-H1
- Coverage
- 100.0%
- State
- Signed
- Artifact
- GDPR_COMPLIANCE_SEP.xmlPENDING_SYNC
- Period
- 2024-09
- Coverage
- 92.1%
- State
- Syncing
- Artifact
- FINANCIAL_LEDGER_Q2.csv0x9A4D...1E2B
- Period
- 2024-Q2
- Coverage
- 99.9%
- State
- Sealed
Verify a file yourself
Drop any file. It is hashed in this browser with Web Crypto and never leaves your machine. The whole point is that the person who needs to check does the checking.
or drop one here
Cryptographic proof · sample
- Status
- Verified
- Ledger block
- #14,982,304
- Timestamp
- 2024-10-27T14:32:01Z
Signature 0x3044…e5f6
If a single byte changed since sealing, verification fails. That’s the point.