Skip to main content
This page documents the Emerging Platform identity layer. Use it when you need reusable identifier and controller patterns. For household-energy workflows, pair this with the Emerging 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

​
Core model

Each entity is represented by a DID and an associated domain record with:
  • identifier and type metadata
  • controller references
  • service endpoints
  • linked claims and credentials

​
Where this is used

This platform capability is used by:
  • /platforms/Emerging/household-monitoring
  • /platforms/Emerging/stove-use-monitoring
  • /platforms/Emerging/emerging-dmrv

​
Cross-product IXO dependencies

  • IXO Protocol for DID and domain state anchoring: /articles/ixo-blockchain
  • Impact Hub Registry for entity and claim records: /platforms/Emerging/registry
  • IXO Matrix for encrypted payload storage when data should not be on-chain: /articles/ixo-matrix

​
Next steps

  • Read /platforms/Emerging/domain-registration for entity registration flow.
  • Read /platforms/Emerging/registry for query and record management.

​
title: “Digital identifiers” icon: “id-card” description: “Use DID-based identity on the Emerging Platform and understand how Emerging Household Energy uses it.”

This page documents a cross-product IXO dependency used by both the Emerging Platform and the Emerging Household Energy solution. Use it when you need the identity model, not household workflow steps.

​
Scope

Digital identifiers provide stable identity for entities such as projects, households, devices, and agents. In this section:
  • platform scope: identity model and control patterns
  • solution scope: household-energy entities that use the model

​
Core model

  • 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 to apply this

  • Platform integration: identity-first registry and claim workflows.
  • Household Energy implementation: register households and devices before monitoring and reporting.
  • Registry integration: /platforms/Emerging/registry
  • Domain-level setup: /platforms/Emerging/domain-registration
  • Credential lifecycle: /platforms/Emerging/credential-issuance
  • Household implementation: /platforms/Emerging/household-monitoring