0DATA
The category

The sealed & anchored proof.

A digital proof that combines three links: continuous measurement at the source, built-in qualified eIDAS timestamping, and anchoring on a public ledger. Verifiable by a third party. 0DATA implements it end to end.

Definition in one sentence

The sealed & anchored proof is a digital proof that combines (1) continuous measurement captured at the source and (2) cryptographic anchoring on a public distributed ledger (Hedera), reinforced by (3) qualified eIDAS timestamping (RFC 3161). Result: integrity and anteriority verifiable by a third party, without relying on the publisher's word.

The three links

Three links. Two core, one reinforcing.

Measurement at the source and public anchoring are enough to make the data verifiable. Qualified eIDAS timestamping adds regulatory probative value (art. 41 eIDAS).

1 · Continuous measurement
Capture at the source

Data is captured passively at the source (sensor, box, API), at a 15-minute cadence. The verdict is computed over a rolling 24 hours — a one-off spike is not enough to change the verdict over a rolling 24 hours.

2 · eIDAS timestamping
RFC 3161 · Qualified timestamping

Each measurement can be timestamped by an eIDAS-qualified TSA — built in. It is not an internal timestamp: it is a stamp that benefits from a presumption of accuracy of the date and time and of data integrity (art. 41 eIDAS).

3 · Public anchoring
Hedera · Public anchoring

The SHA-256 fingerprint is published on a public distributed ledger (Hedera Consensus Service). Integrity is verified independently of the publisher, by anyone, without an account.

Why this category exists

Declaring is not proving.

The compliance market has been built on three families, each incomplete.

GRC / declaration tools

GRC · documentation · checklist

Market GRC tools produce compliance documentation: registers, checklists, reports. They declare conformity at a point in time, but nothing is sealed, qualified-timestamped, or anchored. The document remains editable by its author.

Timestamping providers

TSP · eIDAS · RFC 3161

Qualified timestamping providers deliver a qualified timestamp or a signature. It is an essential link, but isolated: they timestamp without measuring or anchoring. Anteriority is proven, but not the continuous integrity of the data.

Blockchain notarizers

Blockchain anchoring · notarization

Blockchain notarizers publish a fingerprint on a blockchain. Integrity is verifiable, but without qualified eIDAS timestamping, and without continuous measurement at the source. Anchoring alone proves integrity, but not anteriority with regulatory presumption.

The sealed & anchored proof brings the three links together. This is the difference between "saying" and "showing". To our knowledge, none of the three families can claim it alone today — that is precisely the space 0DATA occupies.
18 verticals

The same engine, applied to every sector.

Each vertical seals and anchors its sector's data: CIR, DORA, CEE, AI Act, CBAM, EUDR, MRV, ESG, methane, capacity, DPE, MiCA, parametric insurance, cold chain, audience, SLA, cyber, Field-Scan.

CIR Proof
R&D work traceability DORA Proof
ICT provider resilience CEE Proof
Energy savings works AI Act Proof
AI systems compliance CBAM Proof
Imported emissions EUDR Proof
Anti-deforestation due diligence MRV Carbon Proof
GHG measurement & verification ESG Proof
Measured physical indicators Methane Proof
Methane emissions Capacity Proof
Energy curtailment DPE Proof
Actual consumption vs DPE MiCA Proof
Proof of reserves (CASP) Parametric Proof
Parametric insurance oracle ColdChain Proof
Pharma cold chain Audience Proof
Influencer performance SLA Proof
Service level Cyber Proof
Measured cyber risk Field-Scan
Sealed field audit Generic Proof
Sealing & anchoring · 0,20 €/seal
Frequently asked questions

What the category answers.

What is a sealed and anchored proof?
A digital proof that combines three links: continuous measurement captured at the source and cryptographic anchoring on a public ledger (Hedera), reinforced by qualified eIDAS timestamping (RFC 3161). Integrity and anteriority are verifiable by a third party, without depending on the publisher.
What is the difference between a proof and a declaration of conformity?
A declaration asserts conformity at a point in time (documentation, checklist, report). A sealed and anchored proof demonstrates it continuously: each measurement is sealed and anchored, and can be eIDAS-timestamped as reinforcement. Any later alteration is detectable and verifiable by a third party.
Why does eIDAS timestamping strengthen the proof?
An internal timestamp (database) is editable by the publisher. eIDAS timestamping (RFC 3161 via a qualified TSA) is a stamp delivered by a regulated trusted third party, which benefits from a presumption of accuracy of the date and time and of data integrity (art. 41 eIDAS).
Why anchor on a public ledger?
Because integrity must not depend on the publisher. A fingerprint anchored on Hedera is verifiable by anyone, without an account, by recomputing the hash. The publisher can neither modify nor delete the history.
How much does a sealing cost?
0,20 € per sealing, no subscription, no quota. Qualified eIDAS timestamping is included.
Is the proof verifiable by a third party?
Yes. Any third party holding the fingerprint can recompute the hash and verify the integrity of the history, without an account or access to 0DATA infrastructure.