BitGraph

Applications

Different products. One recording step.

BitGraph does not replace a provenance product; it sits under one. Whatever your system already produces, an asset, a credential, a log entry, a release, its SHA-256 is bound by the enclave and the proof travels with it. These are integration patterns on the same interface. Two of them run on this site today.

Patterns, not partnerships: no company named or implied here uses BitGraph.

Content Credentials

Signed history, plus an attested recording.

Today	A C2PA manifest carries signed assertions about an asset: who signed it, what tool made it, the edits.
BitGraph adds	An independent record that these exact bytes, asset and manifest together, were bound after an unpredictable moment, at a counted position, inside a window of public time. The signer's own clock is not the only clock.
What is bound	The asset's SHA-256 and the manifest store's, as two leaves of one tree, bound as one BitGraph. Nothing in the asset changes, so the manifest's own hashes stay valid.
What you get back	A BitGraph proof kept beside the asset or referenced from your system; each leaf checks on its own.

Running now: a ChatGPT image and its OpenAI-signed credential, bound together and verifiable offline.

Finding the original

A copy finds the record. The record proves the bytes.

Today	A watermark, or a perceptual search, leads from a copy back to an identity or a database entry: whatever the database says today.
BitGraph adds	The entry becomes a verifiable recording: the original's exact bytes and a perceptual fingerprint, bound together when the original was recorded. A match, by watermark or by looks, says a copy resembles the original; the original's bytes are what prove it.
What is bound	The original's SHA-256 and a fingerprint record, in one tree. A watermark can carry a pointer to that BitGraph; the fingerprint lets a copy find it with no watermark at all.
What you get back	The original's proof, reached from any copy that still looks like it.

Running now: Check matches a stripped copy to the original's bound record by its looks, with no watermark at all.

Trusted capture

How it was captured, and when it was recorded.

Today	A controlled capture pipeline produces evidence about how an image or recording was made, on what device.
BitGraph adds	Order and a time window for the capture artifact that do not rest on the device's clock or the vendor's database. BitGraph does not see or vouch for the physical event; it fixes when the artifact's bytes were bound.
What is bound	The capture artifact's SHA-256, or its signed capture record, as soon as it leaves the device.
What you get back	A proof that pairs with the capture evidence; each can be checked without the other's issuer.

Asset registries

Registration events anyone can check outside the registry.

Today	Assets and their provenance records are registered and looked up inside one ecosystem.
BitGraph adds	Each registration, or each batch of them, gets a recording that verifies with an open tool and the published enclave measurement, independently of the registry's own servers.
What is bound	A registration record's SHA-256, or the root of a batch of them.
What you get back	Per-registration proofs, or one proof per batch with an inclusion path for each entry.

AI agents and audit

What an agent did, bracketed and in order.

Today	Agent platforms keep logs of actions, tool calls and outputs, in their own storage.
BitGraph adds	Two BitGraphs bracket a run: everything bound between them came after the first and before the second, in counted order. Work made from the first one's nonce could not have existed before it.
What is bound	Each action or log segment's SHA-256, or a log root per step. An MCP server makes this one tool call for any agent.
What you get back	A chain of proofs that orders the run and checks offline.

Running now: The sealed exam: questions from A's nonce, answers bound as B.

Software supply chain

Artifacts recorded at build time.

Today	Build systems sign artifacts and publish attestations; transparency logs make those entries public.
BitGraph adds	An attested recording of the artifact or its bill of materials at a counted position, from hardware whose build is published. It sits beside signatures and transparency-log entries rather than replacing them.
What is bound	The artifact's SHA-256, or a release's tree of artifacts as one BitGraph.
What you get back	A proof per release, each artifact checkable on its own.

Research and enterprise records

Large collections, one recording each.

Today	Lab notebooks, datasets, contracts and logs are kept in systems their own operators control.
BitGraph adds	A whole collection, thousands of files at a time, bound as one tree in one BitGraph; any single file proves its inclusion without the others being disclosed.
What is bound	The root of an RFC 6962 Merkle tree over the files' SHA-256s.
What you get back	One proof for the collection and an inclusion path for each file.

Your product

Something else in mind?

