The verified-delivery settlement rail for compute
RAW is composed of three layers: an edge attestation device, a Daml contract framework on Canton Network, and a non-custodial settlement engine. Together they turn a delivery claim into a verified, atomically-settled transaction.
Three components. One invariant.
Every element subordinates to the integrity of the delivery record.
RAW Box — edge attestation hardware
A hardware-secured device deploys at the producer's site, capturing delivery telemetry at the closest possible point to the source. On compatible hardware, readings are additionally signed inside a Trusted Execution Environment (TEE) before any party can alter them. Keys never leave the device.
Asset DNA — on-ledger contract framework
Daml templates on Canton Network encode the delivery contract: terms, SLA, and price. Asset DNA maintains an append-only lifecycle record per physical asset — identity, attestation history, and every verified delivery proof, comparable to a vessel's classification record.
Settlement engine — atomic, non-custodial
An independent assurance layer verifies usage records, then payment moves directly from buyer to producer in regulated stablecoins. RAW never holds customer funds. Under-delivery automatically reduces the payout.
How the RAW Box prevents spoofed telemetry
Signed before it can be altered
Compute execution and inference results are signed where they are produced — before they ever reach a contract. Hardware-backed attestation on compatible platforms proves the integrity of the execution environment, while independent cross-verification ensures every result is verifiable.
Multiple independent measurements
Provider-side telemetry is matched against consumer-side telemetry.
24 hours before finality
A dispute window precedes settlement becoming final, giving counterparties time to flag anomalies before funds move.
| Dimension | GPU / telemetry monitoring software | RAW Box |
|---|---|---|
| Purpose | Operator's own visibility | Contract-grade evidence for a counterparty |
| When data is captured | Polled and aggregated after the fact | Signed at the point of capture |
| Editable after capture | Yes — exportable and editable | No — the signature breaks if altered |
| Tied to payment | No | Yes — drives settlement directly |
Built on Canton Network
Four properties of Canton are load-bearing for RAW. Institutional counterparties evaluating alternatives typically have to combine several separate providers to get all four; Canton Network provides them in one environment.
Counterparties see only their own contracts. Privacy is a native property of the ledger, not an overlay.
Delivery validation, fund transfer, fee deduction, and cash leg complete in one all-or-nothing transaction.
Contracts are written in Daml and settle in native USDC under Canton's CIP-56 token standard. RAW doesn't operate Canton Network — it settles on top of it.
Integration checklist
What a producer needs in place before the first verified record can settle. Most facilities already satisfy items 01 through 03.
A readable delivery signal
The RAW Box draws on data already available from your existing systems:
- Inference serving layer metrics endpoint (throughput, TTFT, token counts)
- GPU management stack (per-device utilization, device class, configuration)
- Existing metering or SCADA for energy-side assets
Power, rack space, outbound connectivity
The device needs a rack slot alongside existing infrastructure and outbound network access to publish signed batches. No inbound access into your network is required, and no facility downtime is needed to install it.
A defined asset to attest
Each attested asset is registered with its identity, device class, and configuration. This is what Asset DNA records against, and what heterogeneity is priced from at contract formation.
Canton party and settlement wallet
A Canton Network party identity and a wallet to receive regulated stablecoin settlement. Payment moves directly from buyer to producer — RAW never holds customer funds, so no custody arrangement is involved.