peaqID

W3C DID for machines, portable across every chain peaqOS supports.

peaqID is a W3C DID that identifies a machine across every chain it transacts on.

DID format

There are two peaqID formats, one per generation of machine.

Economics 2.0 machines

did:peaq:<machine id as decimal>

The machine ID is uint256(keccak256(abi.encode(machineType, credentialSubject))), the same value as the machine’s ERC-721 token ID in MachineRegistry. The DID document (controller, verification methods, authentication indices, service endpoints) is stored in MachineRegistry itself at activation and updated with the DID setters; id is computed on read, never supplied. Documentation and data API URLs live in serviceEndpoints. There is no mapping from an address-form DID to a 2.0 machine ID. A machine homed on Solana keeps the same did:peaq:<decimal id> form; its DID document lives in the machine’s Solana accounts, verification-method controllers are base58 Solana keys, and each list holds at most 8 entries with 128 UTF-8 bytes per string. See Solana onboarding: the DID document and Economics 2.0.

Tokenomics 1.0 machines (onboarded before 2026-09-01)

did:peaq:<0x-address>

The address is the machine’s EOA (externally owned account) on peaq chain. The DID resolves to a flat key-value attribute store on the peaq DID precompile (0x0000000000000000000000000000000000000800). Any consumer can start from the DID and traverse on chain to the machine’s identity and financial history. The rest of this page describes this format.

peaq chain has roughly 3.5 million peaqID holders from before peaqOS, and they keep their peaqIDs.

Per-machine vs per-proxy

Tokenomics 1.0 path. This section and the DID attribute table describe the Tokenomics 1.0 model: registerMachine / registerFor and the DID attribute writers serve machines already onboarded under Tokenomics 1.0. New machines store their DID document in MachineRegistry at activation; see Economics 2.0 machines.

peaqOS assigns one DID per machine and one DID per proxy operator. The two serve different roles:

DID type	Registered by	Attributes	Purpose
Machine DID	registerMachine (self-managed) or registerFor (proxy delegation)	machineId, nftTokenId, operator, documentation_url, data_api, data_visibility	Identifies a single machine, links to its Machine NFT and event history
Proxy DID	registerMachine. The proxy itself is a registered machine.	machineId, machines	Identifies an operator, lists the machine IDs of all machines it manages

A machine that self-manages has no operator attribute. A proxy operator’s machines attribute is a JSON array of machine IDs (e.g., [123, 456, 789]).

DID writes always go to the caller’s DID. The DID precompile keys attributes by msg.sender, so a proxy that calls registerFor mints the machine’s identity NFT and pays the bond but cannot write the machine’s DID attributes. The machine must sign its own writeMachineDIDAttributes call.

DID attribute table

Under Tokenomics 1.0, registration mints the identity and creates the on-chain machine ID. Writing these attributes is a separate transaction: call writeMachineDIDAttributes, or writeProxyDIDAttributes for a proxy operator.

Attribute	Type	Description
machineId	uint256	On-chain machine ID assigned by IdentityRegistry. Primary key for all queries.
nftTokenId	uint256	Token ID of the machine’s Machine NFT. This is a separate ERC-721 token space and is not equal to machineId.
operator	did:peaq:0x...	Proxy operator’s DID. Absent if the machine self-manages.
documentation_url	URL string	Link to machine documentation maintained by the project.
data_api	URL string	Raw data API endpoint maintained by the project.
data_visibility	public / private / onchain	Data visibility setting. Unset or empty defaults to private.
machines	JSON array string	Proxy operator DID only. List of managed machine IDs. The DID precompile stores the full JSON.

Byte limits

Both SDKs enforce these constraints before any DID write reaches the chain:

Constant	Value	Applies to
DID_MAX_NAME_BYTES	64	Attribute name
DID_MAX_VALUE_BYTES	2560	Attribute value

Resolving a peaqID

The MCR API resolves an Economics 2.0 machine at https://mcr.peaq.xyz/machine/did:peaq:<decimal machine id>. It does not resolve address DIDs: did:peaq:0x... returns 400 Invalid machine DID format.

JS/TS

const MCR_API_URL = "https://mcr.peaq.xyz";
const did = "did:peaq:108934426058480933785963234320575706003575332367737915173645220784539698794848";

// Fetch machine profile by DID
const response = await fetch(`${MCR_API_URL}/machine/${encodeURIComponent(did)}`);
const machine = await response.json();

console.log(machine.peaqos.did);                 // "did:peaq:1089..."
console.log(BigInt(machine.peaqos.machine_id));  // decimal string on the wire
console.log(machine.peaqos.mcr);                 // "Provisioned" here; a rated machine returns a grade such as "BBB"

The profile reports data_visibility: "private" for every machine and carries no event rows or partner data. data_api is present when the machine’s DID document carries a peaq-data-api service endpoint. The SDK response types keep optional event_data, partner_data, and partner_data_error keys; the MCR API does not return them.

Cross-links

• Activate function creates the machine and stores its DID document (Economics 2.0), or registers it and writes DID attributes (Tokenomics 1.0)
• GET /machine/{did} returns the full machine profile, including DID-sourced metadata
• Machine NFT is linked to the peaqID via the nftTokenId attribute