# Token Migration Policy

Version: 1.1

Effective Date: April 20, 2026

Last Update:  April 27, 2026

***

**1. Purpose and Scope**

This Token Migration Policy (“Policy”) governs the migration of AITECH tokens to ACN within the AITECH ecosystem (“Migration”).

This Policy is issued by Solidus AI Tech Inc. as part of the AITECH Cloud Network (ACN) group structure, which includes AITECH Cloud Network Foundation and affiliated entities supporting ecosystem strategy, technology operations, and related functions.

This Policy forms an integral part of, and must be read together with, the Company’s Terms and Conditions. In the event of conflict, the Terms and Conditions shall prevail unless expressly stated otherwise.

***

**2. Nature of the Migration**

The Migration is a technical token transition mechanism within the ecosystem and does not constitute:

* An offer, solicitation, or invitation to invest;
* A financial instrument, security, or regulated product;
* Any guarantee of value, liquidity, or future utility.

***

**3. Migration Window (Strict Time Limitation)**

The Migration is available strictly for a period of seven (7) calendar days and 7 days extension from the officially announced start date (“Migration Window”).

* The Company shall determine and publish the Migration Window;
* Users must complete all required steps within this period.

***

**4. Expiry and Irrevocable Forfeiture**

Failure to complete the Migration within the Migration Window shall result in:

* Automatic and permanent expiration of the User’s right to migrate; and
* Irrevocable forfeiture of any entitlement to convert AITECH into ACN.

To the maximum extent permitted by applicable law:

* No extensions, exceptions, reversals, reissuances, or compensation shall be provided.

***

**5. No Extensions, Exceptions, or Obligations to Remind**

* No extensions, grace periods, or exceptions shall be granted under any circumstances.
* The Company has no obligation to provide reminders, follow-ups, or individual notifications regarding the Migration Window.
* Users are solely responsible for monitoring official communications and deadlines.

***

**6. Mandatory User Acknowledgment (Clickwrap Consent)**

Access to the Migration process is conditional upon the User providing explicit and informed consent via a mandatory acknowledgment mechanism (e.g., checkbox + “Accept”).

By accepting, the User:

* Confirms understanding of the 7-day limitation;
* Accepts the risk of permanent loss of migration rights;
* Agrees to be legally bound by this Policy.

The Company may maintain electronic records of such acceptance, which shall constitute valid and binding evidence of consent.

***

&#x20;

**7. Eligibility**

Users must:

* Have full control and access to a compatible digital wallet;
* Comply with applicable Terms and Conditions and policies;
* Not be subject to sanctions, restrictions, or prohibited jurisdiction limitations.

***

**8. Migration Process**

To complete the Migration, Users must:

1. Access the official migration interface;
2. Connect a compatible wallet;
3. Follow all technical instructions;
4. Confirm and execute required blockchain transactions.

Certain technical, operational, customer support, platform management, infrastructure, security, transaction monitoring, communications, recordkeeping, troubleshooting, or other functions relating to the Migration may be performed, coordinated, or supported by relevant entities, internal divisions, affiliated companies, contractors, or authorized third-party service providers within or engaged by the AITECH Cloud Network (ACN) group, where reasonably necessary to facilitate the Migration process, maintain service continuity, manage operational risk, or comply with applicable legal and regulatory obligations.

All network fees (gas fees) and transaction costs are the sole responsibility of the User.

***

**9. User Responsibilities**

Users are solely responsible for:

* Ensuring correct wallet addresses and blockchain network selection;
* Using compatible wallets and platforms;
* Safeguarding private keys and credentials;
* Completing all steps within the Migration Window.

Any errors may result in permanent and irreversible loss of tokens.

***

**10. Risk Disclosure**

Users acknowledge and accept all risks associated with the Migration, including but not limited to:

* Incorrect wallet addresses or unsupported networks;
* Smart contract interaction errors;
* Blockchain congestion, delays, or failures;
* Loss or compromise of private keys;
* Platform downtime or technical limitations;
* Third-party service failures.

Digital assets involve inherent technical and operational risks, and outcomes cannot be guaranteed.

***

**11. Third-Party Dependencies**

The Migration may rely on third-party infrastructure, including:

* Blockchain networks
* Wallet providers
* Exchanges or custodians

The Company:

* Does not control such third parties; and
* Shall not be liable for any losses, delays, or failures arising from them.

The Migration may also rely on affiliated entities, technology operators, and authorized service providers within the AITECH Cloud Network (ACN) group.

***

&#x20;

**12. Finality and Irreversibility**

All Migration transactions are:

* Final
* Irreversible
* Non-cancellable

Once executed, no corrections, reversals, or refunds shall be possible.

***

&#x20;

**13. Limitation of Liability**

To the maximum extent permitted by applicable law, the Company shall not be liable for:

* Loss of tokens due to missed deadlines;
* User errors (including incorrect wallet details);
* Third-party failures or blockchain issues;
* Any indirect, incidental, or consequential damages.

Unless expressly stated otherwise, references to the group structure do not create joint, several, or collective liability among all affiliated entities solely by reason of common ownership, branding, or association.

***

**14. Indemnification**

The User agrees to indemnify and hold harmless the Company from any claims, losses, or damages arising from:

* Breach of this Policy;
* Misuse of the Migration process;
* Violation of applicable laws or third-party rights.

***

**15. No Financial Advice**

Nothing in this Policy constitutes:

* Financial, investment, legal, or tax advice;
* A recommendation or endorsement of any crypto-asset.

***

**16. Regulatory Position**

The Migration is intended solely as a technical ecosystem process and shall not be interpreted as:

* A public offering or exchange offer;
* A regulated activity under securities or financial services laws, to the extent permitted by applicable law.

***

**17. Amendments**

The Company reserves the right to modify this Policy at any time.

* Updates shall be effective upon publication or stated effective date;
* Continued participation constitutes acceptance of the updated Policy.

***

**18. Governing Law and Jurisdiction**

This Policy shall be governed by the laws of the United Kingdom.

Any disputes shall be resolved in the courts of that jurisdiction, unless otherwise required by applicable law.

***

&#x20;

**19. Entire Understanding**

This Policy constitutes the complete understanding regarding the Migration and supplements the Terms and Conditions.

***

### 20. Contact Information

If you have any questions or concerns regarding this Token Migration Policy, contact us at:\
\
Email:             <admin@aitech.io>

Mailing Address:        SOLIDUS AI TECH INC, PH The Century Tower, Office 317 Vía Ricardo J. Alfaro Corregimiento de Betania, Distrito de Panamá, Panama City, Panama.

&#x20;

<br>


---

# 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://whitepaper.aitech.io/regulatory-and-compliance/token-migration-policy.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.
