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

# Introduction

> The development of Bitcoin by Satoshi Nakamoto in 2009 demonstrated that it was possible
> \
> to create a decentralized value transfer system, without a central authority, based
> \
> solely on cryptography and the consensus mechanism of a peer-to-peer network.
>
> Ethereum subsequently expanded this concept by adding a complete programming language,
> \
> allowing anyone to deploy smart contracts and decentralized applications
> \
> directly on the blockchain.

Zeltra follows this same path. The network is based on the same technical architecture as Ethereum same virtual machine, same tool compatibility, same fee structure but it integrates a native mechanism absent from other networks:

\
an automatic redistribution of a portion of transaction fees to the participants who contribute to the growth of the ecosystem.

The idea is simple.
\
Every transaction on Zeltra generates fees. These fees fund not only the validators who secure the network, but also a partnership fund whose sole purpose is to reward those who integrate, promote, and develop the network.
\
Zeltra does not claim to reinvent blockchain. It takes what has already proven successful at scale and adds an economic engine designed to transform each active user into a driver of growth.

{% hint style="info" %}
**Zeltra** ChainId : 271017 · Native token : ZLA · technical basis : go-ethereum
{% endhint %}


---

# 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://zeltra.gitbook.io/zeltra-docs/readme.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.