Verifiable digital evidence infrastructure.
SigmaProof is an open evidence protocol and planned reference implementation for independently verifying the integrity, existence, provenance assertions, and history of digital objects. Documents stay in their existing systems; customers retain portable evidence that can be verified without SigmaProof's servers.
Status: experimental local proof tooling · Concept: v0.2 · September 2026
The CLI can create explicitly unanchored private packages and verify local document integrity and batch membership. An internal transactional store and opt-in development HTTP endpoints support ingestion, frozen batches and pending submission records. Paperless integration and authenticated Celestia proofs are not implemented yet. Specifications and binary profiles remain experimental drafts, not an interoperable protocol release.
flowchart TD
D[Paperless / S3 / SharePoint / enterprise systems] --> A[Integration agent]
A --> E[Commitments and lifecycle evidence]
E --> B[Merkle batches]
B --> C[Celestia]
B --> O[Bitcoin / OpenTimestamps]
B --> T[EU trust services / qualified ledgers]
C --> P[Portable .sigmaproof package]
O --> P
T --> P
P --> V[Independent CLI / browser / SDK verification]
Anchors and trust services are parallel providers of different assertions. No particular provider defines the protocol.
Make a Paperless-ngx document independently tamper-evident with a portable proof anchored to Celestia. Verification must succeed after historical blob retrieval is disabled, using preserved proof material and explicitly authenticated anchor state.
- Keep authoritative documents in their original systems.
- Publish only opaque randomized commitments; never document contents or identifying metadata.
- Export evidence that belongs to the customer.
- Verify using open specifications without contacting SigmaProof.
- Separate cryptographic validity, anchor authentication, and evidence-policy satisfaction.
- Preserve old evidence and renew it as algorithms and trust systems evolve.
Integrity does not establish that document contents are true, that an uploader was authorized, or that a workflow meets legal requirements. Qualification must be established for the specific trust service; a public blockchain is not automatically a qualified ledger.
| Area | Entry point |
|---|---|
| Product and scope | Product brief |
| Documentation | Documentation index |
| Architecture | System architecture |
| Protocol | SEP draft index |
| Delivery | Roadmap and GitHub milestones |
| Security | Threat model and reporting |
| Contributing | Contributor guide |
Use Go 1.27.1 and Python 3.9+ for implementation and documentation checks:
git clone https://github.com/SigmaUno/sigmaproof.git
cd sigmaproof
make check build
./bin/sigmaproof version
./bin/sigmaproofd -listen 127.0.0.1:8080 -store ./sigmaproof.dbWithout -store, the daemon serves /healthz (200) and /readyz (503). With a private local store it enables experimental ingestion, batching, pending outbox listing and unanchored package export endpoints, and refuses non-loopback listen addresses because there is no authentication. sigmaproof verify --offline checks local integrity; default verification exits 3 because anchor authentication is unavailable. See the local CLI walkthrough. There is no provider worker or production deployment yet.
Target: October 8, 2026 testnet developer preview, conditional on the four-week release plan and all MVP gates.
Licensing is undecided, pending the project owner's selection before public launch.