> For the complete documentation index, see [llms.txt](https://docs.awenetwork.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.awenetwork.ai/technical/stpt-to-awe-token-migration-guide.md).

# STPT to AWE Token Migration Guide

## STPT → AWE Migration

> **Migration closes September 21, 2026.** After the deadline, STPT will no longer be eligible to migrate to AWE.

The official migration converts **STPT on Ethereum to AWE on Base at a 1:1 ratio**.

### Before you begin

* Use only the [official migration portal](https://upgrade.stp.network/).
* Confirm that your STPT is on Ethereum.
* Keep enough ETH in your wallet for network fees.
* Never send tokens directly to a migration or token contract.
* AWE contributors will never ask for your seed phrase or private key.

### How to migrate

1. Open the [official migration portal](https://upgrade.stp.network/).
2. Connect the wallet holding your STPT on Ethereum.
3. Enter the amount you want to migrate.
4. Approve and confirm the migration transaction.
5. Wait for the deposit to be verified.
6. Switch your wallet to Base when prompted.
7. Claim the corresponding AWE.

**1 STPT on Ethereum = 1 AWE on Base**

### If your STPT is on Base

There is no direct STPT-on-Base to AWE conversion.

You must first bridge STPT from Base back to Ethereum and then complete the migration process above. Bridging may take up to seven days, so begin before the deadline.

### If your STPT is on an exchange

The original exchange migration period has ended. Check the exchange’s current support policy directly. Do not assume that new STPT deposits will be converted automatically.

### Stay safe

Use only links published through AWE’s official website and social channels. There is no private or support-assisted migration process.


---

# 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://docs.awenetwork.ai/technical/stpt-to-awe-token-migration-guide.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.