Skip to main content
This concept has been absorbed into peaqOS. See peaqID for the current identity model.
You can fully customize the identity document. All fields are optional; sensible defaults are applied if omitted. Accepted options and types:
  • id: string (default: generated from your address)
  • controller: string (default: same as id)
  • verificationMethods: array of objects { id: string, type: string, controller: string, publicKeyMultibase: string }
  • authentications: array of strings (verification method references)
  • services: array of objects { id: string, type: string, serviceEndpoint?: string, data?: string }
  • signature: object { type: string, issuer: string, hash: string }
  • name: string (stored on-chain; default: did:peaq:<address>)
  • tx_options, on_status: transaction options/callback
Example (custom fields):
Notes:
  • If you only want the minimal document, you can omit all fields; defaults are applied.
  • Services support either serviceEndpoint or compact data for small payloads.
  • For FINAL confirmation and status logs, pass tx_options and on_status.