PROOFLINK · THE LIVE AI-ACCOUNTABILITY STANDARD
85,000+ AI actions cryptographically sealed and publicly verifiable — right now, not a spec. SHA-256 hash-chained, Ed25519-signed, Bitcoin-anchored.
Independently verifiable. Go check it yourself — no account required.
The Problem
Nobody can prove what they did.
Your AI fixed it. But when the auditor asks "show me what happened" — you have a log file that could have been altered.
EU AI Act Article 12 applies from August 2, 2026. Automatic, tamper-evident logging. €15M or 3% of global turnover. Your ELK stack doesn't qualify.
Datadog sees it. ServiceNow tickets it. Neither proves it.
The Solution
One receipt. Five questions. Mathematically undeniable.
Each receipt hashes to the next. The chain terminates in Bitcoin. Tamper one — the rest break.
Connect anything, prove everything
Not another vendor silo. Reach ProofLink two ways — every connected action seals a receipt.
mcp.itechsmart.dev — v2.2.0, 60+ tools, Bearer auth + rate limiting, A2A agent-card protocol 0.3.0. AI agents connect directly and every tool call seals a ProofLink receipt.
api.itechsmart.dev/v1 — sub-150ms, structured errors, Swagger at /docs. Non-agent backends integrate over plain REST; receipt-per-call.
Public verify API: verify.itechsmart.dev — /api/verify/<id>, /api/anchors, /api/export. Anyone verifies independently.
Connector fleet for AWS, Kubernetes (kubectl), Prometheus, network gear (netmiko — Cisco IOS/NX-OS), ServiceNow, Splunk and Wazuh — every connected action seals a receipt. Datadog and ServiceNow logs are per-vendor and self-attested; ProofLink is cross-vendor and publicly anchored.
Install the SDK. Verify a receipt. Seal in server mode.
pip install prooflink # or: npm i @itechsmart/prooflink
import prooflink
r = prooflink.fetch("c58347c60394a21f") # any receipt on the public chain
assert prooflink.verify(r) # ✓ hash + Ed25519 verifiedOn a host with the canonical append.py, seal() generates a receipt in real time — SHA-256 hash chain + Bitcoin OTS anchoring.
Anyone can verify. No account. verify.itechsmart.dev — recompute the hash, re-derive the canonical form, check Ed25519.
Open Verifier →Three independent reviewers re-derived the crypto on live receipts — the published verifier passes.
— Verification review, 2026
The standard is the map. iTechSmart is the territory — a public chain you can verify in your browser.
— Competitive assessment, 2026
When the auditor asks "prove what your AI did," you hand them a receipt they verify themselves — offline, without trusting us.
— Regulated-buyer one-liner
Market directly to the mandate
Prove what your AI did. Here is the ProofLink field that satisfies each mandate.
High-risk AI must automatically record events over its lifetime with traceability. Penalty: up to €15M or 3% of global turnover.
Every AI action seals a receipt (timestamp / actor / action / subject / outcome / details) into an append-only, hash-chained, tamper-evident ledger.
Security & resilience evaluated and documented; post-deployment monitoring implemented.
Security / remediation actions documented as signed immutable receipts; the autonomous loop seals a receipt for every detection + action; human_input flags oversight.
Create, protect, retain audit records; ensure integrity.
Cryptographically integrity-protected receipts; retention via the immutable chain; offline-verifiable without trusting the producer.
Monitor for anomalies; evaluate security events; controlled change management.
Anomaly / telemetry receipts; signal_classified / security receipts; config_change receipts (device / change_type / before_hash / after_hash / diff) with authorization captured.
Retain documented evidence of monitoring / measurement results.
The receipt ledger IS the retained, integrity-provable evidence; live receipts already emit iso_42001 control mappings.
High-risk AI systems must keep automatic, tamper-evident logs over their lifetime. Traditional logs, ELK stacks and Datadog dashboards don't satisfy the record-keeping requirement on their own.
The Difference
“An auditor can verify this receipt without calling us. That's not a log. That's proof.”
LedgerProof, OVERT and VeritasChain published specs. iTechSmart runs the live chain.
ProofLink doesn't replace any of these. It adds a publicly-anchored proof layer on top of all of them.
The difference between “trust us” and “verify yourself.”
Try to fake a receipt. Then explain to the judge why the Bitcoin blockchain disagrees.
Pick a tier, check out with Stripe, and get your API key + SDK quickstart on the spot.
Your key is scoped to verify + read + SDK-against-sandbox. Self-serve sealing into the production ledger is in private beta — talk to us to enable it.
For teams standing up their first audit trail.
For regulated teams shipping to auditors.
For enterprises and gov / defense programs.
Every membership seals a ProofLink receipt for the subscription itself — verifiable at verify.itechsmart.dev.
Paste any receipt ID. No account. Recompute the crypto yourself.
Be provable.