Choose the role that describes your capacity.
Your role determines what operations you may initiate in the federation — which primitives you can invoke, what your dispatch authority looks like, and what your registration record represents to counterparties. Select the role that most accurately describes your participation intent.
You operate or are developing a generation asset — SMR, solar-plus-storage, microgrid, or other firm or intermittent capacity. You attest what you can produce and deliver. Your registration CU is the capacity claim that load nodes and market participants will reference when structuring dispatch agreements.
Generation nodes may initiate Register, Dispatch (generation side), and Settle operations.
You operate an industrial load — AI compute cluster, advanced manufacturing cell, data center campus, or other large-scale energy consumer whose operational reliability cannot depend on grid uncertainty. You attest your load profile and demand requirements. Your registration CU is what generation nodes evaluate when accepting dispatch commitments.
Load nodes may initiate Register, Dispatch (load side), and Settle operations.
You are building applications, tooling, or market logic on top of the Meridian protocol. Settlement engines, load forecasting models, dispatch optimization layers, market analytics — the protocol handles the attestation layer. You build on top of a chain that is already proof. Registration gives you API access and establishes your participation record in the federation.
Developers may initiate Register operations and access the read API. Dispatch and Settle operations are available to applications acting on behalf of registered generation or load nodes.
You are a regulator, policy researcher, legislative staffer, or institutional observer engaged with the governance architecture of decentralized energy-compute markets. Registration establishes a CU record of your participation without conferring dispatch or settlement authority. The federation's audit record is open to observers by design.
Every Meridian transaction is attested from registration through dispatch through settlement. The audit record is the authorization mechanism — not a retrospective receipt, but the gate through which every operation passes. Observer registration gives you standing in the chain and read access to the full federation record.
Your record is created immediately. Your CU follows.
Registration Received
Your submission is recorded immediately. Name, organization, role, contact, and capacity description — this is the narrative record that will be attached to your founding Chandra CU. It is preserved from the moment of submission.
CU Written on Backend Launch
When the Meridian attestation layer goes live, your registration produces its Chandra CU. The CU is the immutable, hash-chained record of your founding participation. You will receive your CU reference at the contact address you provide.
You Are in the Chain
Early registrants are the federation's founding record. Their CUs are first in the chain. The chain is append-only. The founding record cannot be superseded — it can only be extended. You were here from the beginning, and the chain proves it.
Dispatch & Settlement
Once your CU exists and the federation is operational, you may initiate dispatch and settlement operations per your role. Generation nodes connect to load nodes. Transactions are attested from match through close. The market runs on the chain.
The Meridian attestation layer is in active development. To register your capacity and establish your founding record, send your name, organization, role, and capacity description to:
Include in your message: