How it works
A window opens, readings arrive, the amount settles
Nothing here happens at month end. The cycle repeats on whatever cadence the agreement sets, which is why disagreements surface while the logs are still warm.
The cycle
Three moves, repeated every window
- 01
Agree the meter
Both parties sign what is counted, how often it is read and what a unit costs. The meter definition is the contract, not an appendix to it.
- 02
Submit readings
Readings arrive from either side on a fixed cadence. Each one is signed and sequenced, so a gap is visible immediately rather than at month end.
- 03
Close the window
At the end of each window the readings are totalled, the dispute period opens, and anything unchallenged settles on Canton.
One hourly window
What an hour actually looks like
- 00:00Window opensCounters reset, the price schedule for this window is fixed
- 00:15Batch b-4417 submittedProvider reading, signed and sequenced
- 00:15Batch b-4418 submittedCustomer reading, 9 units apart, inside tolerance
- 01:00Window closesTotals computed, amount produced, dispute period starts
- 03:00Dispute period endsNothing challenged, settlement executes on Canton
Specs
The numbers behind a meter
- Window lengths
- Hourly, daily, monthly
- Reading submission
- Either party, signed and sequenced
- Dispute period
- Configurable, default 48 hours
- Settlement asset
- Any Canton-issued token
- Splits
- Up to 20 recipients per window
- Retention
- Readings kept for the life of the agreement
Bring one invoice your customer disputed.
We will model it as a meter, replay the usage, and show what both sides would have signed at the time.