> ## Documentation Index
> Fetch the complete documentation index at: https://ixoworld-mintlify-9a7944b6.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# IXO Protocol: record what is true, who proved it, and what changed

> Trust and action on-chain: who is involved, what exists, what is claimed, what evidence supports it, how state changes, and which operations are valid—on Impact Hub and compatible deployments.

<Tip>
  **IXO Protocol** is the module set for **identity-bound entities**, **claims**, **credentials**, **assets**, and **programmable coordination**. **Impact Hub Network** is the primary public deployment of this stack; applications and services across the ecosystem target that network unless noted otherwise.
</Tip>

**IXO Protocol** records the parts of real-world work that coordination depends on: **who** is involved, **what** exists in the model, **what** is claimed, **what evidence** supports assertions, **how** important state changes over time, and **which actions** are valid under the rules.

It is how you move from “messages and documents about a program” to **inspectable, permissioned state** that agents and partners can rely on—then extend with [IXO Matrix](/articles/ixo-matrix), [IXO Blocksync](/articles/ixo-blocksync), and [Agentic Oracles](/articles/agentic-oracles) for full workflows.

## Conceptual scope

<AccordionGroup>
  <Accordion title="Protocol primitives" icon="puzzle-piece">
    IXO Protocol provides modules for identity-bound entities, claims workflows, and programmable coordination.
  </Accordion>

  <Accordion title="Network deployment" icon="server">
    Impact Hub Network is the primary public deployment used by applications and services in the IXO ecosystem.
  </Accordion>

  <Accordion title="Cross-service role" icon="layer-group">
    IXO Matrix, IXO Blocksync, and Agentic Oracles integrate with IXO Protocol to execute end-to-end workflows.
  </Accordion>
</AccordionGroup>

## Why it matters

* Anchors identities and rights in verifiable records.
* Supports claims and attestations that drive downstream workflows.
* Provides the shared state foundation for tokenized and governed coordination.

## Go here next

<CardGroup>
  <Card title="Developer guides" icon="hand-pointer" href="/guides/dev/overview">
    Follow task-oriented implementation guides.
  </Card>

  <Card title="API reference" icon="server" href="/api-reference/index">
    Use canonical API pages for exact interface details.
  </Card>

  <Card title="IXO Blocksync" icon="magnifying-glass" href="/articles/ixo-blocksync">
    Understand the indexed query layer that sits above protocol state.
  </Card>
</CardGroup>