> For the complete documentation index, see [llms.txt](https://whitepaper.axondao.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.axondao.io/axondao/usdaxgt-tokenomics.md).

# $AXGT Tokenomics

## AXGT Supply Overview

AXGT is designed to support governance, infrastructure funding, decentralized science incentives, and ecosystem coordination while maintaining a transparent and verifiable token supply model.

### Current Supply Metrics

Current supply metrics are available in real time at:

{% embed url="<https://axgt-supply.oci.axondao.io/>" %}

{% embed url="<https://axgt-supply.oci.axondao.io/og-image/summary.png?gb=202607>" %}

###

### Supply History

AXGT originally launched with a maximum supply of **1,000,000,000 tokens** under the AXGT (V1) contract.

Prior to migration, **271,909,430 AXGT** were permanently burned, resulting in a fixed AXGT (V2) supply of **728,089,886 tokens**.

### Supply Characteristics

* AXGT (V2) does not include a mint function.
* No additional AXGT can be created under the current contract.
* Supply can only decrease through token burns or future governance-approved contract upgrades.
* All supply metrics are publicly verifiable and tracked through the live supply dashboard.

### Contract Information

<table data-header-hidden><thead><tr><th width="265.25">Property</th><th>Value</th></tr></thead><tbody><tr><td>Network</td><td>Ethereum Mainnet</td></tr><tr><td>Token Symbol</td><td>AXGT</td></tr><tr><td>Status</td><td>Live</td></tr><tr><td>Contract Address</td><td><code>0x6112C3509A8a787df576028450FebB3786A2274d</code></td></tr></tbody></table>

### Trading AXGT

AXGT can currently be swapped on Ethereum Mainnet through Uniswap.

**AXGT Contract**

[`0x6112C3509A8a787df576028450FebB3786A2274d`](https://etherscan.io/token/0x6112c3509a8a787df576028450febb3786a2274d)

**Uniswap Pair**

[`0xf9c56A9CcC1398Bed3C519ef2F0B42CE52AaA440`](https://etherscan.io/address/0xf9c56A9CcC1398Bed3C519ef2F0B42CE52AaA440)

### Network Support & Security

AXGT exists exclusively on Ethereum Mainnet.

AxonDAO does not currently support:

* Bridging
* Wrapped or mirrored AXGT
* No Base AXGT
* No Arbitrum AXGT

Always verify the AXGT contract address before swapping or interacting with the token:

`0x6112C3509A8a787df576028450FebB3786A2274d`

Any token claiming to represent AXGT on another network is not an official AxonDAO deployment. \
\
If needing to do migration your old tokens to the current contract; reference this tweet from the official AxonDao X profile. Email <admin@axondao.io> if you have issues no one from the team will DM you first.

{% embed url="<https://x.com/axondao/status/2006737346377515285?s=46&t=uad_RD_8kcXghcCYcd4lkQ>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://whitepaper.axondao.io/axondao/usdaxgt-tokenomics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.