> For the complete documentation index, see [llms.txt](https://ethernal-2.gitbook.io/blade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ethernal-2.gitbook.io/blade/detailed-design/evm-compatible-data-structures.md).

# EVM Compatible data structures

The Ethereum blockchain data structure was defined in the [Ethereum Yellow Paper](https://ethereum.github.io/yellowpaper/paper.pdf), authored by Dr. Gavin Wood in April 2014. This foundational document established the core principles of Ethereum’s state transition system, including its use of Merkle Patricia Trees for efficient state management.

Ethereum’s data structure is based on an **account-based model** (as opposed to Bitcoin’s UTXO model), where each account maintains:

* **Balance**
* **Nonce**
* **Storage**
* **Code**

The blockchain itself is structured as a **linked list of blocks**, where each block contains:

* A **header**
* A **transaction list**
* **Receipts**

The state of the Ethereum Virtual Machine (EVM) is maintained using a **modified Merkle Patricia Trie**, enabling efficient verification and storage of account states.

These design choices allow Ethereum to support **smart contracts** and **decentralized applications (DApps)** while ensuring:

* **Security**
* **Transparency**
* **Scalability**


---

# 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:

```
GET https://ethernal-2.gitbook.io/blade/detailed-design/evm-compatible-data-structures.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.