# Registry (TLDs)

The Registry is a decentralized and open-source smart contract that acts as the backbone of the Context ecosystem. It serves as a global, decentralized name service for data that is stored within the Context network. The Registry allows users to associate a unique name to a Context documents, which can then be easily referenced and queried by other users within the ecosystem.

**Functionality**

The primary function of the Registry is to provide a mapping between names and context documents. Each name in the Registry corresponds to a specific linked list of transactions, and this name is unique. This means that once a name is assigned to a context document, it cannot be used for another document. This unique mapping allows users to easily locate and access the data stored in a context document by using its assigned name.

**Decentralization**

The Registry is decentralized, meaning it is not controlled by any single entity. Instead, it is maintained by the users of the Context Protocol. This decentralization enhances the security and reliability of the Registry, as it is not vulnerable to single points of failure.

**Interoperability**

The Registry promotes interoperability and data portability. Since each name in the Registry corresponds to a Context document, and each Context document can be linked to one or more schemas, it is possible to link a single piece of data to multiple schemas. This makes it easier for developers to build and scale their applications, as they can leverage the same data across different schemas.

**Data Versioning**

In addition to its naming function, the Registry also supports data versioning. Each time a Context document is updated, a new version of the data is created and stored. This allows users to track the evolution of their data over time, enhancing data traceability.

\
List of deployed contracts in the future


---

# 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.ctx.xyz/dns3/smart-contracts/registry-tlds.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.