# DINX EVM (beta)

<figure><img src="/files/2UuNUXU5sbhU64mSVF0O" alt=""><figcaption></figcaption></figure>

### What is DINX?

DINX (short for **Distributed Indexer**) is an innovative system designed to offer efficient and reliable data indexing for inscriptions. It utilizes a **Layer 1.5 architecture**, to build a virtual chain for inscriptions, separating them from the main Ethereum chain. This structure enhances scalability and reduces the usability threshold.

The DINX consensus system is maintained jointly by the **DINX protocol**, the **Inscription Protocol Party**, and a **Distributed Mining System**. This collaborative effort ensures the security and integrity of inscription data, providing a reliable framework for indexing.

By leveraging the **security and decentralization** of Layer 1 public chains and combining them with the scalability and performance benefits of Layer 2 solutions, DINX ensures high efficiency in handling large datasets, real-time queries, and supports multiple inscription indexing environments.

***

### How DINX Works

DINX employs a virtual blockchain architecture, abstracting inscriptions across multiple protocols into a unified framework. Each protocol is supported by a decentralized network of indexers to ensure consistent and verifiable data. To guarantee data consistency, **becoin nodes** (official protocol indexers) are employed, along with **dedicated data validators** who conduct third-party checks.

In this structure, all **fungible tokens (FT)** in the inscription protocols are unified under a single **DINX ERC20** standard. The unique value of each inscription is derived from its **protocol name** and **tick**, allowing us to calculate corresponding virtual FT contract addresses. These addresses can be interacted with using the standard **ERC20 methods** (e.g., `getBalance`, `totalSupply`), enabling all inscriptions to follow a uniform execution standard. This consistency is easily understood and recognized by most users, facilitating seamless integration for wallets and dApps.

DINX also provides a standardized RPC interface for structured data output. This ensures that all data can be easily consumed by wallets, dApps, and other applications, playing a key role in unified ecosystem development.

***

### What Problems Does DINX Solve?

DINX leverages **EVM** to build a high-performance virtual public chain for storing inscription-related data, similar to **HyperLiquid**. By isolating inscription data from the non-inscription data (which makes up only a small fraction of overall transactions on the main chain), we significantly improve the operational efficiency of the network.

DINX is designed as a **decentralized indexing service** for **B2B service providers** and ecosystem developers, including wallet applications and exchanges with embedded tokens. The system is fully decentralized, maintained by a network of contributors. Miners gather data packets through DINX nodes, capturing requests related to the supported inscription records within the index.

<figure><img src="/files/5ttKFFeDlMJIVq2hyRvr" alt=""><figcaption></figcaption></figure>

***

### DINX Beta

DINX EVM is now in **beta**. You can experience the following features via [`https://explorer.dinx.io`](https://explorer.dinx.io):

* Add DINX RPC to your wallet to extend inscription support for Ethereum's native network.
* View **IERC protocol assets** in your wallet (currently only balance viewing is supported).
* Explore inscriptions using the **Block Explorer** (currently in progress).

Access **DINX Yellow Book V1.0** at [Yellow Paper](https://hackmd.io/@DINX/yellow_paper).


---

# 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.ierc20.com/devs/dinx-evm-beta.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.