Skip to main content
waiTransport · Receipts and energy

Receipts for what was delivered, and what it cost.

waiTransport will sign a receipt for every object it delivers, chained per publisher key and track. A receipt will carry an energy figure only where the work was measured, with how it was measured signed beside it, and each figure will come with the report that says what it covered. Anyone can check WAI receipts with the open verifiers.

Roadmap Not yet operating. Each open component below is labelled with where it stands on the WAI status page.

The three labels

In the standard
The open component is in the main branch of the WAI open standard. Its link goes to its row on the dated WAI status page, and its notes are that row's.
Building
The open component is in active development, as the WAI status page lists it.
Roadmap
Planned: a WAI roadmap item, or a waiTransport service. Every waiTransport service is on the roadmap; none is operating yet.

Attested, in WAI, means signed by the party that did the work and measured it: a reader can check the signature, not re-measure the figure. It is not hardware attestation.

01 · The service

What waiTransport will sign, and how each figure will be assured.

  • Group receipts for every track waiTransport will deliver: a content hash per object, a Merkle root per group, and a signature linked to the previous receipt.
  • Energy measured on waiTransport's own encode, packaging and relay work, with hardware meters where the hardware has them. Every figure labelled with its acquisition class.
  • Energy assurance, figure by figure: each figure published with its measurement report (the meter, its acquisition class and what the figure covered), so a reader can check how it was obtained.
  • The stage claims and session claims that sinks sign, kept beside the delivery receipts they name.
  • A C2PA manifest for each reconstruction waiTransport will measure, binding its energy figure to that reconstruction.
02 · Builds on

Open components, each with its WAI label.

  • In the standard

    Group receipts: a content hash per object, a Merkle root per group, an Ed25519 publisher signature and a link to the previous receipt, chained per publisher key and track.

  • In the standard

    Typed receipt classes (delivery, energy, lawful-basis, log-inclusion, stage, delivery-gap and session), with an independent verifier and differential tests.

  • In the standard

    A relay cannot splice, replay or hold back a track's receipts unnoticed.

  • In the standard

    Energy acquisition classes, signed beside the figure: CalibratedInstrument, OnChipCounter, ModelBased or Estimator.

    Notes Unmetered work carries no figure and reads as not metered.

  • In the standard

    Energy meters: a hardware counter meter, or a calibrated instrument with its calibration reference, and a model meter that only ever yields a modelled figure.

    Notes A meter that cannot measure returns no figure; it never falls back to a fabricated one.

  • In the standard

    Measurement claims report on an energy figure without changing the receipt that seals it, and ratios are derived by every reader, never stated.

  • In the standard

    A power reader counts only while its rail advances: a rail that stops advancing is refused, and unmetered work is never a figure of zero joules.

  • In the standard

    C2PA manifest emission that binds an energy figure to the reconstruction it was measured over.

    Notes An optional build feature. The manifest validates; signer trust comes from the verifier's trust list.

  • In the standard

    Stage claims: a sink signs the stage it presented for each unit, the stage delivery reached and each refinement object's fate.

  • In the standard

    The signed session claim: what a sink presented when, what arrived and what was missed.

    Notes Timings, missed deadlines and switches remain the signer's statements, as do the facts of an encrypted envelope that only its payload shows. A sink that received a multi-rendition envelope only as byte ranges cannot yet state its classical length.

  • In the standard

    A key log at a web origin the signer names, so verifiers confirm receipts and claims offline.

03 · Being built

In active development in the standard.

  • Building

    Receipts served over HTTP, with a receipt index a client follows by hash to an object's group receipt, its stage claim and its chain.

04 · Roadmap

Planned, in the standard and in the service.

  • Roadmap· waiTransport

    Attested energy measurement on waiTransport's own hops, with a measurement report for every figure.

  • Roadmap· WAI

    Energy receipts for origins, hops and relays, and steering that reads them.

05 · Limits

What this page does not claim.

  • Energy figures cover the work measured. They do not cover displays.
  • A modelled figure is labelled as modelled and is never presented as measured.
  • Fleet and period totals, and energy and carbon reports across an organisation, belong to waiOS: Energy and carbon reporting.
  • No energy saving is stated on this site.
06 · Read next