Cryptographic provenance for claims and creators.
Ed25519 signatures, RFC 3161 timestamps, and attestation chains — packaged as two CLI-first .NET libraries with 590 tests.
Claim
dotnet run --project ClaimLedger.Cli -- assert claim.json
Attest
dotnet run --project CreatorLedger.Cli -- attest asset.png
Test
dotnet test ledger-suite.sln # 590 tests
Why Ledger Suite
Portable, offline-first cryptographic proof.
Ed25519 signed
Every claim, citation, and attestation carries a cryptographic signature. No blockchain, no third party.
RFC 3161 timestamps
Non-repudiation via trusted timestamping authorities. Proves when a claim was made.
590 tests
ClaimLedger (371) + CreatorLedger (219). Runs on every push with Windows CI for DPAPI coverage.
The Ledgers
Two ledgers, one shared crypto layer.
Quick start
Build & test
git clone https://github.com/mcp-tool-shop-org/ledger-suite.git
cd ledger-suite
dotnet build ledger-suite.sln
dotnet test ledger-suite.sln ClaimLedger CLI
# Assert a claim with Ed25519 signature
dotnet run --project src/ClaimLedger/ClaimLedger.Cli -- assert claim.json
# Publish a ClaimPack bundle
dotnet run --project src/ClaimLedger/ClaimLedger.Cli -- publish ClaimLedger
Scientific claim provenance.
Assertions
Sign claims with Ed25519 keys. Each assertion is a self-contained cryptographic proof.
Citations & attestations
Link claims together. Peer review, reproduction, and institutional approval — all signed.
ClaimPacks
Bundle claims, citations, and attestations into portable packages for offline verification.
CreatorLedger
Creator attestation proofs.
Content hashing
SHA-256 content hashes bind attestations to specific file versions.
Multi-party chains
Build attestation chains across multiple signers for collaborative provenance.
Proof bundles
Export portable proof bundles that verify without network access.