> For the complete documentation index, see [llms.txt](https://docs.jazdid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jazdid.com/developers/architecture.md).

# Architecture

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

## Major Components

### RegistrarController

The unified portal for register and renewal of different top-level domains (TLD) will be charged according to the registration fees configured by different registrars.

### Registrar

The registrar is responsible for allocating subdomains. Registrars can be configured at any level, and are pointed to by the owner field of the registry.

### ReverseRegistrar

The registrar responsible for managing reverse resolution via the ***.addr.reverse*** special-purpose TLD.

The reverse registrar provides functions to claim a reverse record, as well as a convenience function to configure the record as it's most commonly used, as a way of specifying a canonical name for an address.

The reverse registrar is specified in [EIP 181](https://eips.ethereum.org/EIPS/eip-181).

### PublicResolver

PublicResolver implements a general-purpose resolver that is suitable for most standard use-cases. The public resolver permits updates to domain name records by the owner of the corresponding name.

### Registry

All domain name lookups start by querying the registry. The registry maintains a list of domains, recording the owner, resolver, and TTL for each, and allows the owner of a domain to make changes to that data.

### BulkRegistrarController

Auxiliary contract of registrarController, support bulk query registration price, bulk search domain names availability, and batch renewal function.


---

# 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://docs.jazdid.com/developers/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.