Status · as of 2026-10-09

Where waiTransport stands

waiTransport is not yet operating. This page lists every part of the service, labelled Roadmap, and the open WAI components each part builds on, with the label and notes the WAI status page gives them. Open-component labels are as of the WAI status page dated 2026-10-09.

Operating now: none. Roadmap: every service below.

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.

Managed delivery

Will package WAI content and carry it over the carriers a sink already uses. Relays will forward each object and its receipt byte for byte. The managed delivery page

Managed delivery: each part, its status label, its notes and where it is described
Part	Status	Notes	Where
A packaging policy, read with every refusal named and digested over its canonical form, so two spellings of one policy have one digest.	In the standard	—	On the WAI status page Packaging extension
Pieces cut at scene changes by a streaming segmenter that looks ahead, so a flash or a cut back does not start a piece.	In the standard	—	On the WAI status page
An integer video encoder that writes the pinned video payload, with the step for each piece chosen under the policy's distortion bound.	In the standard	—	On the WAI status page
Packages: a stage index and a signed package receipt bound to the policy it was packed under, a floor checked against its keyframe plan, and HLS, DASH and Media over QUIC views of one package.	In the standard	Packages carry a base and its floor; refinement layers in packages, rule ladders and other media come next.	On the WAI status page
Staged delivery: a base first and refinements as separate objects, each linked to its base by hash, with a stated determinism tier per stage. A missing or refused refinement leaves the base intact.	In the standard	—	On the WAI status page Staged delivery demonstration
A sink bounds the work and memory of every base and every layer, and refuses past each bound before decoding.	In the standard	—	On the WAI status page
The Media over QUIC streaming format, with one whole single-payload envelope per object and an optional per-object receipt property.	In the standard	Tracks IETF Internet-Drafts. Each object is one whole single-payload envelope. An energy claim carries an object's class under a signature.	On the WAI status page MoQ streaming format extension
Refinement layers over Media over QUIC: each layer its own track with its own receipts track, so a subscriber caps layers and receipts together.	In the standard	The binding follows the Media over QUIC Internet-Drafts it names, which may still change.	On the WAI status page
WAI objects over HTTP, named by their content hash and immutable.	In the standard	—	On the WAI status page HTTP delivery extension
A head a client checks against the content hash before it fetches the rest.	In the standard	—	On the WAI status page
Byte-range fetch of one rendition from a multi-rendition envelope, checked by its digest, with the whole object as the fallback.	In the standard	—	On the WAI status page
Cache rules, with a public driver that checks a cache against them.	In the standard	—	On the WAI status page
Playlists sealed in a receipt and verified strictly, revision by revision.	In the standard	—	On the WAI status page
Unidirectional delivery.	In the standard	Specification text; no bearer binding.	On the WAI status page Unidirectional delivery extension
Relay preservation: envelopes and receipts forwarded byte for byte, with no transcoding, rewriting or re-signing.	In the standard	A relay attests in a separate, parallel receipt.	On the WAI status page
A transform recorded as its own signed lineage step.	In the standard	—	On the WAI status page
A package played in the browser: every object checked against the stage index, and every rebuilt frame checked against the native reference.	In the standard	One open-film excerpt at 256 × 128. Bytes, quality and decode time are measured in the tab; no saving is stated.	On the WAI status page Cargo, measured
Staged delivery on the measured excerpt: a base first and refinement layers after, every level checked by hash.	Building	—	On the WAI status page
Receipts, key statuses, grants and parameter sets served over HTTP and checked on every fetch path.	Building	—	On the WAI status page
Hosted packaging and delivery from Transaction Science.	Roadmap· waiTransport	—	The managed delivery page
Bearer bindings for broadcast, satellite and multicast.	Roadmap· waiTransport	—	The managed delivery page
Live tracks over Media over QUIC end to end, with live packaging.	Roadmap· WAI	—	On the WAI status page
An edge that evaluates derived tracks and rebuilds or re-packs content under its own receipt.	Roadmap· WAI	—	On the WAI status page
Synthetic pieces packed as instructions the sink evaluates.	Roadmap· WAI	—	On the WAI status page
Energy receipts for origins, hops and relays, and steering that reads them.	Roadmap· WAI	—	On the WAI status page

Receipts and energy

Will sign receipts for what was delivered, presented and decoded. A receipt will carry an energy figure only where the work was measured, always with how it was measured. The receipts and energy page

