MATCHING AND EVIDENCE
How an ElecTrace result is calculated and checked.
The method keeps physical meter data, contractual allocation and cryptographic evidence as separate layers. That distinction makes the result easier to reproduce and prevents a hash from being mistaken for proof that the original reading was true.
Match the same interval
Rooftop generation and every participating load are aligned to the same UTC interval. In each interval, on-site consumption is the smaller of total generation and total demand. Any remaining generation is export; any remaining demand is supplied by the grid. Internally, energy is represented as integer Wh so each interval can be checked for conservation.
Apply one stated allocation rule
Where several occupants share a rooftop system, the available on-site electricity is assigned under one visible rule. The demonstration supports allocation in proportion to contemporaneous demand, a stated priority order, or contract weights. No participant can receive more rooftop electricity than its demand in that interval, and the same Wh cannot be allocated twice.
Package inputs, results and provenance
The EvidencePackage records the scenario, interval results, matching rule and version, source metadata, totals, manifest and proofs. Source records distinguish historical operational data, models, scaling and user input. A result should not be labelled as metered merely because it follows the same schema as a meter export.
Recalculate hashes and inclusion proofs
Canonical JSON gives the same byte representation to the same structured input. SHA-256 identifies that representation, while a Merkle root binds the complete interval set. An inclusion proof checks that a specified interval belongs to the set represented by that root. The independent verifier reruns the allocation and recalculates these values; it does not trust a saved “valid” flag from the interface.