Supermultiverse LLC · BDO-EVIDENCE-01

Technical provenance evidence for digital content.

BDO Evidence validates the origin of a piece of content (its C2PA credentials, its signature, its AI declaration), records the result in a signed document and anchors it in Bitcoin and in a European qualified timestamp. Any third party can repeat the verification years from now, without depending on us.

Request a meeting or pilot See the result

verification_resultbdo-evidence-01 · illustrative example

subject: anchor_request
exact_match: match
content_integrity: valid
c2pa.signature: valid
c2pa.trust_status: trusted
creator.binding: valid
ai_generation: no_signed_declaration
existence.bitcoin: confirmed · block 912 480
existence.qets: valid
mode: replay_original

What it is

A technical evidence service on the origin of digital content

BDO Evidence takes a piece of digital content (image, audio, video, document), checks its provenance against published, versioned rules and records the result in a signed record. That record is anchored in Bitcoin and sealed with a European qualified timestamp. What we deliver is an evidence package that an auditor, a judge or a client can verify again years from now with an open-source verifier. If the content carries no credentials, the result says so, and that is evidence too.

C2PA is the open content-credentials standard that cameras, editing tools and generative models are already adopting. BDO Evidence validates those credentials; it does not create them.

Who it is for

Whoever generates or distributes AI content

and must be able to show an authority that the marking required by Article 50 existed and was validated on a given date.

Compliance consultancies and partners

that guide their clients on transparency and traceability and need independent technical proof to put in their reports.

Media, agencies and legal departments

that need to prove the origin and integrity of a piece of content in a dispute, a claim or an audit.

Three guarantees

The whole validation is proven, not a loose hash

The signed record binds the content, its C2PA manifest, the validation profile and the result obtained. What is proven before the block is the entire validation, not a loose hash.

Reproducible years from now

The Evidence Bundle freezes the evaluation context: exact validator version, trust lists, revocation responses and the instant evaluated. An auditor repeats the validation with the same inputs and reaches the same verdict.

Verifiable without us

The evidence package is designed to be verified without our infrastructure, without our live keys and without our permission: records, proofs and the anchored key history travel in the export, and the open-source verifier ships with the first release.

We sell evidence, not truth: the result states exactly what was checked, under which rules and what came out, and nothing more.

Art. 50

EU AI Act · Article 50

Since 2 August 2026, AI-generated or manipulated content must be marked and detectable.

Article 50 of the EU Artificial Intelligence Act requires whoever generates or distributes synthetic content (image, audio, video or text) to mark it in a machine-readable format and to disclose deep fakes. Saying it was done is no longer enough: you have to be able to prove it.

Non-compliance can be fined with up to EUR 15 million or 3% of total worldwide annual turnover, whichever is higher (for SMEs, whichever is lower), on top of reputational damage and the burden of proof in any dispute about a content's origin.

BDO Evidence does not certify compliance and does not replace legal advice. It provides what an internal log cannot: independent, reproducible evidence, anchored in Bitcoin and in a European qualified timestamp, that your content's marking and provenance were validated and existed on a specific date. Presentable to authorities, clients and auditors years later, without depending on us.

Request a meeting

Where it fits

Each tool answers a different question

Electronic signatures, timestamps, evidence certification services and content-credential verifiers solve real problems, and some of them are components of BDO Evidence. None of them answers the auditor's question on its own: what was validated about this content, under which rules, with what result and when?

Comparison between timestamps, electronic signatures, evidence certification, C2PA verifiers and BDO Evidence
	Timestamp / hash on a blockchain	Electronic signature (eIDAS, qualified)	Evidence certification by a trusted third party	Content-credential verifier (C2PA)	BDO Evidence
