Primitives

Six contracts that cover every meter we have seen

Written once on Canton, reused per agreement. Adding a customer means a new MeterAgreement, not a new integration.

MeterAgreement

What gets counted and at what price

Holds the unit definition, the reading cadence, the price schedule and the parties. Changing it needs both signatures.

ReadingBatch

Signed usage, in sequence

A numbered batch of readings with the submitter's signature. Missing sequence numbers surface as gaps, not silence.

SettlementWindow

The period that closes

Totals the batches, applies the price schedule and produces one amount. Windows can be hourly, daily or monthly.

DisputeTicket

The disagreement, on the record

Either party can challenge a window before it settles. The ticket names the readings in question and pauses only that part.

PayoutSplit

Who gets which slice

Splits one settlement across resellers, partners or infrastructure providers by rules agreed up front.

MeterVault

The funds behind the meter

Holds the collateral or prefunded balance a window draws from, so settlement does not depend on a bank transfer clearing.

Out of scope

What Orbitmeter leaves alone

Readings come from your gateway, your substation, your terminal. We take them signed.

The schedule is yours. We apply it and show the arithmetic.

A vault is optional and holds only what a window can draw.

We will model it as a meter, replay the usage, and show what both sides would have signed at the time.