Turn digital events, AI outputs, and release binaries into tamper-evident, verifiable proof.
Zero-Auth. Zero-Storage. O(log N) Merkle Batching on The Open Network (TON).
π Web Platform β’ β‘ Interactive Playground β’ π€ Telegram Bot β’ π Documentation β’ π€ llms.txt
"Don't trust ProofCore. Verify the mathematical proof yourself."
ProofCore is not a centralized SaaS notary. It is a cryptographic commitment protocol designed to bridge human communication, DevOps release chains, and autonomous AI agents with the TON Blockchain.
- Payload Integrity (SHA-256): Verifies the raw bytes have not changed.
- Batch Inclusion (O(log N) Merkle Trees): Proves an individual item belongs to an anchored batch without requiring access to other batch data.
- Timestamped Existence: Anchors the root cryptographic commitment into an immutable TON Blockchain block transaction.
- Zero-Storage Architecture: Raw user files and private datasets are never stored on-chain. Only the 64-character Merkle Root is committed publicly.
| Repository | Distribution Channel | Target Audience | Description |
|---|---|---|---|
proofcore |
pip install proofcore |
Python, AI & Web3 Devs | Core Python SDK, LangChain/CrewAI tools, and ProofRegistry.tact contracts. |
proofcore-mcp |
uvx proofcore-mcp |
Cursor, Claude Desktop | Model Context Protocol (MCP) server for autonomous AI audit notarization. |
proofcore-action |
GitHub Marketplace | DevOps, Security Teams | CI/CD Action to notarize release binaries and SBOMs with GitHub OIDC authentication. |
cursor-web3-auditor |
cursor.directory |
Smart Contract Auditors | Cursor IDE (.mdc) rule to automatically seal security audit verdicts. |
pip install proofcorefrom proofcore import seal, verify
# 1. Seal an artifact anonymously (Zero-Auth / Zero-Storage)
receipt = seal(
content="Security Audit: Vault.sol passed with 0 Critical issues.",
agent_id="Claude-3.5-Sonnet",
title="Vault.sol Audit Report"
)
print(f"Verified URL: {receipt['verification_url']}")
print(f"Citation Badge: {receipt['citation']}")
# 2. Programmatically verify authenticity (M2M)
result = verify(
deal_id=receipt["deal_id"],
content="Security Audit: Vault.sol passed with 0 Critical issues."
)
assert result["valid"] is TrueRun instantly without installation:
# Claude Code CLI
claude mcp add proofcore https://mcp.proofcore.orgOr add to your .cursor/mcp.json / claude_desktop_config.json:
{
"mcpServers": {
"proofcore": {
"url": "https://mcp.proofcore.org"
}
}
}Automatically hash compiled release binaries on GitHub runners and anchor them to TON:
name: Release & Notarize
on:
release:
types: [published]
permissions:
id-token: write # Required for Cryptographically Proven GitHub OIDC Identity
contents: read
jobs:
notarize:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: ProofCore Notary
uses: ProofCore-Protocol/proofcore-action@v1
with:
files: "dist/*.tar.gz, dist/*.whl"
title: "Release ${{ github.ref_name }}"Every proof anchored by the protocol can be exported into an air-gapped, self-contained Evidence Archive (GET /api/download/{deal_id}):
proof_evidence_package.zip
βββ π 1_ORIGINAL_ASSET/ β Unmodified raw payload (HTML, PDF, Media)
βββ π 2_PROOF_DATA/ β proof.json (Merkle path) + forensic_metadata.json
βββ π 3_VERIFIERS/ β verify.html & verify.py (100% Offline 3-Way Match)
βββ π 4_LEGAL_CERTIFICATE/ β FRE 902(14) / eIDAS PDF with verification QR
βββ π 5_README/ β Offline audit instructions
Local Asset SHA-256 ββ(+ Siblings)βββΊ Calculated Root == Manifest Root == TON Block Payload
[ Merkle Root ] βββ Committed to TON (Opcode 0 payload: "MR: <root>")
/ \
Hash(0-1) Hash(2-3)
/ \ / \
H(A) H(B) H(C) H(D)
- 1. Asset Digest:
H_asset = SHA256(raw_bytes) - 2. Metadata Digest:
H_meta = SHA256(forensics_json_bytes) - 3. Combined Deal Hash:
H_deal = SHA256( (H_asset_1 + ... + H_asset_n + H_meta).encode('utf-8') ) - 4. Tree Traversal: For each sibling in
merkle_path:direction == 'left'βH_next = SHA256( (sibling + H_current).encode('utf-8') )direction == 'right'βH_next = SHA256( (H_current + sibling).encode('utf-8') )
- πΊπΈ US Federal Rules of Evidence (FRE 902): Rule 902(14) establishes that electronic data authenticated by a certified digital identification process (cryptographic hash) is self-authenticating in judicial proceedings.
- πͺπΊ EU eIDAS Regulation (EU No 910/2014): Article 41(1) recognizes electronic time stamps as legally admissible evidence, prohibiting denial of legal effect solely due to electronic form.
- βοΈ The "Proof is Not Truth" Distinction: ProofCore cryptographically certifies Integrity (bytes match), Inclusion (belongs to the batch), and Existence (anchored at time T). It does not evaluate the factual truthfulness of the underlying claims.
- Main Platform: proofcore.org
- Interactive Explainer: proofcore.org/learn
- Developer API Sandbox: demo.proofcore.org
- Hosted MCP Server:
https://mcp.proofcore.org - OpenAPI 3.1.0 Specification: proofcore.org/openapi.json
- Machine-Discovery Manifest: proofcore.org/llms.txt