NRR & NCTR
- For
- Renewable generators on one side, emitting companies on the other
- Live at
-
recs.thinkn.cloud
tax.thinkn.cloud - Shape
- Two registries, one backend, one database
- Unit
- MWh issued, tCO₂ owed
Two registries that only make sense as a pair. The National Recs Registry is where renewable electricity becomes a tradeable certificate. The National Carbon Tax Registry is where a company's emissions become a bill. The first creates the supply that settles the second.
They are separately branded and separately logged into, but they run on a single backend over a single database. Every account is stamped with the side it belongs to, and every route checks that stamp, so the two registries share a marketplace without sharing each other's books.
Registering
A generator registers a project, solar, wind, hydro, biomass or geothermal, through a four-step intake: the project itself, its documents, the data connectors that will report its output, then review and submission. Submitted projects go to the registry for approval before anything can be issued.
Issuing
An approved project issues vintages: a quantity of MWh for a period, priced per MWh, listed on the marketplace with whatever remains available.
Reporting
On the compliance side, a company reports emissions in tonnes of CO₂ by month and by source. Its annual quota is derived from rules for its industry, a base allowance per employee, an intensity factor, and the penalty rate per tonne over.
Forecasting
Reported months are annualised into a projected year-end figure and marked against the quota as on track, warning or critical, with best and worst case scenarios beside the current trend, so the size of the gap is known before the year closes rather than after.
Settling
Buying is a two-step commit. The purchase reserves against an available vintage
and opens a pending transaction, and confirming it decrements the vintage and
mints a certificate with its own serial in REC-XXXXXXXXXXXX form.
Confirming twice does not mint twice.
Retiring
A certificate held against a compliance obligation is retired, which is the point of the whole exercise: it is spent, recorded as spent, and cannot be sold on to anybody else.
Live SCADA and REST ingestion from project connectors, document upload, in-app notifications, and on-chain settlement. The data model and the screens for these exist; the feeds behind them are not connected yet.