Resources

CTU metering test vectors

Run your meter against these cases.

Approved by the Board for implementation · 20 November 2026

DraftVersion 0.2.0Drafted 12 November 2026Owner: Systems Engineering (role being recruited; interim owner to be named, Q4)Licence: [to be confirmed]Side of the line: published

A draft (0.x): read it, build to it and comment on it; it may change without notice. Drawn from the CTU book and the Sovereign Stack page. Changelog · Comment on this specification

In short

Run your meter against these cases. A meter conforms at a level when it gives the expected result for every vector at that level. All values are examples. No meter has been tested against them yet; when one has, the changelog will say so.

#LevelCaseExpectedFields checked
V11A passing cycle on one deviceOne record; all fields presentOutcome, Energy
V21A cycle rejected at the gateOne record; outcome reject; energy countedOutcome, Energy
V31A cycle that fails before the gateOne record; outcome failed; energy countedOutcome, Energy
V42Two cycles sharing a nodeTwo records; allocations sum to the node meterAllocation rule, Energy
V52Missing meter readings for part of a cycleRecord marked unverified; no silent estimateEnergy
V62A correction for a calibration errorA new record pointing back; the original unchangedCorrects
V71No CTU definition yetConversion: none; CTU empty; raw values presentConversion, CTU, Energy, Compute
V81A record with a personal name in itRejectedDeployment

From data. All values are examples. No meter has been tested against these vectors yet.

Levels

LevelA meter at this levelNeeded for
1 RecordEmits one complete record per cycle, with every required field and unit, including failed cyclesTestnet cycles
2 VerifiedLevel 1, plus signed records that pass the five checks, with T1 measuredPartner reports
3 FacilityLevel 2, plus T2 metered rather than estimated, and raw logs kept for auditBenefit-report figures

Back to the CTU metering method

Owner: Systems EngineeringNext review: 2027-05-11