> For the complete documentation index, see [llms.txt](https://eonixchains-organization.gitbook.io/welcome-to-eonix-chain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eonixchains-organization.gitbook.io/welcome-to-eonix-chain/eonix.md).

# EONIX

layer 1

EONIX is a Layer-1 blockchain. This means that in its operations, it does not depend on any other blockchain for finalizing transactions sent to it. In other words, once the EONIX  validators have achieved consensus about a transaction and added it to the ledger, this is sufficient for the transaction to be valid and irreversible.

EVM Compatible

In addition to the information about the transactions processed by the EONIX, its nodes also permanently store and update the code and current state of smart contracts. Smart contracts are computer programs (persistent scripts) that anyone can interact with by sending transactions summoning them. Smart contracts also have accounts that can hold token balances.

On the network nodes, smart contracts are stored and executed in an environment called a 'virtual machine' (VM). The EONIX blockchain is broadly compatible with Ethereum's virtual machine (EVM).


---

# 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://eonixchains-organization.gitbook.io/welcome-to-eonix-chain/eonix.md?ask=<question>&goal=<endgoal>
```

`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.