// Evidence pipeline

Every event.
One proof layer.

Proofstream is the evidence pipeline at the core of Attesto 2.0. It receives events from any source, processes them into tamper-evident proof objects, and makes each one independently verifiable.

// What Attesto proves

Every category of digital event.

[ AI ]

AI decisions

Model inference, prompt hash, output hash, model version, human override, policy check, risk classification.

[ App ]

Application activity

API call, process step, approval, access event, configuration change, business process step.

[ Cyber ]

Cyber incidents

Detection, escalation, containment, remediation, approval receipts, recovery milestones.

[ Data ]

Data movement

Transfer event, location claim, storage commitment, processing record, deletion proof, retention evidence.

[ Content ]

Digital content

C2PA manifest, media hash, edit chain, publication proof, distribution record.

[ Audit ]

Audit activity

Review event, control evidence, auditor receipt, policy check, compliance milestone.

// How to connect

Four ways to submit events.

[ 01 ]

SDK

Embed the Attesto SDK directly in your application or AI system to submit events programmatically.

[ 02 ]

REST API

Submit events via HTTP POST from any platform, script, or system that can make web requests.

[ 03 ]

Connectors

Install marketplace connectors that forward events from existing tools into Proofstream automatically.

[ 04 ]

Batch

Import structured batches of historical records or high-volume event streams via bulk upload.

// Full Proofstream lifecycle

From event to independently verifiable bundle.

[ 01 ]

Event

A system action is submitted to Attesto via SDK, API, or connector.

[ 02 ]

Receipt

A signed receipt is returned immediately — the first layer of cryptographic verification.

[ 03 ]

Window

Events are grouped into closed windows with inclusion proofs and window commitments.

[ 04 ]

Checkpoint

Stream-head commitments capture cryptographic snapshots of the full evidence stream state.

[ 05 ]

Witness

Independent witnesses attest to checkpoint validity. Conflicting histories produce fork evidence automatically.

[ 06 ]

Anchor

Checkpoint roots are anchored externally, creating a time-stamped commitment independent of Attesto.

[ 07 ]

Bundle

A portable Truth Package is assembled: receipts, windows, checkpoints, witness statements, and anchors in one verifiable archive.

// Witness plane

No single party controls your evidence integrity.

The witness plane ensures independent attestation at every checkpoint. When evidence histories conflict, fork evidence is generated automatically — machine-readable proof of what happened, not a hidden dispute.

[ 1-of-1 ]

Single quorum

One witness must attest for checkpoints to be accepted. Simpler configuration for internal or low-risk streams.

[ 2-of-3 ]

Supermajority quorum

Two of three witnesses must agree. Stronger fork detection for regulated or high-stakes evidence streams.

// Fork detection

Conflicting histories become evidence.

If a system attempts to rewrite its evidence history, the witness plane detects the conflict. Instead of a silent disagreement, Attesto generates fork evidence: machine-readable proof of the conflict, who reported it, and when.

Start building your evidence pipeline.

Book a demo