Digital twin domains

What a digital twin domain is: a domain that stands for a real-world thing, the classes of twin, what each one holds, and how protocols give twins a shape.

A digital twin domain is a domain that stands for something in the real world: a device, a household, an organisation, a project or a service. It gives that thing an identifier, a record of who controls it, a place for its data, and links to the other domains it relates to. Claims about the thing are made against its domain.

Read this page to understand the idea before you model your own system. For the record's fields, example code and how to create a twin from a protocol, use Digital twins.

Classes of twin

ClassWhat it stands forExample
Physical twinA device or sensorA cooking stove with a usage monitor
Cognitive twinAn organisational constructAn organisation, a project or a process
Oracle twinAn AI service that evaluates, verifies or automatesAn agentic oracle
Twin systemThe relationships and feedback loops between twinsA programme linked to its projects, devices and funders

Each class has its own configuration. An organisational domain, for example, contains membership groups as sub-domains.

What a twin holds

A digital twin is a domain, so it has every part a domain has. Core concepts describes each one. The parts that matter most for a twin are:

PartWhat it does for a twin
EntityThe ownable NFT at the core of the domain. Ownership can be transferred
DIDA W3C Decentralized Identifier that names the twin uniquely
ControllersThe keys or accounts allowed to update the twin's record, as its IID document defines
ServicesEndpoints the twin exposes, such as a data ingestion endpoint
Linked resourcesDocuments and media the twin references by URI, often with a hash for integrity
Accorded rightsWhat the twin is entitled to do, mainly expressed as UCAN parent capability documents
Linked claimsClaims made about the twin, such as device usage records or fuel delivery confirmations
Linked entitiesLinks to related domains, such as funders, projects or oracles
AccountsOn-chain accounts the twin holds, for payments and staking
Matrix space and VFSEncrypted rooms and a file store for the twin's data

Where a twin's data lives

A twin's working data is not on chain. Each twin domain has its own encrypted data store in IXO Matrix, where structured data and streams are recorded. Data can be shared across servers and organisations without being decrypted on the way. Larger files and public datasets can be kept in decentralised file storage such as IPFS. The chain holds the twin's record and the hashes that tie data to it. See IXO Matrix.

How claims about a twin are checked

A device, a person or an agent makes a signed claim about the twin. A decision oracle checks the evidence and produces the facts, and the IXO decision engine applies the rules and signs the decision. A decided outcome can then be issued as a W3C Verifiable Credential.

Each of those records shows something different. A signed claim shows who said what. It does not show that it is true. What each record proves goes through each one.

Protocols give twins a shape

Setting up every domain by hand is slow, so IXO uses protocols as templates. A protocol defines the default properties, relationships and data model for one type of domain. A twin created from a protocol inherits its defaults, which can then be changed for the case at hand. That gives you:

  • standard domain types you can create quickly
  • the same data structure across projects
  • child domains that trace back to their parent protocol

For example, a protocol for clean cooking projects can set the default data fields (fuel types, reporting standards, usage metrics), the relationships (verification oracles, project developers, funders) and the services (data analytics, payment frameworks, governance tools).

Agentic oracles can carry out some steps of creating domains. What they can do is described in Agentic oracles.

Where to go next