Use case
Energy certificate register
A unit that claims to track a megawatt-hour or a certificate. The meter, the registry rules, and the legal scheme come first.
An issuer wants certificates that cannot be double-counted, with a buyer who can see retirement.
When shared machinery earns a place
Double-counting across organisations is the actual defect a shared register can address.
When it does not
A spreadsheet inside one utility, or a token that does not map to the official registry rules.
Conventional-first
Integration to that registry. Do not create a shadow instrument.
You depend on the registry's API and rules.
Hybrid
Issuance against meter evidence, transfer limits, retirement as a terminal state, public commitment of retired serials.
Oracle or meter trust is the whole system.
On-chain-native
Restricted token, retirement, no second market you did not design.
A parallel unofficial token is a misrepresentation risk.
Patterns
Components
- OpenZeppelin ContractsGreen — compatible use if you keep the notices
- Chainlink EVM contractsAmber — conditions, and a legal review before you copy it in
- PonderGreen — compatible use if you keep the notices
- viemGreen — compatible use if you keep the notices
Read before you build
Questions a person still has to answer
- Which official scheme is this, if any?
- What prevents two tokens for one megawatt-hour?
- Who may retire?