Use this guide to design private domain data handling patterns. Exact API contracts belong in protocol and service references.Documentation Index
Fetch the complete documentation index at: https://docs.ixo.world/llms.txt
Use this file to discover all available pages before exploring further.
Before you start
- Confirm your target network and endpoint set in
/reference/networks-and-endpoints. - Confirm authentication requirements for each surface in
/reference/authentication-matrix. - Confirm controller authority for the domain DID.
What this guide does
You separate privacy responsibilities across protocol metadata and service storage, then verify that sensitive values are not exposed in public document fields.Privacy model boundary
- Protocol layer: public DID document structure and authorized metadata updates.
- Service layer: encrypted payload storage and controlled retrieval patterns.
Typical workflow
- Register key material and controller relationships at protocol layer.
- Encrypt sensitive settings before writing to service storage.
- Publish only references or proofs in public protocol metadata when required.
- Enforce recipient authorization on read.
Verify the result
Expected result:- domain metadata updates succeed with authorized signatures;
- sensitive values remain encrypted in service storage;
- unauthorized reads fail.
Next steps
Domain settings
Configure services, permissions, and domain-level behavior.
API authentication
Apply correct auth patterns across IXO API surfaces.
Product and SDK map
Confirm canonical product names and SDK route mappings.