# ASTRL token

$ASTRL is the official governance and yield bearing token of the Astrolescent project.

{% hint style="success" %}
Radix Babylon resource address

`resource_rdx1t4tjx4g3qzd98nayqxm7qdpj0a0u8ns6a0jrchq49dyfevgh6u0gj3`
{% endhint %}

**Please note:** to use the latest features of the Radix Babylon network, the original Olympia ASTRL token is undergoing a migration program. Go to <https://astrolescent> to quickly and for free upgrade your (old) $astrl tokens to the new $ASTRL tokens.&#x20;

The Olympia token can be recognized by the lowercase $astrl symbol and its resource address below.

{% hint style="danger" %}
Radix Olympia resource address

`resource_rdx1t5ga7j04ek4laprf7xryxlu4hl04373sskdaaptfnjhnsns98vma8m`
{% endhint %}

### Utility

#### Staking

All of the profits of Astrolescent will be used to buy back ASTRL and will be deposited into the staking contract. &#x20;

The expected staking APY based on 3 million staked ASTRL is 10% to 15% yearly.&#x20;

At the start of each quarter, an overview of all the earned fees and the direct operating cost of the previous quarter will be published. The profit share for ASTRL stakers will be converted to ASTRL via the Astrolescent aggregator (bought on the market) and distributed linearly over the 12 weeks of the new quarter at a random day and time each week to prevent gaming of the staking system. This should ensure tokens stay staked over a longer period.&#x20;

The distribution of the fees will start on January 1st, 2024, with the distribution of the fees earned in Q4 2023.&#x20;

#### Voting

ASTRL and sASTRL can both be used to vote on governance votes by the AstrolescentDAO.

### Tokenomics

ASTRL has a total of 36 million tokens, after burning 64 million tokens in early 2023.

| Destination                                                                                                                                           | Percentage | Amount     |
| ----------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | ---------- |
| [Community incentives and airdrops](https://dashboard.radixdlt.com/account/account_rdx16yz5f663lgzmef9p4ht6nu7aw4jza53lpgltrsa2hehyg7svllvc0a/tokens) | 75%        | 27 million |
| [Team](https://dashboard.radixdlt.com/account/account_rdx168zmr4v967a9n2pg6qkpce0njnvnfdd7lj8zxpuhpm3g3zmahm9kh0/tokens)                              | 19.4%      | 7 million  |
| [Marketing](https://dashboard.radixdlt.com/account/account_rdx16y6spuy7pvxj3v9ruezge6dvnvjkjja70wmv8fa4c73n4csl9p3pr5/tokens)                         | 5,6%       | 2 million  |

#### Distribution

**Airdrops**\
12,000,000 is reserved for monthly airdrops up to 100,000 ASTRL per month to incentivize the usage of Astrolescent products for 10 years.

2,000,000 ASTRL is reserved to refund lost tokens as a result of bugs and edge cases during the usage of Astrolescent products for up to $2000 per incident.

The additional supply of tokens will be used for special occasions.&#x20;

**Team**\
Up to 100,000 ASTRL will be distributed among the team members of Astrolescent each month for 6 years.

**Marketing**\
The 2,000,000 tokens will be used to run marketing campaigns

**Operating cost**\
The operating cost of Astrolescent will be funded from the revenue generated.

#### Locking

The tokens that are not needed during the present year will be locked with RadLock in October 2024.&#x20;

If vesting is available in time on RadLock a vesting schedule will be created to automatically unlock airdrop and team tokens each month. Otherwise, the tokens will be locked until October 2025 and relocked with a vesting schedule afterwards.


---

# 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.astrolescent.com/astrolescent-docs/tokens/tokenomics.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.