Anything that can be hashed can be recorded. Tell us what your product produces and where the recording step would sit.

Evaluate the technology Talk with us

Different products. One recording step.

Patterns, not partnerships: no company named or implied here uses BitGraph.

Signed history, plus an attested recording.

Today	A C2PA manifest carries signed assertions about an asset: who signed it, what tool made it, the edits.
BitGraph adds	An independent record that these exact bytes, asset and manifest together, were bound after an unpredictable moment, at a counted position, inside a window of public time. The signer's own clock is not the only clock.
What is bound	The asset's SHA-256 and the manifest store's, as two leaves of one tree, bound as one BitGraph. Nothing in the asset changes, so the manifest's own hashes stay valid.
What you get back	A BitGraph proof kept beside the asset or referenced from your system; each leaf checks on its own.

A copy finds the record. The record proves the bytes.

Today	A watermark, or a perceptual search, leads from a copy back to an identity or a database entry: whatever the database says today.
BitGraph adds	The entry becomes a verifiable recording: the original's exact bytes and a perceptual fingerprint, bound together when the original was recorded. A match, by watermark or by looks, says a copy resembles the original; the original's bytes are what prove it.
What is bound	The original's SHA-256 and a fingerprint record, in one tree. A watermark can carry a pointer to that BitGraph; the fingerprint lets a copy find it with no watermark at all.
What you get back	The original's proof, reached from any copy that still looks like it.

How it was captured, and when it was recorded.

Today	A controlled capture pipeline produces evidence about how an image or recording was made, on what device.
BitGraph adds	Order and a time window for the capture artifact that do not rest on the device's clock or the vendor's database. BitGraph does not see or vouch for the physical event; it fixes when the artifact's bytes were bound.
What is bound	The capture artifact's SHA-256, or its signed capture record, as soon as it leaves the device.
What you get back	A proof that pairs with the capture evidence; each can be checked without the other's issuer.

Registration events anyone can check outside the registry.

Today	Assets and their provenance records are registered and looked up inside one ecosystem.
BitGraph adds	Each registration, or each batch of them, gets a recording that verifies with an open tool and the published enclave measurement, independently of the registry's own servers.
What is bound	A registration record's SHA-256, or the root of a batch of them.
What you get back	Per-registration proofs, or one proof per batch with an inclusion path for each entry.

What an agent did, bracketed and in order.

Today	Agent platforms keep logs of actions, tool calls and outputs, in their own storage.
BitGraph adds	Two BitGraphs bracket a run: everything bound between them came after the first and before the second, in counted order. Work made from the first one's nonce could not have existed before it.
What is bound	Each action or log segment's SHA-256, or a log root per step. An MCP server makes this one tool call for any agent.
What you get back	A chain of proofs that orders the run and checks offline.

Artifacts recorded at build time.

Today	Build systems sign artifacts and publish attestations; transparency logs make those entries public.
BitGraph adds	An attested recording of the artifact or its bill of materials at a counted position, from hardware whose build is published. It sits beside signatures and transparency-log entries rather than replacing them.
What is bound	The artifact's SHA-256, or a release's tree of artifacts as one BitGraph.
What you get back	A proof per release, each artifact checkable on its own.

Large collections, one recording each.

Today	Lab notebooks, datasets, contracts and logs are kept in systems their own operators control.
BitGraph adds	A whole collection, thousands of files at a time, bound as one tree in one BitGraph; any single file proves its inclusion without the others being disclosed.
What is bound	The root of an RFC 6962 Merkle tree over the files' SHA-256s.
What you get back	One proof for the collection and an inclusion path for each file.

Applications.

Different products. One recording step.

Signed history, plus an attested recording.

A copy finds the record. The record proves the bytes.

How it was captured, and when it was recorded.

Registration events anyone can check outside the registry.

What an agent did, bracketed and in order.

Artifacts recorded at build time.

Large collections, one recording each.

Something else in mind?

Applications.

Different products. One recording step.

Signed history, plus an attested recording.

A copy finds the record. The record proves the bytes.

How it was captured, and when it was recorded.

Registration events anyone can check outside the registry.

What an agent did, bracketed and in order.

Artifacts recorded at build time.

Large collections, one recording each.

Something else in mind?