> For the complete documentation index, see [llms.txt](https://ordict.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ordict.gitbook.io/whitepaper/technology/technical-architecture.md).

# Technical Architecture

<figure><img src="/files/npKsdRMHMyP44QDUbnbY" alt=""><figcaption></figcaption></figure>

Ordict's Soulbound Protocol is built on a robust technical infrastructure designed to leverage the Bitcoin blockchain for secure and verifiable user achievement records and digital credentials. This section outlines the critical modules involved in the setup.

**Bitcoin Blockchain**

At the core of the Soulbound Protocol is the Bitcoin blockchain, which provides the foundation for data immutability and security. All inscription data is embedded directly within Bitcoin transactions using the taproot spend script, ensuring that the records are permanently stored and protected by Bitcoin's proof-of-work consensus mechanism.

#### Burn Mechanism

A cornerstone of the Soulbound Protocol is its **burn mechanism**, which ensures the permanence and integrity of inscriptions by irrevocably tying them to the owner's identity:

* **Burn Process**: After a Soulbound Inscription is created, it is sent to a burn address, making it non-transferable. While the inscription is no longer in circulation, its metadata remains accessible and verifiable on the Bitcoin blockchain.
* **Ownership Proof**: The inscription’s association with the owner's wallet is retained through signature verification. Only the original wallet's private key can authenticate ownership, ensuring the inscription remains securely tied to the rightful owner.
* **Permanent Record**: This approach solidifies the concept of Soulbound Inscriptions by ensuring they are immutable and cannot be reassigned, preserving the trust and authenticity of the data.

**Soul Indexer**

The Soul Indexer is a decentralized registry that crawls and indexes inscription data stored on the Bitcoin blockchain. It utilizes sophisticated data structures and indexing mechanisms to facilitate rapid search and retrieval of SBIs based on various criteria, such as issuer identity, achievement type, or specific keywords within the inscription data. This indexer is crucial for providing quick access to the necessary information.

**Provenance Setup with Parent-Child Relationships**

Provenance tracking within the Soulbound Protocol is established through a parent-child relationship system. This setup allows for detailed tracking of related achievements and credentials by:

* **Parent Inscriptions**: Serving as the foundational records created by authorized issuers.
* **Child Inscriptions**: Containing additional data linked to the parent inscriptions, ensuring data integrity and origin.
* **Audit Trails**: Creating a clear lineage of data modifications and updates, enhancing transparency and trust.

**Verification Engine**

The Verification Engine is essential for ensuring the authenticity and validity of Soulbound Inscriptions. It allows anyone to verify the integrity of an inscription's data and the legitimacy of the issuing organization by:

* **Cryptographic Validation**: Validating the digital signatures embedded within SBIs using the issuers' public keys.
* **Provenance Tracking**: Confirming the origin and integrity of the data, ensuring it hasn't been tampered with.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://ordict.gitbook.io/whitepaper/technology/technical-architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.