# Migration Guide

With the official launch of House Party Protocol (HPP), all AERGO and AQT tokens will be fully migrated to the new HPP token. This guide outlines the migration process for all AERGO token holders.

* Migrating from AERGO and AQT to HPP is mandatory.
* If your AERGO and AQT tokens are stored on a centralized exchange (CEX) that supports HPP, the swap will be processed automatically.
* If you hold tokens in a personal wallet such as MetaMask or Aergo Connect, you must follow the manual migration steps below.
* When migrating AQT, fractional amounts cannot be swapped, and only whole numbers are allowed.&#x20;
* Only AQT (ERC-20) tokens can be migrated. Tokens on BNB Chain must first be transferred via the Alpha Quark bridge.<br>

HPP tokens will exist in three multi-chain formats, each with its own network and specific purpose:

| **Layer**        | **Network**                           | **Token Name**        | **Role & Functionality**                                                                                                  |
| ---------------- | ------------------------------------- | --------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| Execution Layer  | HPP Mainnet (Arbitrum Orbit-based L2) | HPP (Mainnet ERC-20)  | Main execution environment for AI computation, smart contract execution, and governance. All CEX/DEX listings occur here. |
| Settlement Layer | Ethereum (L1)                         | HPP (Ethereum ERC-20) | Backup asset for enhanced security and settlement.                                                                        |
| Legacy Layer     | HPP (AERGO Mainnet)                   | HPP (AERGO Mainnet)   | Maintains existing Aergo-based integrations with enterprises and government agencies.                                     |

### How to Migrate Based on Where You Store Tokens:

| **Where Your AERGO Is Stored**            | **Do You Need to Migrate?** | **What to Do**                                                                                                   |
| ----------------------------------------- | --------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| On a supported centralized exchange (CEX) | ❌ No                        | No action needed. The exchange will handle the swap automatically. Check the official announcements for details. |
| In MetaMask as AERGO (ERC-20)             | ✅ Yes                       | Follow the self-migration steps outlined below.                                                                  |
| In Aergo Connect as AERGO (Native)        | ✅ Yes                       | Follow the self-migration steps outlined below.                                                                  |

### 1. If held in a supported CEX:

If your AERGO tokens are stored in an exchange that officially supports HPP migration, they will be automatically swapped to HPP tokens without any action on your part.

* All swaps are conducted at a 1:1 ratio.
* No additional steps are required from the user.
* Exchange-specific timelines will be announced individually by each exchange.

### 2. If held in a wallet (Metamask, Aergo Connect, etc.):

Step 1: Migrate AERGO (ERC-20) or (Native) → HPP (Ethereum ERC-20)

* Go to the AERGO Bridge & HPP Migration Portal. (The site will be updated in time for the official migration launch. Currently, only the AERGO Bridge is available.)
* Follow the on-screen instructions to connect your wallet and start the migration.
* AERGO (ERC-20): Converted immediately.
* AERGO (Native): Converted within 24 hours.

Step 2: Bridge HPP (Ethereum ERC-20) → HPP (Mainnet ERC-20)

* Access the official HPP Bridge link (to be provided later).
* Bridge HPP (Ethereum ERC-20) to HPP (Mainnet ERC-20).
* Funds will be deposited within approximately 5 minutes after bridging.

⚠️ HPP (Mainnet ERC-20) uses ETH for gas fees. Make sure you have some ETH in your wallet before sending HPP.

### Token Swap Portal Opening & Related Notice

The Token Swap Portal will open on August 18, 2025. However, the migration and bridge functions will be provided in line with the official support schedule. After the official support date, users will be able to access the portal and swap their tokens at any time.&#x20;

In the initial phase, we will focus on stabilizing the token swap process and exchange listings, making every effort to ensure HPP is listed on all exchanges where AERGO was previously traded. Liquidity on DEXs will be introduced gradually, with availability expanding step-by-step.

### 🔗 Important Links

* HPP Token Swap Portal:[ https://portal.hpp.io/<br>](https://portal.hpp.io/)(Will be activated on August 18, 2025, alongside the website update. Migration functionality will go live with official support.)
* HPP Mainnet Bridge:[ https://portal.hpp.io/bridge<br>](https://portal.hpp.io/bridge)(Will be activated on August 18, 2025.)
* AQT Holder Migration Guide: TBD
* Exchange-specific announcements: TBD

### ❓ Questions or Support

If you have any questions about the token swap, rebranding, or HPP in general, feel free to reach out via email or our official Telegram channel:

* Email: <hello@hpp.io>
* Telegram:[ https://t.me/aergoofficial\ <br>](https://t.me/aergoofficial)


---

# 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.hpp.io/community-1/migration-guide-1.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.