# Migration to Mainnet

Generally, token distribution plans include various distribution modes to launch the issuer’s mainnet. Instead of factoring all the complexity into the genesis block of a mainnet, Polimec allows this to be set in the contribution token phase to be later migrated to its mainnet. Designing and integrating such complexity directly into the contribution tokens generates trust and transparency.

On Polimec, the instance-ID of the contribution token and all contribution token balances are migrated to the new mainnet leveraging XCM to ensure that assets are not lost or duplicated across multiple chains.

*Contribution token issuance and mainnet migration:*

<figure><img src="/files/2Sd6RAUKYoIdQv8NZl4G" alt=""><figcaption></figcaption></figure>

Furthermore, the token distribution process can implement particular balances owned by the issuer or under the control of trusted entities. They can serve as a contribution token reserve for the team, early participants, a foundation, or bounty programs. These accounts are maintained directly by the issuer without any funding token equivalent being transferred. This functionality increases transparency in funding rounds as it shows the exact amount of issued tokens and stores corresponding transaction data on-chain[^1].

Today, projects more frequently explore other designs for token distributions with growing popularity. Airdrops of different forms have gained prominence, especially by allocating tokens to target user groups based on network contribution or interest to bootstrap a network at launch. This proved effective in raising awareness and distributing tokens widely if structured correctly. In particular, such an approach may be appropriate for projects aiming to distribute tokens and incentivize participation amongst a specific audience of potential users that have funding support for network development through other means. Airdrops represent a functionality of Polimec as they support the creation of a user base for the contribution token. Issuers can manage airdrops by engaging with their community to request their Polimec addresses and valid on-chain verification for [sybil attack protection](#user-content-fn-2)[^2].

<br>

[^1]: Activities, transactions, or data that are recorded directly on the blockchain.

[^2]: Strategies and mechanisms designed to safeguard decentralized and distributed systems from security threats posed by malicious users creating multiple fake identities or nodes to manipulate or control the network.


---

# 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://hub.polimec.org/learn/funding-process/migration-to-mainnet.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.