> For the complete documentation index, see [llms.txt](https://docs.thehemera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thehemera.com/welcome/account-centric-indexing-protocol/example-hemera-use-cases/evm-chain-history-preservation.md). # EVM chain history preservation {% hint style="warning" %} Note: This is a roadmap item that is not currently available. We are documenting it here to give developers an idea of potential use cases that can be supported by Hemera Network. {% endhint %} Ethereum's history growth is gradually increasing the hardware requirements for running full nodes. For long, Ethereum community has been working on [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444), which requires a solution for history preservation of Ethereum's full nodes. Similar needs will also arise, likely a lot fast, in high performance EVM scenarios, where history grows at 100 \~ 10,000X faster speed. As such, an EVM history preservation service designed in a similar architecture as in[ ](/welcome/account-centric-indexing-protocol/example-hemera-use-cases/ethereum-long-term-da.md)[the previous section](/welcome/account-centric-indexing-protocol/example-hemera-use-cases/ethereum-long-term-da.md) can be expanded to meet such needs. --- # 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.thehemera.com/welcome/account-centric-indexing-protocol/example-hemera-use-cases/evm-chain-history-preservation.md?ask=&goal= ``` `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.