# Sidetree

[DID:ION](https://github.com/decentralized-identity/ion) leverages the blockchain-agnostic [Sidetree](https://identity.foundation/sidetree/spec/) protocol to anchor tens of thousands of DID/DPKI (Decentralized Public Key Infrastructure) operations into one single on-chain Bitcoin transaction. These transactions are encoded so [DID:ION](https://github.com/decentralized-identity/ion) nodes can fetch, store, and replicate hash-associated DID operation batches via IPFS (InterPlanetary File System). [DID:ION](https://github.com/decentralized-identity/ion) nodes process operations in batches that independently arrive at the corrected DPKI state for system IDs, without the need for consensus mechanisms, blockchain, or sidechain. Nodes can work in parallel to fetch, process, and assemble DIDs, allowing nodes to run tens of thousands of operations per seconds. This allows Zion to create a robust decentralize identifier network that does not require trusted intermediaries, centralized authorities, or secondary consensus mechanisms.<br>

## Sidetree Network Topology

<figure><img src="/files/LhJCzq61BGrUP6dvv2Yy" alt=""><figcaption><p>Sidetree Network Topology</p></figcaption></figure>

**Bitcoin Ledger:** Global [anchoring ](https://identity.foundation/sidetree/spec/#anchoring-system)and linear sequencing system for DID operations

**Sidetree nodes:** Nodes that interact with the [anchoring system](https://identity.foundation/sidetree/spec/#anchoring-system) to anchor operations, as well as fetch and replicate CAS network data.

**Content Accessible Storage(CAS):** A IPFS Network that Sidetree nodes utilize to distribute and replicate DID operation files.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.zion.fyi/architecture/did/sidetree.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.