Skip to main content
Use this guide for domain setting workflows. It focuses on protocol-facing document management and avoids service-specific endpoint duplication.

​
Before you start

  • You control the target domain DID.
  • You have signing authority for domain update transactions.
  • You have selected the target network from /reference/networks-and-endpoints.

​
What this guide does

You apply common domain setting operations and verify that changes are committed through protocol interfaces.

​
Core operations

  • Update DID document fields.
  • Add or revoke verification methods.
  • Add or remove services.
  • Manage controllers and linked resources.

​
Protocol boundary

These operations are IXO Protocol concerns. Service APIs such as Registry or Matrix can consume domain metadata, but they do not replace protocol-level document authority.

​
Example protocol message literal

const msg = {
  typeUrl: "/ixo.iid.v1beta1.MsgUpdateIidDocument",
  value: {
    id,
    controller,
    verificationMethod,
    authentication,
    service
  }
};

​
Verify the result

Expected result:
  • document query returns updated fields;
  • updates are attributable to an authorized controller.

​
Next steps

  • Domain privacy guide: /guides/dev/domain-privacy
  • Blockchain REST API: /api-reference/grpc-gateway-api
  • Authentication matrix: /reference/authentication-matrix