peaqID

peaqID is a W3C 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 is the machine’s on . The DID resolves to a flat key-value attribute store on the peaq DID (0x0000000000000000000000000000000000000800). Any consumer can start from the DID and traverse to the machine’s identity, financial history, and through the 1.0 MCR API. 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. A migration path to the current DID format is on the roadmap.

Per-machine vs per-proxy

peaqOS assigns one DID per machine and one DID per . 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 (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 the machine’s and pays the but cannot write the machine’s DID attributes. The machine must sign its own writeMachineDIDAttributes call, or it stays unreachable through the .

DID attribute table

Registration mints the identity and creates the machine ID. Writing these attributes is a separate : 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. The MCR API reads this when `data_visibility` is `public`.
`data_visibility`	`public` / `private` / `onchain`	Controls how the MCR API exposes raw event data. 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; the MCR API reads the full list and pages it with `offset` and `limit` (20 per page).

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

import "dotenv/config";
import { PeaqosClient } from "@peaqos/peaq-os-sdk";

const client = PeaqosClient.fromEnv();

// Fetch machine profile by DID
const response = await fetch(
  `${client.apiUrl}/machine/did:peaq:0xMachineAddress`
);
const machine = await response.json();

console.log(machine.peaqos.did);         // "did:peaq:0x..."
console.log(machine.peaqos.machine_id);  // 123
console.log(machine.peaqos.mcr);         // "BBB"

from dotenv import load_dotenv
import requests
from peaq_os_sdk import PeaqosClient

load_dotenv() # load envs from .env file

client = PeaqosClient.from_env()

# Fetch machine profile by DID
response = requests.get(
    f"{client.api_url}/machine/did:peaq:0xMachineAddress"
)
machine = response.json()

print(machine["peaqos"]["did"])         # "did:peaq:0x..."
print(machine["peaqos"]["machine_id"])  # 123
print(machine["peaqos"]["mcr"])         # "BBB"

Data visibility modes

The data_visibility attribute controls how the MCR API handles raw data for this machine:

Mode	MCR API behavior	Raw data location
`public`	Fetches from `data_api`, includes in response	Project’s API
`private`	Returns the `data_api` URL only; consumer fetches directly	Project’s API
`onchain`	Parses JSON metadata from EventRegistry events into `event_data[]`, capped at the first 100 events per response	Onchain (higher gas cost)

private is the default when data_visibility is unset or empty.

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/ returns the full machine profile, including DID-sourced metadata
Machine NFT is linked to the peaqID via the nftTokenId attribute

Welcome

Get Started

Concepts

Functions

Guides

DID format

Economics 2.0 machines

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

Per-machine vs per-proxy

DID attribute table

Byte limits

Resolving a peaqID

Data visibility modes

Cross-links

​DID format

​Economics 2.0 machines

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

​Per-machine vs per-proxy

​DID attribute table

​Byte limits

​Resolving a peaqID

​Data visibility modes

​Cross-links

DID format

Economics 2.0 machines

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

Per-machine vs per-proxy

DID attribute table

Byte limits

Resolving a peaqID

Data visibility modes

Cross-links