# Technology behind Context

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

### Application Layer

This layer enables users and enterprises to manage domains, query data, and anyone to interact with the DNS3 ecosystem. Additionally, the Application Layer supports the integration of third-party applications via our **SDK** or **Public Gateway**, allowing developers to easily connect their services with DNS3. For companies, this layer also includes a **Dashboard (SaaS)** that offers comprehensive tools for managing and monitoring their domains and data within the Web3 environment.

### Abstraction Layer

Using **MongoDB Atlas**, DNS3 implements a semantic caching system that temporarily stores frequently accessed queries and semantically enriched responses, significantly reducing response times. We also create a Vector Search that supports AI training, particularly Retrieval-Augmented Generation (RAG), enhancing the accuracy and efficiency of AI models by providing them with real-time, structured data. Additionally, account abstraction is handled through **Biconomy**, allowing for the creation of smart wallets for users, making interactions with the blockchain effortless and user-friendly.

### Integration Layer

This layer manages the deployment of **multiple smart contracts (Top-Level Domain “TLD” Registry)** across different blockchains, ensuring that they are interoperable and can communicate effectively. By leveraging **LayerZero**, DNS3 ensures that contracts can interact seamlessly between chains, allowing for a truly decentralized and interconnected Web3 environment.

### Storage Layer

The Storage Layer integrates multiple Web3 storage solutions to handle both public and private data. For public data, DNS3 connects with decentralized storage networks like **Arweave**, **BNB Greenfield**, or **Swarm**, ensuring that data is distributed and securely stored across the network. For private data, DNS3 supports encrypted solutions like **Ten Protocol**, allowing sensitive information to be stored securely and accessed only by authorized parties.


---

# 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/protocol-overview/technology-behind-context.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.