This page covers domain registration on the Emerging Platform. Every solution on the platform registers its organisations, projects, assets, protocols and oracles as digital twin domains, which hold their identity and state. Emerging Household Energy uses the same flow.
A domain is the whole presence of something on IXO: an ownable entity NFT at its core, a DID, an on-chain record (its IID document), controllers, owners, an optional governance group, linked resources, services, claims and accounts. See Core concepts for the full list. After reading, you will know how to choose a protocol for a new domain, what its entity document must contain, how the governance vote works, and how to check the result.
What you can register
| Kind of domain | Examples |
|---|---|
| Organisations | Legal organisations that manage clean cooking projects |
| Projects | Mitigation activities and programmes |
| Assets | Physical devices and tokenised outcomes |
| Protocols | Templates and governance rules |
| Oracles | AI-enabled verification services |
What a domain record holds
| Part | What it contains |
|---|---|
| Digital identifier (DID) | Follows the Interchain Identifier method. Self-sovereign, cryptographically secure, globally unique, resolvable, permanent and immutable. |
| Entity metadata | Verification credentials, relayer node assignment, validity period, operational status and verification state. |
| Service configuration | API endpoints, data streams, oracle integrations and payment services. |
Register a domain
Choose a protocol
Browse the available protocol templates, review the domain specification each one requires, and choose the one that fits. See Find available protocols for a query that lists them.
Create the entity document
Fill in the entity document your protocol requires. It needs:
- a protocol class reference
- the entity type
- a relayer node assignment
- a validity period (optional)
- an initial status
Entity document (illustrative example)
{
"@context": {
"class": "did:ixo:entity:abc123",
"type": "CleanCookingProject",
"version": "1.0"
},
"credentials": [],
"relayerNode": "did:ixo:entity:relayer123",
"validFrom": "2024-01-01T00:00:00Z",
"status": "active"
}Submit it for verification
Submit the domain proposal to a DAO. Voters decide whether to verify it, and on approval the verification runs automatically. The next section describes the vote.
Governance and DAO workflow
A domain change (a new domain, a protocol class, a relayer, or material metadata) is packaged as a proposal. Voters decide whether the network should treat that domain as verified and active for the programme it is meant for.
- Draft. Complete the entity document and the evidence your template requires: controllers, relayer, protocol DID and any credentials. Use Digital identifiers and Data integrity as guardrails.
- Submit. Send the proposal through the governance tool your deployment uses, for example on-chain gov module parameters, a Studio or Portal workflow, or APIs specific to your operator. Confirm which with your programme operator. The exact transaction or HTTP call depends on the deployment. Align it with the Emerging Platform API and Networks and endpoints.
- Vote. Token holders, committee members or allow-listed voters weigh the risk, the relayer assignment and the fit with the protocol. Outcomes are usually pass, fail or abstain, with a quorum threshold.
- Execute. On approval, the state changes run: verification flags, registry pointers and service enablement. On rejection, the domain stays inactive or reverts to its previous version, depending on the module's rules.
For how governance fits into IXO, see Core concepts. For the starting points by what you want to do, see Choose your path.
Check before you submit
- The controllers and keys match whoever will operate the entity on chain.
- The protocol or class DID is the one your template expects.
- The relayer and service endpoints can be reached from your environment.
- Evidence and metadata match Digital certification where it applies.
After the vote
- Poll the domain's status with GraphQL (see Query examples) or your operator's dashboard.
- Rotate credentials if the proposal changed controllers or services. See the Authentication matrix.
Who does what
| Work | Typical role | Where to start |
|---|---|---|
| Integration, keys and automation | Developer | Build on the protocol |
| Evidence review, rubrics and approvals | Evaluator | Build an evaluator |
| Capital and outcome-linked funding | Funder | Design outcomes-based financing |
| Implementation and service delivery | Service provider | Do work and get paid |
Query examples
Find available protocols
Illustrative example: list the protocols registered under one relayer node.
query EntitiesByRelayerNodeAndType {
entities(
filter: {
relayerNode: {equalTo: "did:ixo:entity:a1fcead81eab2f1158a726597d872413"},
type: {equalTo: "protocol"}
}
) {
nodes {
id
type
metadata
}
}
}Check domain status
Illustrative example:
query DomainStatus($did: String!) {
entity(id: $did) {
id
status
verificationStatus
credentials {
type
status
}
}
}Next steps
- Review the available protocols
- Prepare the entity document
- Submit for verification
- Configure services
- Monitor status
Developer resources:
- Emerging Platform API
- SDK guide: client libraries and tools.
- Example projects
- Developer support on Slack