Every artifact in this repository is anchored to Bitcoin.
Verify any .proof file at verify-anchoring.org.
A .proof file is a self-contained evidence bundle that proves a specific file existed at a specific moment in time — anchored in the Bitcoin blockchain.
release.tar.gz ← the artifact
release.tar.gz.proof ← the proof (certificate + OTS)
The proof is independently verifiable. No account, no vendor, no trust required.
examples/ci/
├── build-output.tar.gz
└── build-output.tar.gz.proof
Anchored automatically via GitHub Action:
- uses: AnchoringTrust/anchor-action@v1
with:
file: build-output.tar.gz
env:
UMARISE_API_KEY: ${{ secrets.UMARISE_API_KEY }}examples/ai/
├── model-v2.1.pt
└── model-v2.1.pt.proof
Proves this exact model existed at this exact time. Useful for:
- Training provenance
- Audit trails
- Regulatory compliance
examples/data/
├── training-data-2026-03.parquet
└── training-data-2026-03.parquet.proof
Proves the dataset was not modified after anchoring.
examples/release/
├── myapp-v1.0.0.tar.gz
├── myapp-v1.0.0.tar.gz.proof
└── SHA256SUMS
.proof sits alongside SHA256 and GPG signatures as standard release artifacts.
Drop any .proof file at verify-anchoring.org.
100% client-side. Nothing is uploaded.
npx @umarise/cli verify build-output.tar.gz.proof
# Hash Match ✓ | Bitcoin Block #881234 | 2026-03-05 | VALIDunzip build-output.tar.gz.proof
sha256sum build-output.tar.gz # compare with certificate.json
ots verify proof.ots # verify against Bitcoinnpx @umarise/cli anchor myfile.pdf
# → myfile.pdf.proof- uses: AnchoringTrust/anchor-action@v1
with:
file: myfile.pdf
env:
UMARISE_API_KEY: ${{ secrets.UMARISE_API_KEY }}Node.js:
npm install @umarise/anchorPython:
pip install umarise-core-sdkGet an API key at umarise.com/developers.
- Umarise — Anchoring Infrastructure
- API Reference
- Independent Verifier
- Anchoring Specification (IEC)
- GitHub Action
Unlicense (Public Domain)