Emerging Platform domain registration

Documentation Index

Fetch the complete documentation index at: https://docs.ixo.world/llms.txt

Use this file to discover all available pages before exploring further.

​

Domain Types

​

Domain Structure

​

Core Properties

​

Registration Process

​

1. Protocol Selection

​

2. Domain Creation

{
  "@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"
}

​

3. Verification Flow

​

Governance and DAO workflow

1. Draft — Complete the entity document and evidence your template requires (controllers, relayer, protocol DID, optional credentials). Use Digital identifiers and Data integrity as guardrails.
2. Submit — Send the proposal through the governance surface your deployment uses (for example on-chain gov module parameters, a Studio/Portal workflow, or operator-specific APIs—confirm with your program operator). The exact transaction or HTTP call is deployment-specific; align with Emerging API and Networks and endpoints.
3. Vote — Token holders, committee members, or allow-listed voters evaluate risk, relayer assignment, and protocol fit. Outcomes are typically pass, fail, or abstain with a quorum threshold.
4. Execute — On approval, state transitions run (verification flags, registry pointers, service enablement). On rejection, the domain stays inactive or reverts to the previous version depending on module rules.

​

Who does what (roles)

​

Checklists

• Controllers and keys match who will operate the entity on-chain.
• Protocol / class DID is the one your template expects.
• Relayer or service endpoints are reachable from your environment.
• Evidence and metadata align with Digital certification where applicable.

• Poll domain status via GraphQL (see Query examples on this page) or your operator dashboard.
• Rotate credentials if the proposal changed controllers or services (Authentication matrix).

​

Query Examples

​

Find Available Protocols

query EntitiesByRelayerNodeAndType {
  entities(
    filter: {
      relayerNode: {equalTo: "did:ixo:entity:a1fcead81eab2f1158a726597d872413"}, 
      type: {equalTo: "protocol"}
    }
  ) {
    nodes {
      id
      type
      metadata
    }
  }
}

​

Check Domain Status

query DomainStatus($did: String!) {
  entity(id: $did) {
    id
    status
    verificationStatus
    credentials {
      type
      status
    }
  }
}

​

Implementation Guide

1. Review available protocols
2. Prepare entity document
3. Submit for verification
4. Configure services
5. Monitor status

​

Developer Resources