You distribute the revenue from your tokenized energy assets. Today, your holders take your word for it — or a quarterly PDF. With YIELD, a Box seals production at the source every 15 minutes and anchors it on public ledgers. The token payout rests on a journal whose prior existence is anchored every hour — impossible to rewrite without breaking a public anchor.
The income of a token backed by a production rests on your statement. Without independent proof, it's a promise, not an asset.
A quarterly PDF report describes the past, signed by you. Between two attestations, anything can move — and be rewritten.
Oracles (Chainlink PoR…) query a custodian's API. On a physical production site, there is no trusted API to query.
On-site device, connected to the production meter or the inverter output, read-only.
Chained SHA-256 hash, every 15 minutes, Ed25519 signature. No secret key: recomputable by any third party.
The head fingerprint is published every hour on Hedera HCS and Base (daily in the Journal tier). History cannot be rewritten beyond the anchoring interval.
A public link per site: anyone recomputes the chain and checks the anchor, with no 0DATA account.
What YIELD proves: the integrity and prior existence of the production journal — a technical element of proof, verifiable by a third party. What YIELD does not claim: that the sensor told the truth at the source (a faulty sensor produces an intact journal of erroneous data). The Settlement tier cross-checks several sources to detect these anomalies.
Outbound API push from your existing SCADA/inverter. 1 stream, hourly sealing, daily anchoring. Public verification link. Integrity of the existing stream — proof at the source (Box) comes with the Sealed tier.
Box installed on site, encrypted one-way push, 15-min sealing, dashboard, verifiable monthly report, up to 5 measurement points.
All of Sealed, + multi-source cross-checking (Box + SCADA export + grid/weather data), anomaly detection, oracle-ready endpoint (Chainlink Functions), detailed monthly report (attested production, discrepancies, consistency index).
Pricing aligned with our Proof plans (1 490 € and 3 000 €/month) — same level of sealing and anchoring, production scope. First Box included at setup; additional Boxes provided (on quote), with a decreasing price from 30 sites. 24-month commitment on Sealed and Settlement — that's what builds your sealed history, and it can't be bought retroactively.
| Deliverable | Form | Tier |
|---|---|---|
| Installed Box | DIN rail in the electrical cabinet, read-only, outbound 4G/Ethernet. Installed in half a day. | Sealed, Settlement |
| Sealed journal | Timestamped JSONL, one record every 15 min: timestamp, value, chained hash, Ed25519 signature. | All |
| Anchoring proof | Hedera HCS + Base transaction — hourly (Sealed, Settlement) or daily (Journal), verifiable on a public explorer. | All |
| Public verification link | Per-site URL to give your holders — chain recomputation, no 0DATA account. | All |
| Dashboard | Production, Box status, chain continuity, alerts. | Sealed, Settlement |
| Verifiable monthly report | 4-page PDF + signed JSON: production, availability, incidents, detected discrepancies. | Sealed, Settlement |
| Settlement stream | Signed HTTPS endpoint, OpenAPI spec, Chainlink Functions compatible. Latency < 1 h. | Settlement |
| Deployment attestation | Document recording the installation, the identifier and the public key of the Box. The root of trust. | Sealed, Settlement |
| Week | 0DATA does | You provide |
|---|---|---|
| S0 — Signature | Contract + site technical sheet. Setup payment. | Signed contract, site sheet, CISO approval (1-page diagram provided). |
| S1 — Preparation | Box configuration, shipping. Ed25519 key generation at installation (S2). Journal tier: API stream from S1. | Site access window, local electrician if connection is needed. |
| S2 — Installation | Installation, read-only connection, push test, first signature. | Presence of the technical lead. |
| S3 — Alignment | Box vs SCADA history comparison, alert calibration. Settlement: stream test to your staging. | Production history export, smart contract staging access. |
| S4 — Live | Continuous journal, first anchor, deployment attestation, 45-min training. | — |
By day 35, you show your holders a verification link that works. That's what you're buying — not software.
— Collection and anchoring: 99 %/month
— 15-min sealing; any gap > 1 h detected, alerted < 1 h, and reported (never hidden)
— HCS + Base anchoring ≤ 24 h
— Box failure: replacement within 10 business days
— Journal exportable in full at any time, at no cost, even at contract end
— Penalties: 5 % discount per missed point, capped at 30 %
— Measurement truthfulness: we prove the integrity and prior existence of the journal, not that the sensor told the truth
— No eIDAS evidential value, no equivalence to a financial audit
— Production, energy price, token performance
— Continuity in case of site destruction or prolonged outage (the gap is recorded and proven, not filled)
No. YIELD produces the continuous technical element of proof; your auditor builds on it instead of starting from scratch.
The sealed journal faithfully certifies false data — that's the limit of any oracle. The Settlement tier cross-checks several sources to detect these anomalies.
The journal and the anchors belong to you and remain independently verifiable via the open-source verifier and public ledgers, as long as they remain accessible.
Chainlink carries data on-chain by querying an API. On a physical site, there is no trusted API. YIELD produces proof of origin — and can feed Chainlink Functions.
One site, 30 days, 0 €, zero installation. The sealed journal starts accumulating from day one — and history can't be bought retroactively. Every month of waiting is a month of proof lost.