# Summary of Xenea

The Xenea is an EVM-compatible Layer 1 blockchain with integrated autonomous decentralized storage. Our core architecture papers have passed peer reviews in informatics societies, including the IEEE, and have been academically recognized for the robustness of the protocol.

Our approach is aimed at ensuring financial inclusion and ensuring assets with value are passed down to the next generation. We foresee widespread tokenization of real world assets (RWAs) and believe tokenization through NFTs will become increasingly important. However, current tokenization with NFTs often results in real data being stored in external storage, which could lead to loss of asset data and inconsistent ownership in the future. Thus, we aim to ensure data consistency and provide an infrastructure for secure transactions, allowing assets to be passed down to future generations.

Key technical features of the Xenea are as follows:

* EVM Compatible: Application developers can easily deploy applications for existing EVM compatible chains on the Xenea while using the development tools they are familiar with.
* PoD (Proof of Democracy) : Consensus algorithms which do not rely on token prices for security and allow for massive decentralization will enable secure trading and transfer of assets for decades to come.
* DACS (Decentralized Autonomous Content Storage): The Xenea integrates autonomous decentralized storage. This ensures data persistence with data and token consistency.


---

# 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.xenea.io/overview/summary-of-xenea.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.