Receipts and energy: each part, its status label, its notes and where it is described
Part	Status	Notes	Where
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	—	On the WAI status page Receipt chain extension
Typed receipt classes (delivery, energy, lawful-basis, log-inclusion, stage, delivery-gap and session), with an independent verifier and differential tests.	In the standard	—	On the WAI status page
A relay cannot splice, replay or hold back a track's receipts unnoticed.	In the standard	—	On the WAI status page
Energy acquisition classes, signed beside the figure: CalibratedInstrument, OnChipCounter, ModelBased or Estimator.	In the standard	Unmetered work carries no figure and reads as not metered.	On the WAI status page Energy measurement extension
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.	In the standard	A meter that cannot measure returns no figure; it never falls back to a fabricated one.	On the WAI status page
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	—	On the WAI status page
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	—	On the WAI status page
C2PA manifest emission that binds an energy figure to the reconstruction it was measured over.	In the standard	An optional build feature. The manifest validates; signer trust comes from the verifier's trust list.	On the WAI status page Energy binding extension
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	—	On the WAI status page
The signed session claim: what a sink presented when, what arrived and what was missed.	In the standard	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.	On the WAI status page Staged measurement demonstration
A key log at a web origin the signer names, so verifiers confirm receipts and claims offline.	In the standard	—	On the WAI status page
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.	Building	—	On the WAI status page
Attested energy measurement on waiTransport's own hops, with a measurement report for every figure.	Roadmap· waiTransport	—	The receipts and energy page
Energy receipts for origins, hops and relays, and steering that reads them.	Roadmap· WAI	—	On the WAI status page

Decoder registries

Will host the decoder modules and parameter sets WAI content needs, each addressed, authorised and revoked by digest, for the sink to check before it decodes. The decoder registries page

Decoder registries: each part, its status label, its notes and where it is described
Part	Status	Notes	Where
The normative parameter-set pin: one SHA-256 over a whole parameter set. A sink verifies the pin before it decodes, and decodes only from the bytes it verified.	In the standard	A pin that does not resolve makes its capability unsupported for that envelope: dispatch continues at the fallback, and selection at the next rendition.	On the WAI status page
Decoder and reconstruct modules, and pinned parameter sets, authorised by digest and revoked by digest. A sink that holds a key log refuses a revoked parameter set, and its dispatch falls back.	In the standard	A runtime host that loads signed modules is on the roadmap.	On the WAI status page
A key log at a web origin the signer names: revisions under a root key that pre-commits to its successor, each key's authorities and its status, confirmed offline.	In the standard	—	On the WAI status page
One rule for every Ed25519 signature WAI defines, applied by the reference verifier and an independent one.	In the standard	OER/2 keeps the signature rule its own extension settles. The quantum toolkit's receipts are verified by its own verifier, which does not yet apply this rule.	On the WAI status page
The model a neural payload needs is named, pinned by digest and never carried in the envelope; a pinned prior can declare its artifact's wire form, and the NNC bitstream is registered as one.	In the standard	A replicate whose prior declares a wire form the sink cannot read is refused.	On the WAI status page Prior carriage extension
The WAI capability registry: every registered string in one table, with a machine-readable export generated from it and checked for drift in CI.	In the standard	—	On the WAI status page
Parameter sets, key statuses and grants served over HTTP and checked on every fetch path.	Building	—	On the WAI status page
Hosted, curated decoder and parameter-set registries from Transaction Science.	Roadmap· waiTransport	—	The decoder registries page
A host that runs signed, revocable modules.	Roadmap· WAI	—	On the WAI status page

Content protection

Will run a protected-path lane for premium content, with receipts for the envelope and every key decision, and an end-to-end lane in which the sink, once it decrypts, can issue every receipt class. Both lanes wait on player integration, on the WAI roadmap. The content protection page

Content protection: each part, its status label, its notes and where it is described
Part	Status	Notes	Where
Player integration: runtime fallback, two DRM lanes and a continuity harness.	Roadmap· WAI	—	On the WAI status page
A key-release service that signs a record of every release and every refusal.	Roadmap· waiTransport	—	The content protection page
Key-release decision records: every release and every refusal is a signed receipt.	In the standard	Records decisions; speaks no licence protocol.	On the WAI status page
Session-class manifest: an HLS media playlist generated once per session class.	In the standard	The signer declares the viewer count behind any per-viewer figure.	On the WAI status page
Relays that forward envelopes and receipts byte for byte.	In the standard	A relay attests in a separate, parallel receipt.	On the WAI status page
Managed group keys for the end-to-end lane.	Roadmap· waiTransport	—	The content protection page
Encrypted payloads and private channels (MLS and SFrame).	In the standard	Specification text in the open-standards repository. Its implementation is a companion implementation outside it, under its own licence, and the demonstration runs on it. The MLS binding follows an individual Internet-Draft that has expired.	On the WAI status page Confidentiality extension Private channel demonstration
The signed session claim.	In the standard	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.	On the WAI status page

