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

# Staking

### **Overview**

Delegate $ASTER to Aster Chain validators and earn rewards.

When staking, users make two key choices:

* Select a validator 
* Choose a lock period

These two choices determine how rewards are generated and distributed.

The basic staking flow can be summarized as:

Select a validator → Stake $ASTER → Choose a lock period → Earn epoch rewards

### **What is a Validator?**

A validator is responsible for processing transactions and producing blocks on Aster Chain.

When users stake $ASTER, they delegate their tokens to a validator. Each validator contributes differently to the network, and this performance determines the validator's total rewards.

Once the rewards are received, they are shared proportionally among delegators after deducting the validator's commission.

This design ensures validators compete based on real network contribution rather than simply attracting large amounts of stake.

### **What is the Lock Period?**

The lock period is the duration where the staked $ASTER cannot be withdrawn without penalty. It determines your Loyalty Rewards weight, and a longer lock period means greater reward weight.

The current **maximum lock duration is 208 weeks (approximately 4 years).**

### **Dual Reward Structure**

Aster Chain staking distributes rewards through two distinct layers.

<table data-header-hidden><thead><tr><th width="180.24609375"></th><th width="357.06640625"></th><th></th></tr></thead><tbody><tr><td><strong>Reward Layer</strong></td><td><strong>Determined By</strong></td><td><strong>Weekly Reward Pool</strong></td></tr><tr><td>Base APY</td><td>Validator transaction share and your delegation size</td><td>150,000 $ASTER</td></tr><tr><td>Loyalty Rewards</td><td>Lock duration and trading activity</td><td>300,000 $ASTER+ Fee Buyback rewards (variable)</td></tr></tbody></table>

Separating these two reward streams serves two goals:

* Encouraging healthy competition between validators&#x20;
* Incentivizing long-term staking commitment&#x20;

**New as of June 17, 2026:** Loyalty Rewards now include a variable component on top of the 300,000 $ASTER base. Each epoch, all $ASTER bought back from platform fees is added to the Loyalty Rewards pool and distributed to veASTER holders by lock weight. Permissionless Spot listing fees fund a further buyback into staking rewards on a separate schedule. See Protocol Fee Rewards below for details.

#### **Protocol Fee Rewards**&#x20;

As part of Aster's tokenomics upgrade, 99% of daily platform fees are automatically used to buy back $ASTER via TWAP. All bought-back $ASTER is distributed to veASTER stakers — on top of the 300,000 $ASTER base Loyalty Rewards each epoch.

This means your staking rewards scale directly with Aster's trading activity.

**How it works:**

1. 99% of daily platform fees flow into the buyback wallet (0xa0edBaBcb48034e368de286b49F9603C7AfA1b60)
2. Buybacks execute via TWAP across each day and settle on-chain
3. Each epoch, the total buyback amount is added to the Loyalty Rewards pool and distributed to veASTER holders by lock weight
4. For every $ASTER bought back, an equal amount is burned from reserve — burns execute bi-weekly and continue until total supply reaches 3,000,000,000

#### Spot Listing Fees:

Each permissionless Spot listing incurs a 50,000 USDT fee, which is also used to buy back $ASTER as additional staking rewards. Listing fees are collected weekly and enter the buyback the following week, with staking rewards from this portion taking effect two weeks after listing.

* Listing fee wallet: 0x39C473f4420e4ae9Ab3fe9e7ceDFc08F9684bB1a

### **Key Terms**

<table data-header-hidden><thead><tr><th width="186.45703125"></th><th></th></tr></thead><tbody><tr><td><strong>Term</strong></td><td><strong>Description</strong></td></tr><tr><td>$ASTER</td><td>Native token used for staking, rewards, and governance</td></tr><tr><td>Validator</td><td>Validator receiving delegated stake</td></tr><tr><td>Delegation</td><td>Relationship between user and validator</td></tr><tr><td>Lock Position</td><td>The staking position tied to a lock duration</td></tr><tr><td>Epoch</td><td>Reward settlement cycle (currently weekly)</td></tr><tr><td>Base APY</td><td>Yield derived from validator performance</td></tr><tr><td>Loyalty Rewards</td><td>Additional yield based on long-term lock commitment, including fee buyback rewards</td></tr><tr><td>veASTER</td><td>Weight metric derived from locked ASTER and lock duration</td></tr><tr><td>Power</td><td>Loyalty reward weight calculated from veASTER and Trading Volume Boost</td></tr><tr><td>Total Power</td><td>Combined Power of all users in a given Epoch</td></tr><tr><td>Penalty</td><td>Penalty applied for exiting before the lock period ends</td></tr></tbody></table>

<br>


---

# 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://docs.asterdex.com/aster-chain/staking.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.