# Merkle-Patricia-trie

*Merkle tree* are Hashes of Hashes, they have the advantage that you can verify only a subtree. Ethereum uses [Modified Merkle Patricia Tries](https://github.com/ethereum/wiki/wiki/Patricia-Tree) for transactions (as well as for state and transaction receipts).

what about *Patricia* ? What does a *trie* mean? And how is it used in Ethereum?

**Trie (also called digital tree, prefix trie or radix trie)**

An ordered tree data structure that is used to store a dynamic set or associative array where the keys are usually strings. A node's position in the tree defines the key with which it is associated.

![](https://1340157391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LsbZSdJt5HV2Zixq30m%2F-LsbZ_tYd61Y1p0HMBOm%2F-LsbZbXkEAsIMc4P2dNr%2Ftrie1.png?generation=1572621941587568\&alt=media)

![](https://1340157391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LsbZSdJt5HV2Zixq30m%2F-LsbZ_tYd61Y1p0HMBOm%2F-LsbZbXmzJIzAyUM2rY4%2Fpat.png?generation=1572621942130178\&alt=media)

**Merkle Patricia Trie**

As described [here](https://easythereentropy.wordpress.com/2014/06/04/understanding-the-ethereum-trie/) <https://easythereentropy.wordpress.com/2014/06/04/understanding-the-ethereum-trie/>, the term Merkle implies that

> the root node becomes a cryptographic fingerprint of the entire data structure

![](https://1340157391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LsbZSdJt5HV2Zixq30m%2F-LsbZ_tYd61Y1p0HMBOm%2F-LsbZbXodtXx496WlQdi%2Fmerkele.png?generation=1572621948894791\&alt=media)


---

# 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://nag-9-s.gitbook.io/block-chain-notes/merkle-patricia-trie.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.
