ALCOA RubberStamp
Create a deterministic commitment to a directory of files, verify it later, and optionally submit that commitment through OpenTimestamps.
Download ZIPSafe default
The commitment and verification engine uses only the Python standard library. It makes no network call unless you explicitly supply --ots or --ots-receipt.
python alcoa_rubberstamp.py create --root /path/to/records
Verify the same file set later:
python alcoa_rubberstamp.py verify \ --root /path/to/records \ --manifest /path/to/alcoa-manifest-<UTC>.json \ --commitment-file /path/to/alcoa-commitment-<UTC>.txt
What it commits to
- Unicode-NFC normalized relative paths
- File sizes and SHA-256 content digests
- A versioned, domain-separated Merkle construction
- An optional independently verifiable prior-state document
Time claims
A local commitment alone makes no time claim. A successfully verified external timestamp can establish an upper bound. A fresh, authentic prior-state binding plus a verified later timestamp can support a two-sided commitment interval.
Deliberate limits
This is inspectable reference software, not a validated GMP system. It does not supply identity, authorization, electronic signatures, workflow integration, retention governance, scientific correctness, or regulatory compliance.
Release integrity
ZIP SHA-256
62b1f41ec434c6d5d38d540b7e0762875c2a889cc913c4a8e34eac038f804805