> 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/usdaxgt-supply-history.md).

# $AXGT Supply History

This page documents the evolution of AXGT supply from the original token launch through permanent supply reductions and migration to the current AXGT (V2) contract.

### Supply Transition Summary

| Event              | AXGT          |
| ------------------ | ------------- |
| Original V1 Supply | 1,000,000,000 |
| Permanently Burned | 271,910,114   |
| Current V2 Supply  | 728,089,886   |

AXGT launched on February 13, 2024 with a maximum supply of 1,000,000,000 tokens under the AXGT (V1) contract.

Between 2024 and 2026, 271,910,114 AXGT were permanently removed from supply through on-chain burns, reducing the total supply by approximately 27%.

As part of the migration to AXGT (V2), the remaining 728,089,886 tokens became the fixed supply of the new contract.

### Contract History(including migration)

| Contract  | Address                                      | Status     |
| --------- | -------------------------------------------- | ---------- |
| AXGT (V1) | `0xDd66781D0E9a08D4FBb5eC7BAc80B691BE27F21D` | Deprecated |
| AXGT (V2) | `0x6112C3509A8a787df576028450FebB3786A2274d` | Active     |

The V2 contract was deployed as a 1:1 migration of the post-burn V1 supply. No additional tokens were created during migration.

The AXGT (V1) contract is no longer supported.

Historical Timeline

#### Phase 1: AXGT (V1) Launch

**February 13, 2024**

AXGT launched on Ethereum as the AxonDAO Governance Token with a maximum supply of **1,000,000,000 AXGT** under the original AXGT (V1) contract.

<table><thead><tr><th width="243">Contract</th><th>Address</th></tr></thead><tbody><tr><td>AXGT (V1)</td><td><code>0xDd66781D0E9a08D4FBb5eC7BAc80B691BE27F21D</code></td></tr></tbody></table>

#### Phase 2: Permanent Supply Reduction

**2024–2026**

During the V1 lifecycle, **271,910,114 AXGT** were permanently removed from circulation through on-chain burns.

| Metric             |             Amount |
| ------------------ | -----------------: |
| Original V1 Supply | 1,000,000,000 AXGT |
| Permanently Burned |   271,910,114 AXGT |
| Remaining Supply   |   728,089,886 AXGT |

This reduced the total supply by approximately <mark style="color:$success;">**27.19%**</mark><mark style="color:$success;">.</mark>

#### Phase 3: AXGT (V2) Migration

**January 2026**

AXGT migrated to a new Ethereum contract using a 1:1 replacement of the post-burn V1 supply.

A total of **728,089,886 AXGT** were minted once into the V2 contract, matching the remaining V1 supply after burns. No additional supply was created during migration.

<table><thead><tr><th width="146">Contract</th><th width="411">Address</th><th>Status</th></tr></thead><tbody><tr><td>AXGT (V1)</td><td><code>0xDd66781D0E9a08D4FBb5eC7BAc80B691BE27F21D</code></td><td>Deprecated</td></tr><tr><td>AXGT (V2)</td><td><code>0x6112C3509A8a787df576028450FebB3786A2274d</code></td><td>Active</td></tr></tbody></table>

#### Legacy Contracts

**As of January 1st 2026:** The following contracts are no longer supported and should not be used:

<table><thead><tr><th width="254">Network</th><th>Contract</th></tr></thead><tbody><tr><td>Ethereum (V1)</td><td><code>0xDd66781D0E9a08D4FBb5eC7BAc80B691BE27F21D</code></td></tr><tr><td>Base</td><td><code>0x9B700B043e9587ddE9a0c29A9483e2F8FA450d54</code></td></tr><tr><td>Arbitrum</td><td><code>0xE0Ee18EacAfDDAeb38f8907C74347C44385578aB</code></td></tr></tbody></table>

#### References

* V2 Contract Explorer: <https://etherscan.io/token/0x6112C3509A8a787df576028450FebB3786A2274d>
* Migration Status: <https://massdrop.multisender.app/airdrop/or2l8do1ka/details>

## PRESALE&#x20;

## Details

## **12% of AXGT Supply was SOLD During PRESALE**&#x20;

&#x20;**AXGT SOLD at Presale (12%)**

* **121M AXGT Total**: All in circulation.

| **Event**      | **Date Range**   | **AXGT Sold**              | **ETH**              |
| -------------- | ---------------- | -------------------------- | -------------------- |
| Manual Presale | 12/14-12/18 2023 | <kbd>14,056,049</kbd>      | <kbd>12.12</kbd>     |
| Pinksale       | 1/14-1/19 20204  | <kbd>37,230,069</kbd>      | <kbd>57.93</kbd>     |
| Fjord          | 1/30-2/4 2024    | <kbd>70,300,000</kbd>      | <kbd>51.35</kbd>     |
| **TOTAL**      | <p><br></p>      | <kbd>**121,586,118**</kbd> | <kbd>**121.4**</kbd> |

**AXGT Presale on Pinksale -** [**Link**](https://www.pinksale.finance/launchpad/0x7289c856a24139C9d99C137C36677549386BedF8?chain=ETH) **- Sale ended (1/20/24)**

{% embed url="<https://www.pinksale.finance/launchpad/ethereum/0x7289c856a24139C9d99C137C36677549386BedF8>" %}

**AXGT Presale on FjordFoundry -** [**Link**](https://app.fjordfoundry.com/token-sales/0xdDC85e7aA53589784A201a1fd9F1C3e17CE7D30a) **- Sale ended (2/4/24)**

{% embed url="<https://app.v2.fjordfoundry.com/pools/0xdDC85e7aA53589784A201a1fd9F1C3e17CE7D30a>" %}


---

# 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://whitepaper.axondao.io/axondao/usdaxgt-tokenomics/usdaxgt-supply-history.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.