# Issuing Channels

Over time, we are expecting new ways to be issued to enhance the learning experience and to adapt to new things coming to the blockchain arena. The total amount of tokens (1 Billion) was designed for an estimated lifespan of about 10 years, but this could turn out to be or not issued (in its total) before that time frame.

Once that moment approaches, we hope to be ready to enable the community to decide on where it wants ATX to move towards. Either way, we will be here to support and contribute to such discussions.

Below you can find all issuing channels of ATX. If they are running or have been updated, paused or deactivated, these will show respectively next to them (check the legend below).

## Methods of Distribution - <mark style="color:purple;">ATX issuing ranges</mark>

* :gear: [HPUD Giveaway](/atexoras-atx/tokenomics/issuing-channels/hpud-giveaway.md) (depends on holding some kind of [NFTs](https://peakd.com/hpud/@forykw/powerup-delegation-giveaway-rules)) - <mark style="color:purple;">**1 to many ATX**</mark>
* ⏸ [Hive Pubs Community](/atexoras-atx/tokenomics/issuing-channels/hive-pubs-community.md) - <mark style="color:purple;">**50 or 10 ATX**</mark>
* :gear: [5 Years of Rewards Pool (ATX:SWAP.HIVE)](/atexoras-atx/tokenomics/issuing-channels/5-years-of-rewards-pool-atx-swap.hive.md) - <mark style="color:purple;">**Depends on the liquidity provided!**</mark>
* :gear: [The #BeerSaturday Challenge](/atexoras-atx/tokenomics/issuing-channels/the-beersaturday-challenge.md) - <mark style="color:purple;">**0.3 or 3 ATX**</mark>

#### Legend

* :gear: - Running
* ⏸ - Paused
* :lock: - Finished


---

# 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://atexoras-witness.gitbook.io/atexoras-atx/tokenomics/issuing-channels.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.