The question it answers	Did these bytes exist before this date?	Who signed this document, and is it intact?	What did the third party see at that moment?	Is this file's manifest valid today?	What was validated about this content, under which rules, with what result and when?
Who vouches for the result	Bitcoin (nobody who can disappear) or the provider	The qualified provider and the signer	The provider: its log, its seal	Nobody: a one-off check that is not preserved	Signed record + Bitcoin + qualified timestamp
Validated C2PA provenance	No	No	No	Yes, with today's context	Yes, under a frozen, versioned profile
Result preserved and reproducible years later	Not applicable	Partial, depends on the provider	Depends on the provider	No	Yes (Evidence Bundle: validator, trust lists, revocation, instant)
Per-dimension verdict with an explicit “not checked”	No	No	No	Partial	Yes, nine dimensions
Verifiable without the provider	Yes (hash) / depends (timestamp)	Depends on the provider	Usually not	Yes, but only in the present	Yes: complete export and open verifier (first release)
Privacy: blinded commitments and withdrawal from publication	No	No	Partial	Not applicable	Yes
Open standard, integrable via API	Yes (OpenTimestamps) / no	Standard yes, integration depends on the provider	No	Yes (C2PA)	Yes (specification, schemas and OpenAPI; public with the v0.2.3 freeze)

The question it answers

Timestamp / hash on a blockchain: Did these bytes exist before this date?
Electronic signature (eIDAS, qualified): Who signed this document, and is it intact?
Evidence certification by a trusted third party: What did the third party see at that moment?
Content-credential verifier (C2PA): Is this file's manifest valid today?
BDO Evidence: What was validated about this content, under which rules, with what result and when?

Who vouches for the result

Timestamp / hash on a blockchain: Bitcoin (nobody who can disappear) or the provider
Electronic signature (eIDAS, qualified): The qualified provider and the signer
Evidence certification by a trusted third party: The provider: its log, its seal
Content-credential verifier (C2PA): Nobody: a one-off check that is not preserved
BDO Evidence: Signed record + Bitcoin + qualified timestamp

Validated C2PA provenance

Timestamp / hash on a blockchain: No
Electronic signature (eIDAS, qualified): No
Evidence certification by a trusted third party: No
Content-credential verifier (C2PA): Yes, with today's context
BDO Evidence: Yes, under a frozen, versioned profile

Result preserved and reproducible years later

Timestamp / hash on a blockchain: Not applicable
Electronic signature (eIDAS, qualified): Partial, depends on the provider
Evidence certification by a trusted third party: Depends on the provider
Content-credential verifier (C2PA): No
BDO Evidence: Yes (Evidence Bundle: validator, trust lists, revocation, instant)

Per-dimension verdict with an explicit “not checked”

Timestamp / hash on a blockchain: No
Electronic signature (eIDAS, qualified): No
Evidence certification by a trusted third party: No
Content-credential verifier (C2PA): Partial
BDO Evidence: Yes, nine dimensions

Verifiable without the provider

Timestamp / hash on a blockchain: Yes (hash) / depends (timestamp)
Electronic signature (eIDAS, qualified): Depends on the provider
Evidence certification by a trusted third party: Usually not
Content-credential verifier (C2PA): Yes, but only in the present
BDO Evidence: Yes: complete export and open verifier (first release)

Privacy: blinded commitments and withdrawal from publication

Timestamp / hash on a blockchain: No
Electronic signature (eIDAS, qualified): No
Evidence certification by a trusted third party: Partial
Content-credential verifier (C2PA): Not applicable
BDO Evidence: Yes

Open standard, integrable via API

Timestamp / hash on a blockchain: Yes (OpenTimestamps) / no
Electronic signature (eIDAS, qualified): Standard yes, integration depends on the provider
Evidence certification by a trusted third party: No
Content-credential verifier (C2PA): Yes (C2PA)
BDO Evidence: Yes (specification, schemas and OpenAPI; public with the v0.2.3 freeze)

BDO Evidence uses OpenTimestamps and qualified timestamps as components and validates what the client's own C2PA tools produce. It does not replace electronic signatures or the certification of communications: it covers the question they do not answer.

What it is not

It is not an AI detector or a watermark: it does not guess whether content is synthetic, it checks whether the content carries the declaration and whether that declaration is valid. It does not certify compliance and does not replace legal advice.

How it works

A real sequence, in four steps