Ad insertion

Will decide ads once per session class and record every impression in a signed receipt. A verifier recomputes the spend and refuses a record past its ceiling. The ad insertion page

Ad insertion: each part, its status label, its notes and where it is described
Part	Status	Notes	Where
Session-class manifest: an HLS media playlist generated once per session class.	In the standard	The signer declares the viewer count behind any per-viewer figure.	On the WAI status page Delivery workflow demonstration
Ad-insertion decisions with per-impression receipts.	In the standard	A verifier rejects a record whose spend exceeds the grant's funds ceiling.	On the WAI status page
Packaging on group-of-pictures boundaries into content-hashed segments.	In the standard	The caller supplies the slices. A verifier recomputes the deduplication totals from the signed entries.	On the WAI status page
Virtual linear channel: signed playback windows chained into a record of what aired.	In the standard	—	On the WAI status page
Managed ad decisions and stitching.	Roadmap· waiTransport	—	The ad insertion page
Player integration: runtime fallback and a continuity harness.	Roadmap· WAI	—	On the WAI status page

Runtimes

Will run WAI capabilities on GPU and NPU backends beside the open reference runtime, within what each capability's determinism tier allows. Speed is an aim until it is measured. The runtimes page

Runtimes: each part, its status label, its notes and where it is described
Part	Status	Notes	Where
Determinism tiers, entropy-consistency and decode-equivalence, typed in code. A replicate means exactly what its tier guarantees.	In the standard	—	On the WAI status page Determinism tiers extension
Fast integer decode kernels that give the same integer for every output.	In the standard	Timed on one machine. WebAssembly runs the same kernels single-threaded, untimed.	On the WAI status page
Native and browser builds produce the same output for the integer-exact capabilities.	In the standard	Checked in the page, per frame, with a 64-bit FNV-1a hash; receipts use BLAKE3.	On the WAI status page
A payload's exact output size, working memory and compute, read from its header before decoding.	In the standard	The header bounds the work; a small payload may describe a large output, and a sink applies its own size policy before decoding.	On the WAI status page
Byte equality of the integer decode paths, checked in CI on each platform the WAI status page lists.	In the standard	—	On the WAI status page
Energy meters that yield a hardware class only when they read hardware.	In the standard	A meter that cannot measure returns no figure; it never falls back to a fabricated one.	On the WAI status page
GPU and NPU backends.	Roadmap· waiTransport	—	The runtimes page
Naming the device and the arithmetic in a receipt. The session claim names the decoder (a built-in decoder and its version, or a module by digest), the decode path within it and the pinned parameter set's tier; it has no device or precision field. Adding one is new work that is neither in the standard nor on the WAI roadmap.	Roadmap· waiTransport	—	The runtimes page
A host that runs signed, revocable modules.	Roadmap· WAI	—	On the WAI status page

Developer tools

Will offer hosted conformance runs, packaging previews and receipt inspection, built on the open command-line tools and verifiers. The developer tools page

Developer tools: each part, its status label, its notes and where it is described
Part	Status	Notes	Where
The wai command-line tool lists the capability registry and writes its machine-readable export, which CI checks through it.	In the standard	—	On the WAI status page
A command-line tool for staged delivery, with the residual refinement payload and a corpus with an independent verifier.	In the standard	—	On the WAI status page
Encoders.	In the standard	Classical encoding in the command-line tool. The learned and integer encoders are offline tools.	On the WAI status page
A package verifier that refuses, never panics.	In the standard	—	On the WAI status page
Conformance corpora, run in CI.	In the standard	—	On the WAI status page
Measurement and the session claim in the browser, giving the native tool's figures byte for byte.	In the standard	—	On the WAI status page Staged measurement demonstration
A C interface over the reference implementation (libwai).	In the standard	Built by the ffi feature, which a default build turns on. Without the codec libraries, CI builds it with --no-default-features --features ffi and runs its envelope tests.	On the WAI status page
Hosted conformance runs, packaging previews, a receipt inspector and embedding libraries.	Roadmap· waiTransport	—	The developer tools page

The standard has its own status page.

Every open component above links to its row on the WAI status page, which is dated and covers the standard only.

The WAI status page Ask about early access