# Token ZLA

ZLA is the native fuel of the Zeltra network. Its role is analogous to that of ETH on Ethereum, BNB on Binance Smart Chain, etc.: it is used to pay the gas for each operation performed on the blockchain.

### Token Functions

**Gas.** Every operation on Zeltra—sending ZLA, calling smart contracts, deploying applications—consumes gas, which is paid for in ZLA. This mechanism ensures that the network cannot be saturated for free and that validators are compensated for their work.

**Validator compensation. 95%** of the fees for each block are directly allocated to the validator who generated it. This provides an economic incentive to maintain an active, honest, and available node.

**Partnership fund. 5%** of fees are automatically added to the Zeltra fund with each block. The more active the network, the larger this fund grows.

**Staking (future).** During the migration to Proof-of-Stake (PoS), ZLA will become the asset used to participate in block validation. Stakers will receive rewards proportional to their stake.

### Emission

ZLA does not have a fixed maximum supply. Like ETH, issuance is continuous and linked to block production. This model has proven successful on a large scale: the demand for tokens to pay network fees creates natural economic pressure that regulates the circulating supply.

A burn mechanism is introduced by governance to adjust monetary policy according to network activity.

{% hint style="info" %}
The power of the ZLA
{% endhint %}


---

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