Skip to main content
This page documents the Emerging Platform identity layer and the cross-product IXO patterns used by Emerging Household Energy and other solutions. Use it for reusable identifier and controller patterns. For household-energy workflow steps, pair this with the household-energy guides.

​
What this covers

  • Creating decentralized identifiers (DIDs) for projects, households, devices, and agents
  • Managing controllers and update permissions
  • Linking claims and credentials to identifiers
  • Keeping sensitive personal data off-chain

​
Scope

  • Platform scope: identity model, controller patterns, and how domains anchor DIDs
  • Solution scope: household-energy entities that use the same model (register households and devices before monitoring and reporting)

​
Core model

Each entity is represented by a DID and an associated domain record with:
  • Identifier and type metadata
  • Controller references (who may update the DID document and authorize changes)
  • Service endpoints
  • Linked claims and credentials
At a glance:
  • A Decentralized Identifier (DID) identifies each entity.
  • Controllers manage updates and authorization.
  • Claims and credentials reference entity DIDs.
  • Registry state provides traceability for lifecycle events.

​
Where this is used

This platform capability is used by: Where to apply this
  • Platform integration: identity-first registry and claim workflows.
  • Household Energy implementation: register households and devices before monitoring and reporting.

​
Cross-product IXO dependencies

  • IXO Protocol for DID and domain state anchoring: IXO Protocol
  • Impact Hub Registry for entity and claim records: Emerging registry
  • IXO Matrix for encrypted payload storage when data should not be on-chain: IXO Matrix
For a single developer-oriented overview of DID, claims, and verifiable credentials together, see Identity and credentials.