# Governance

## **Overview**

Listing Vote is a permissionless listing mechanism on Aster Chain. Any active validator can propose a new listing, and proposals are decided by on-chain vote weighted by staked $ASTER.

This process ensures that listing decisions are transparent, on-chain verifiable, and governed by the validators that secure the network.

***

### **How It Works**

* A Validator proposes a new listing (e.g. BTC/U as a perp pair).
* All active validators vote: **Approved / Rejected / Not Voted (Abstain)**
* Votes are weighted by each validator's **currently active staked $ASTER**
* A proposal passes only if **both** of the following conditions are met:
* Approve **stake > 50%** of total active stake
* Approve validator **count > 50%** of total active validators

Pending stakes and in-progress withdrawals are **not counted** toward vote weight. Validators in **inactive** status cannot vote and are not counted in the totals.

### **Eligibility**

To become an active validator on Aster Chain and participate in Listing Vote:&#x20;

\- Stake a minimum of \*\*20M $ASTER\*\*&#x20;

\- Maintain active validator status

### **Voting Rules**

| Parameter         | Value                                                                                                      |
| ----------------- | ---------------------------------------------------------------------------------------------------------- |
| Who can vote      | Active Validator nodes                                                                                     |
| Vote options      | Approved / Rejected / Not Voted (Abstain)                                                                  |
| Vote weight       | Proportional to active staked $ASTER                                                                       |
| Passing threshold | Approve stake > 50% of total active stake **AND** Approve validator count > 50% of total active validators |

***

### **Voting Lifecycle**

Proposed → Voting → Approved / Rejected

* **Voting** — The proposal is open. Validators cast their votes. Results update in real-time.
* **Approved** — Both stake and validator count thresholds are met; the token will be listed.
* **Rejected** — Either threshold failed.

***

### **For Validators**

If you are an active validator on Aster Chain, you can:

* Propose new listings
* Vote on any active listing proposal: Approve, Reject, or stay as Not Voted
* Votes are recorded on-chain

***

### **FAQ**

**Q: How is the vote result calculated?**

A: A proposal passes only when **both** the Approve stake exceeds 50% of total active stake and the Approve validator count exceeds 50% of total active validators.

**Q: Does every node have the same vote weight?**

A: No. Stake-side weight is proportional to each validator's active staked $ASTER. More stake means more influence. The validator-count threshold treats every active validatorequally (one validator = one count).

**Q: What counts as "active stake"?**

A: Only currently effective staked $ASTER. Pending stakes and in-progress withdrawals are excluded.

**Q: Can inactive validators vote?**

A: No. Validators in inactive status cannot vote.

**Q: Who can propose a new listing?**

A: Any active validator node can propose a new token listing.

**Q: How do I become a validator?**

**A: Stake a minimum of 20M $ASTER and maintain active validator status.**&#x20;

<br>


---

# 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.asterdex.com/aster-chain/governance.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.