01
Reproducible C2PA validation
We check where the file comes from.
The file and its manifest are validated with a pinned validator version under a frozen, versioned profile. The full context (trust lists, revocation, evaluation instant) is preserved in the Evidence Bundle. A negative result is evidence too.
02
Signed, canonical record
We leave a signed record of what was checked.
A signed Anchor Request Record is issued, binding content, manifest, bundle and creator identity through hashes or, in blinded mode, commitments that reveal nothing correlatable.
03
Dual anchor: Bitcoin and qualified timestamp
We anchor that record in two independent clocks.
The record's 32-byte commitment is timestamped with OpenTimestamps on Bitcoin and, optionally, with a qualified timestamp (QeTS) from an eIDAS provider. Two independent proofs over the same bytes.
04
Verification and export
Anyone can repeat the check.
A public URL returns a signed verification result. The deterministic export contains everything needed to repeat the verification at any time and anywhere; the open-source verifier ships with the first release.

Anchoring is asynchronous: confirmation arrives when Bitcoin includes the proof. We promise no deadlines, and we never present an inference as cryptographic proof.

The result

A per-dimension verdict, without overclaiming

Each dimension answers one concrete question and can only be valid, invalid, not_checked or not_applicable. A “false” never means both “invalid” and “there was nothing to check”. The absence of a declaration is never presented as proof of the opposite.

exact_match

Exact match

Is the file provided, byte for byte, the one on record?

content_integrity

Content integrity

Are the hard bindings between manifest and content still intact?

c2pa.signature · trust

C2PA signature and issuer trust

Does the signature verify, and is the certificate on the profile's trust list?

creator_assertion

Creator assertion

Is the credential valid, does it verify, and does it bind the author to this specific content? Assurance level derived by policy.

ai_generation_claim

AI declaration

Is there a signed AI-generation declaration? No declaration does not mean “not AI”.

existence.bitcoin

Existence in Bitcoin

Block and height of the attestation; pending until the proof is included.

existence.qets

Qualified timestamp

Validity of the eIDAS timestamp over the same commitment.

subject_signature

Record signature and authorisation chain

Was the signing key authorised, and is that authorisation verifiably earlier?

verification_mode

Reproduced context

Was the original context replayed, or was it evaluated against current policy? Both modes are legitimate, and the result states which one was used.

Reproducible means, to us, “same context, same verdict”.

For partners

For those already guiding clients on transparency and traceability

If your company helps organisations with transparency, provenance or digital content traceability obligations, BDO Evidence adds what an internal log cannot give: independent technical evidence your clients can present to third parties.

What you integrate

Open API; OpenAPI specification and schemas available to pilot partners, published with the v0.2.3 freeze
Signed verification result, embeddable in your reports
Public verification URL for every record
Deterministic export for audits; open-source verifier with the first release
Blinded mode for confidential documentation

What you don't have to operate

Bitcoin nodes or OpenTimestamps calendars
Signing keys, rotations or ceremonies
A contract with a qualified timestamp provider
C2PA validator, profiles or trust lists
Retention, privacy and withdrawal from publication

A complement to your compliance solution

If you help your clients with the AI literacy required by Article 4 of the EU AI Act, BDO Evidence covers the other half of the same Regulation: evidence that the content marking and provenance required by Article 50 were validated and existed on a specific date. You train and guide; we provide the proof. We neither replace your solution nor pass judgement on it.

Specification BDO-EVIDENCE-01 v0.2.3 at release candidate, with the schema and API layers closed; available to pilot partners and published with the freeze. Pilot programme open to partners.

What the end client receives

Record, result and evidence package

Minimal public record

Identifier, hashes or commitments, validation profile and proof status. Never full credentials.

Signed verification result

The nine dimensions with their states, the block height and the qualified timestamp, in a record a third party can verify again.

Evidence package

Deterministic export with records, .ots proofs, the qualified timestamp response, key history and validation bundle. The open-source verifier ships with the first release.

Privacy and withdrawal

Blinded mode, selective disclosure and withdrawal from publication. The anchored proof is immutable by nature, and that is stated before the record is made.

Ownership

A project owned by Supermultiverse LLC

BDO Evidence and the BDO-EVIDENCE-01 specification are owned by Supermultiverse LLC, the company behind the Bitcoin Digital Objects standards.

Contact: toni@supermultiverse.io

Pilot programme

Request a meeting or a pilot

Tell us what you need and we'll reply personally.