Keys ready
Keys ready. Next: verify identity for application.
Create a wallet, complete KYC off-chain, apply for registry roles, then wait for consortium or governance admission. On-chain ACTIVE is not the same as identity verified and does not show that a meter reading was true.
Drivers, employees, checkers, and regulators-as-people.
Legal entity, beneficial owners, and binding authority for keys.
| UI label | Role enum |
|---|---|
| Site / facility operator | OPERATOR / PRODUCER / CONSUMER |
| Data integrator | INTEGRATOR |
| Checker | CHECKER |
| Verifier | VERIFIER |
| Regulator seat | REGULATOR |
| AI reviewer | AI_REVIEWER |
| Adjudicator | ADJUDICATOR |
| Node operator | NODE_OPERATOR |
Keys ready. Next: verify identity for application.
Your KYC case is with the verification vendor.
Review the reason code and contact support if you need to appeal.
Choose registry roles, jurisdiction, and legal name. This is not on-chain activation.
Your package is in the consortium queue. Governance or authority still activates the participant.
A participant id exists with PENDING status until admission completes.
You are admitted for the roles on your participant record. Identity verified for application is not meter truth.
This participant is suspended. Write paths may be unavailable.
This participant was revoked. The chain history remains readable.