Energy Types
EnergyAS maintains an on-chain registry of energy source types. These are used to classify generator project attestations.
Registered Types
The following energy types are pre-registered at deployment:
| ID | Name | Description |
|---|---|---|
| 0 | consumer | Reserved — consumption project (no generation source) |
| 1 | solar_pv | Photovoltaic solar |
| 2 | wind_onshore | Land-based wind turbines |
| 3 | wind_offshore | Offshore wind turbines |
| 4 | hydro | Hydroelectric (run-of-river or reservoir) |
| 5 | biomass | Biomass combustion or biogas |
| 6 | geothermal | Geothermal heat or steam |
| 7 | ocean_tidal | Tidal or wave energy |
| 8 | nuclear | Nuclear fission |
| 9 | natural_gas | Natural gas combustion |
| 10 | coal | Coal combustion |
| 11 | oil | Oil/diesel combustion |
| 12 | storage_discharge | Battery or other storage system discharge |
| 13 | hydrogen_fuel_cell | Hydrogen fuel cell |
Usage Rules
Energy types are set once at project registration and are immutable. The energyType parameter passed to registerProject() determines the project's classification: 0 for consumers, 1–13+ for specific generation sources. The registry validates that the given energy type is registered before accepting the project.
Energy types are not part of the attestation schema and are not validated during attestation. The registry reads the project's energy type internally to route energy totals to the correct accumulators (generated vs consumed) and to emit it in events for indexers.
New energy types (e.g., fusion, next-generation renewables) can be added on-chain by the Energy Type Admin without redeploying contracts or changing the schema.
Energy Type Admin
The energy type registry is managed by a separate admin role (distinct from the contract owner). This allows delegating type management without granting full contract control.
The admin can register new types, remove existing ones, and transfer the admin role to another address.