-
-
Monthly Scope 1 emissions
Emissions by source
Findings from the auditor's review of v1
Historian import and verification
Exports go in exactly as the plant systems produce them. Every row is matched to a registered source and checked before anything changes; nothing is applied until you confirm.
Choose a file
What the import would do
Row by row
On-chain proof without publishing emissions
The chain records a salted commitment, not the total. Anyone can see that a report was filed and when; only parties holding the salt can check the figure against it.
1. The facility commits
2. What the public chain shows
Why salting? Try to guess the total
An attacker tries every whole tonne from 900,000 to 1,000,000 (100,001 guesses), hashing each one the way the contract would.
Hashing a plain number on a public chain doesn't hide it: the range of plausible totals is small enough to try them all. A 32-byte secret salt makes guessing infeasible, so only the facility, its accredited auditor and NREB, who hold the salt, can check the total against the chain.
3. NREB verifies
A match proves the figure is exactly the one committed at filing and unchanged since. Whether it is right is still established by the accredited auditor's verification.
NREB filing package and audit log
The report, its evidence fingerprints and the commitment, assembled in one package. Every action is written to a hash-chained log, so any later edit shows.