<?xml version="1.0" encoding="UTF-8"?>
<html    xmlns:mica="https://www.esma.europa.eu/taxonomy/2025-03-31/mica/"
   xmlns:gen="http://xbrl.org/2008/generic"
   xmlns:lei-fn="http://www.xbrl.org/taxonomy/int/lei/2020-07-02/functions"
   xmlns:xbrldt="http://xbrl.org/2005/xbrldt"
   xmlns:variable="http://xbrl.org/2008/variable"
   xmlns:xl="http://www.xbrl.org/2003/XLink"
   xmlns:lei="http://www.xbrl.org/taxonomy/int/lei/2020-07-02"
   xmlns:cf="http://xbrl.org/2008/filter/concept"
   xmlns:valm="http://xbrl.org/2010/message/validation"
   xmlns:link="http://www.xbrl.org/2003/linkbase"
   xmlns:enum2="http://xbrl.org/2020/extensible-enumerations-2.0"
   xmlns:xlink="http://www.w3.org/1999/xlink"
   xmlns:validation="http://xbrl.org/2008/validation"
   xmlns:dtr-types_2="http://www.xbrl.org/dtr/type/2022-03-31"
   xmlns:dtr-types="http://www.xbrl.org/dtr/type/2020-01-21"
   xmlns:iso4217="http://www.xbrl.org/2003/iso4217"
   xmlns:msg="http://xbrl.org/2010/message"
   xmlns:va="http://xbrl.org/2008/assertion/value"
   xmlns:cfi="http://xbrl.org/2010/custom-function"
   xmlns:label="http://xbrl.org/2008/label"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xmlns:ef="http://xbrl.org/2008/filter/entity"
   xmlns:xbrli="http://www.xbrl.org/2003/instance"
   xmlns="http://www.w3.org/1999/xhtml"
   xmlns:ix="http://www.xbrl.org/2013/inlineXBRL"
   xmlns:ixt="http://www.xbrl.org/inlineXBRL/transformation/2011-07-31"
   xmlns:negated="http://www.xbrl.org/2009/role/negated"
   xmlns:net="http://www.xbrl.org/2009/role/net"
   xmlns:nonnum="http://www.xbrl.org/dtr/type/non-numeric"
   xmlns:num="http://www.xbrl.org/dtr/type/numeric"
   xmlns:xbrldi="http://xbrl.org/2006/xbrldi"
   xmlns:xsd="http://www.w3.org/2001/XMLSchema"
   xsi:schemaLocation="http://xbrl.org/2006/xbrldi http://www.xbrl.org/2006/xbrldi-2006.xsd
                       http://www.xbrl.org/2003/instance http://www.xbrl.org/2003/xbrl-instance-2003-12-31.xsd"
>
<head>
   <title>iXBRL report for the MICA taxonomy</title>
   <script type="text/javascript" src="http://www.xbrl.org/ixbrl-samples/es6-shim.js"></script>
   <script type="text/javascript" src="https://code.jquery.com/jquery-1.12.0.min.js" ></script>
   <script type="text/javascript" src="https://cdn.jsdelivr.net/interact.js/1.2.6/interact.min.js" ></script>
   <script type="text/javascript" src="http://www.xbrl.org/ixbrl-samples/ixbrl-inspector.js"></script>

    <style type="text/css">
      td,tr,h1,h2,h3{
    font-family:calibri,sans-serif;
    font-size:16px;
    color:#000000;
    background-color:#FFFFFF;
    border-width:thin;
    vertical-align:bottom;
    text-align:left;
    border-left-color:black;
    border-right-color:black;
    border-top-color:black;
    border-bottom-color:black;
}

td{
    border-left-style:solid;
    border-right-style:solid;
    border-top-style:solid;
    border-bottom-style:solid;
}
    </style>
</head>
<body>

        <div style="display:none">
          <ix:header>
            <ix:references>
              <link:schemaRef xlink:type="simple"  xlink:href="https://www.esma.europa.eu/taxonomy/mica/2025-03-31/mica_entry_table_2.xsd"/>
            </ix:references>
            <ix:resources>
        <xbrli:context id="_ctx1">
            <xbrli:entity>
                <xbrli:identifier scheme="http://standards.iso.org/iso/17442">254900RNIRZ1EOPDO568</xbrli:identifier>
            </xbrli:entity>
            <xbrli:period>
                <xbrli:startDate>2026-01-01</xbrli:startDate>
                <xbrli:endDate>2026-12-31</xbrli:endDate>
            </xbrli:period>
        </xbrli:context></ix:resources>
          </ix:header>
        </div>
<div class="toc">
<h2>Table of Contents</h2>
<div class="toc-item"><a href="#General_Information">General Information</a></div>
<div class="toc-item"><a href="#SUMMARY">SUMMARY</a></div>
<div class="toc-item"><a href="#Part_A_-_Information_about_the_Offeror_or_the_Person_Seeking_Admission_to_Trading">Part A - Information about the Offeror or the Person Seeking Admission to Trading</a></div>
<div class="toc-item"><a href="#Part_B_-_Information_about_the_Issuer,_If_Different_from_the_Offeror_or_Person_Seeking_Admission_to_Trading">Part B - Information about the Issuer, If Different from the Offeror or Person Seeking Admission to Trading</a></div>
<div class="toc-item"><a href="#Part_C_-_Information_about_the_Operator_of_the_Trading_Platform">Part C - Information about the Operator of the Trading Platform</a></div>
<div class="toc-item"><a href="#Part_D_-_Information_about_the_Crypto-Asset_Project">Part D - Information about the Crypto-Asset Project</a></div>
<div class="toc-item"><a href="#Part_E_-_Information_about_the_Offer_to_the_Public_of_Crypto-Assets_or_their_Admission_to_Trading">Part E - Information about the Offer to the Public of Crypto-Assets or their Admission to Trading</a></div>
<div class="toc-item"><a href="#Part_F_-_Information_about_the_Crypto-Assets">Part F - Information about the Crypto-Assets</a></div>
<div class="toc-item"><a href="#Part_G_-_Information_on_the_Rights_and_Obligations_attached_to_the_Crypto-Assets">Part G - Information on the Rights and Obligations attached to the Crypto-Assets</a></div>
<div class="toc-item"><a href="#Part_H_-_Information_on_the_underlying_technology">Part H - Information on the underlying technology</a></div>
<div class="toc-item"><a href="#Part_I_-_Information_on_Risks">Part I - Information on Risks</a></div>
<div class="toc-item"><a href="#Part_J_–_Information_on_the_sustainability_indicators_in_relation_to_adverse_impact_on_the_climate_and_other_environment-related_adverse_impacts">Part J – Information on the sustainability indicators in relation to adverse impact on the climate and other environment-related adverse impacts</a></div>
</div>
<table style="margin:0px auto; border:0px; width:80%;" cellspacing="0">
<tr><td colspan="2" style="color:#FFF;height:20px;border-width:0;"/></tr>
<tr><td colspan="2" style="text-align:center;background-color:#0066DF;color:white;font-weight:bold;padding:10px;"><a id="General_Information">General Information</a></td></tr>
<tr>
<td style="background-color:#92D050; width:30%;">00: Table of content</td>
<td id="_TEMPLATE_id_00" style="color:#0066DF;"><ix:nonNumeric name="mica:TableOfContentForOtherTokenWhitePaper" contextRef="_ctx1" id="TEMPLATE_id_00" escape="false"><div style="color:#0066DF;">true</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">01: Date of notification</td>
<td id="_TEMPLATE_id_01" style="color:#0066DF;"><ix:nonNumeric name="mica:DateOfNotificationForOtherTokenWhitePaper" contextRef="_ctx1" id="TEMPLATE_id_01" escape="false"><div style="color:#0066DF;"><p>2026-01-21</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">02: Statement in accordance with Article 6(3) of Regulation (EU) 2023/1114</td>
<td id="_TEMPLATE_id_02" style="color:#0066DF;"><ix:nonNumeric name="mica:StatementEnsuringComplianceWithUnderlyingRegulation" contextRef="_ctx1" id="TEMPLATE_id_02" escape="false"><div style="color:#0066DF;"><p>This crypto-asset white paper has not been approved by any competent authority in any Member State of the European Union. The person seeking admission to trading of the crypto-asset is solely responsible for the content of this crypto-asset white paper.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">03: Compliance statement in accordance with Article 6(6) of Regulation (EU) 2023/1114</td>
<td id="_TEMPLATE_id_03" style="color:#0066DF;"><ix:nonNumeric name="mica:ComplianceStatementAboutManagementConfirmation" contextRef="_ctx1" id="TEMPLATE_id_03" escape="false"><div style="color:#0066DF;"><p>This crypto-asset white paper complies with Title II of Regulation (EU) 2023/1114 of the European Parliament and of the Council and, to the best of the knowledge of the management body, the information presented in the crypto-asset white paper is fair, clear and not misleading and the crypto-asset white paper makes no omission likely to affect its import.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">04: Statement in accordance with Article 6(5), points (a), (b), (c), of Regulation (EU) 2023/1114</td>
<td id="_TEMPLATE_id_04" style="color:#0066DF;"><ix:nonNumeric name="mica:StatementAboutPotentialRisks" contextRef="_ctx1" id="TEMPLATE_id_04" escape="false"><div style="color:#0066DF;"><p>The crypto-asset referred to in this crypto-asset white paper may lose its value in part or in full, may not always be transferable and may not be liquid.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">05: Statement in accordance with Article 6(5), point (d), of Regulation (EU) 2023/1114</td>
<td id="_TEMPLATE_id_05" style="color:#0066DF;"><ix:nonNumeric name="mica:StatementAboutExchangeabilityForOtherToken" contextRef="_ctx1" id="TEMPLATE_id_05" escape="false"><div style="color:#0066DF;"><p>False</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">06: Statement in accordance with Article 6(5), points (e) and (f), of Regulation (EU) 2023/1114</td>
<td id="_TEMPLATE_id_06" style="color:#0066DF;"><ix:nonNumeric name="mica:StatementAboutCompensationAndGuaranteeForOtherToken" contextRef="_ctx1" id="TEMPLATE_id_06" escape="false"><div style="color:#0066DF;"><p>The crypto-asset referred to in this white paper is not covered by the investor compensation schemes under Directive 97/9/EC of the European Parliament and of the Council or the deposit guarantee schemes under Directive 2014/49/EU of the European Parliament and of the Council.</p>
</div></ix:nonNumeric></td>
</tr>
<tr><td colspan="2" style="color:#FFF;height:20px;border-width:0;"/></tr>
<tr><td colspan="2" style="text-align:center;background-color:#0066DF;color:white;font-weight:bold;padding:10px;"><a id="SUMMARY">SUMMARY</a></td></tr>
<tr>
<td style="background-color:#92D050; width:30%;">07: Warning in accordance with Article 6(7), second subparagraph, of Regulation (EU) 2023/1114</td>
<td id="_TEMPLATE_id_07" style="color:#0066DF;"><ix:nonNumeric name="mica:ClarificationRegardingOtherTokenOfferTerms" contextRef="_ctx1" id="TEMPLATE_id_07" escape="false"><div style="color:#0066DF;"><p>Warning</p>
<p>This summary should be read as an introduction to the crypto-asset white paper. The prospective holder should base any decision to purchase this crypto-asset on the content of the crypto-asset white paper as a whole and not on the summary alone. The offer to the public of this crypto-asset does not constitute an offer or solicitation to purchase financial instruments and any such offer or solicitation can be made only by means of a prospectus or other offer documents pursuant to the applicable national law. This crypto-asset white paper does not constitute a prospectus as referred to in Regulation (EU) 2017/1129 of the European Parliament and of the Council or any other offer document pursuant to Union or national law.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">08: Characteristics of the crypto-asset</td>
<td id="_TEMPLATE_id_08" style="color:#0066DF;"><ix:nonNumeric name="mica:DescriptionOfCharacteristicsOfOtherTokenExplanatory" contextRef="_ctx1" id="TEMPLATE_id_08" escape="false"><div style="color:#0066DF;"><p>$CHIP is the governance token of the USD.AI protocol, enabling on-chain participation in protocol decision-making and risk management through voting on upgrades and key system parameters. Mere ownership or holding of $CHIP does not involve staking and does not by itself provide loss-protection or insurance functionality. Staking $CHIP is a separate, optional protocol feature that users may choose to participate in within designated insurance modules to support loss-protection mechanisms. The token is designed to align participant incentives and support the secure operation of the protocol and does not confer equity, dividend, or profit rights.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">09: Further information about utility tokens</td>
<td id="_TEMPLATE_id_09" style="color:#0066DF;"><ix:nonNumeric name="mica:DescriptionOfFurtherInformationAboutUtilityTokensExplanatory" contextRef="_ctx1" id="TEMPLATE_id_09" escape="false"><div style="color:#0066DF;"><p>Not applicable as CHIP is not a utility token as defined under MiCA.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">10: Key information about the offer to the public or admission to trading</td>
<td id="_TEMPLATE_id_10" style="color:#0066DF;"><ix:nonNumeric name="mica:OfferDescriptionExplanatory" contextRef="_ctx1" id="TEMPLATE_id_10" escape="false"><div style="color:#0066DF;"><p>This white paper has been prepared for the purposes of seeking admission to trading on the crypto-asset trading platform operated by Coinbase Luxembourg S.A.</p>
</div></ix:nonNumeric></td>
</tr>
<tr><td colspan="2" style="color:#FFF;height:20px;border-width:0;"/></tr>
<tr><td colspan="2" style="text-align:center;background-color:#0066DF;color:white;font-weight:bold;padding:10px;"><a id="Part_A_-_Information_about_the_Offeror_or_the_Person_Seeking_Admission_to_Trading">Part A - Information about the Offeror or the Person Seeking Admission to Trading</a></td></tr>
<tr>
<td style="background-color:#92D050; width:30%;">A.1: Name</td>
<td id="_TEMPLATE_A.1" style="color:#0066DF;"><ix:nonNumeric name="mica:NameOfOtherTokenOfferor" contextRef="_ctx1" id="TEMPLATE_A.1" escape="false"><div style="color:#0066DF;"><p>Genesys Protocol Holdings Ltd.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">A.2: Legal form</td>
<td id="_TEMPLATE_A.2" style="color:#0066DF;"><ix:nonNumeric name="mica:OfferorsLegalForm" contextRef="_ctx1" id="TEMPLATE_A.2" escape="false"><div style="color:#0066DF;"><p>A Company Limited by Shares</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">A.3: Registered address</td>
<td id="_TEMPLATE_A.3" style="color:#0066DF;"><ix:nonNumeric name="mica:OfferorsRegisteredAddressDetailsAbstract" contextRef="_ctx1" id="TEMPLATE_A.3" escape="false"><div style="color:#0066DF;"><p>CCP Financial Consultants Limited, 2nd Floor, Ellen L. Skelton Building, Fishers Lane, Road Town, Tortola, British Virgin Islands</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">A.4: Head office</td>
<td id="_TEMPLATE_A.4" style="color:#0066DF;"><ix:nonNumeric name="mica:OfferorsHeadOfficeDetailsAbstract" contextRef="_ctx1" id="TEMPLATE_A.4" escape="false"><div style="color:#0066DF;"><p>CCP Financial Consultants Limited, 2nd Floor, Ellen L. Skelton Building, Fishers Lane, Road Town, Tortola, British Virgin Islands</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">A.5: Registration date</td>
<td id="_TEMPLATE_A.5" style="color:#0066DF;"><ix:nonNumeric name="mica:OfferorsRegistrationDate" contextRef="_ctx1" id="TEMPLATE_A.5" escape="false"><div style="color:#0066DF;"><p>2025-12-27</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">A.6: Legal entity identifier</td>
<td id="_TEMPLATE_A.6" style="color:#0066DF;"><ix:nonNumeric name="mica:OfferorsLegalEntityIdentifier" contextRef="_ctx1" id="TEMPLATE_A.6" escape="false"><div style="color:#0066DF;"><p>254900RNIRZ1EOPDO568</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">A.7: Another identifier required pursuant to applicable national law</td>
<td id="_TEMPLATE_A.7" style="color:#0066DF;"><ix:nonNumeric name="mica:OfferorsAnotherIdentifierRequiredPursuantToApplicableNationalLaw" contextRef="_ctx1" id="TEMPLATE_A.7" escape="false"><div style="color:#0066DF;"><p>2197263</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">A.8: Contact telephone number</td>
<td id="_TEMPLATE_A.8" style="color:#0066DF;"><ix:nonNumeric name="mica:OfferorsContactTelephoneNumber" contextRef="_ctx1" id="TEMPLATE_A.8" escape="false"><div style="color:#0066DF;"><p>+13457499601</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">A.9: E-mail address</td>
<td id="_TEMPLATE_A.9" style="color:#0066DF;"><ix:nonNumeric name="mica:OfferorsEmailAddress" contextRef="_ctx1" id="TEMPLATE_A.9" escape="false"><div style="color:#0066DF;"><p>gkennedy@leewardmanagement.ky</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">A.10: Response time (days)</td>
<td id="_TEMPLATE_A.10" style="color:#0066DF;"><ix:nonNumeric name="mica:OfferorsResponseTimeDays" contextRef="_ctx1" id="TEMPLATE_A.10" escape="false"><div style="color:#0066DF;"><p>002</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">A.11: Parent company</td>
<td id="_TEMPLATE_A.11" style="color:#0066DF;"><ix:nonNumeric name="mica:IdentificationOfOfferorsParentCompany" contextRef="_ctx1" id="TEMPLATE_A.11" escape="false"><div style="color:#0066DF;"><p>There is no parent company.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">A.12: Members of management body</td>
<td id="_TEMPLATE_A.12" style="color:#0066DF;"><ix:nonNumeric name="mica:MembersOfOfferorsManagementBodyForOtherTokenAbstract" contextRef="_ctx1" id="TEMPLATE_A.12" escape="false"><div style="color:#0066DF;"><p>Executive / Director : Diana Aidee Muñoz Maclao de Camargo,<br />
Residential address: Ernesto Cordoba Campos, Urbanizacion Casa Real Second Street, No 274., Panama City, Panama.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">A.13: Business activity</td>
<td id="_TEMPLATE_A.13" style="color:#0066DF;"><ix:nonNumeric name="mica:OfferorsBusinessActivityExplanatory" contextRef="_ctx1" id="TEMPLATE_A.13" escape="false"><div style="color:#0066DF;"><p>The principal business activity of Genesys Protocol Holdings Ltd. is facilitating onchain, collateralized financing for AI infrastructure, allowing neocloud operators and similar market participants to access capital without selling equity or relinquishing operational control of their hardware. The protocol operates permissionlessly and onchain, connecting liquidity providers with borrowers in the AI compute market. Its principal market consists of AI infrastructure providers, GPU operators, and decentralized compute networks seeking capital-efficient financing solutions.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">A.14: Parent company business activity</td>
<td id="_TEMPLATE_A.14" style="color:#0066DF;"><ix:nonNumeric name="mica:ParentCompanyBusinessActivityOfOfferorSideExplanatory" contextRef="_ctx1" id="TEMPLATE_A.14" escape="false"><div style="color:#0066DF;"><p>Not applicable as the offeror or person seeking admission to trading was established within the past three years.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">A.15: Newly established</td>
<td id="_TEMPLATE_A.15" style="color:#0066DF;"><ix:nonNumeric name="mica:NewlyEstablishedOfferorsIndicator" contextRef="_ctx1" id="TEMPLATE_A.15" escape="false"><div style="color:#0066DF;"><p>True</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">A.16: Financial condition for the past three years</td>
<td id="_TEMPLATE_A.16" style="color:#0066DF;"><ix:nonNumeric name="mica:InformationAboutOfferorsFinancialConditionForPastThreeYearsExplanatory" contextRef="_ctx1" id="TEMPLATE_A.16" escape="false"><div style="color:#0066DF;"><p>Not applicable as the offeror or person seeking admission to trading was established within the past three years.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">A.17: Financial condition since registration</td>
<td id="_TEMPLATE_A.17" style="color:#0066DF;"><ix:nonNumeric name="mica:InformationAboutOfferorsFinancialConditionSinceRegistrationExplanatory" contextRef="_ctx1" id="TEMPLATE_A.17" escape="false"><div style="color:#0066DF;"><p>Genesys Protocol Holdings Ltd. was incorporated on December 27, 2025, and has therefore existed for less than three years. Due to the recent incorporation, only limited historical financial information is currently available, and audited or management accounts for the preceding three-year period are not applicable. Any available financial statements will be provided as they become available as operations progress.</p>
<p>The project is expected to be capitalized primarily through an initial coin offering (ICO) targeting proceeds of approximately USD 21 million. The ICO proceeds are intended to be used in a discretionary manner to expand, support, and solidify the USD.AI protocol ecosystem and its associated operations.</p>
<p>Potential uses of funds may include, but are not limited to: 1) capitalizing protocol-owned or protocol-aligned initiatives that support liquidity, risk management, or market efficiency, such as a GPU Inventory Maker (GIM) or similar facilities designed to manage defaulted GPU collateral; 2) capitalizing first-loss or risk-absorbing protocol positions to support prudent financing parameters and risk curation; 3) paying service providers that support the protocol’s technological, financial, legal, compliance, and operational infrastructure, including off-chain functions; and 4) satisfying regulatory, compliance, and other financial obligations of the entity or protocol.</p>
<p>Where implemented, a GPU Inventory Maker would function as a protocol-owned market-facing facility that may act as a buyer of last resort for defaulted GPU collateral, assume short-term inventory risk, and seek to generate revenue through resale to secondary market participants, including neocloud operators or IT asset disposition firms. Such mechanisms are intended to support protocol liquidity and resilience and may convert default events into recoverable value, though no specific implementation is guaranteed.</p>
<p>Key performance indicators for the protocol are expected to be both financial and non-financial in nature and may include metrics related to protocol adoption, liquidity, collateral performance, risk utilization, and yields generated from protocol activities, including those related to GPU-backed financing arrangements. Capital resources are expected to consist primarily of ICO proceeds and any revenues generated through protocol-aligned activities.</p>
</div></ix:nonNumeric></td>
</tr>
<tr><td colspan="2" style="color:#FFF;height:20px;border-width:0;"/></tr>
<tr><td colspan="2" style="text-align:center;background-color:#0066DF;color:white;font-weight:bold;padding:10px;"><a id="Part_B_-_Information_about_the_Issuer,_If_Different_from_the_Offeror_or_Person_Seeking_Admission_to_Trading">Part B - Information about the Issuer, If Different from the Offeror or Person Seeking Admission to Trading</a></td></tr>
<tr>
<td style="background-color:#92D050; width:30%;">B.1: Issuer different from offerror or person seeking admission to trading</td>
<td id="_TEMPLATE_B.1" style="color:#0066DF;"><ix:nonNumeric name="mica:IssuerDifferentFromOfferrorOrPersonSeekingAdmissionToTrading" contextRef="_ctx1" id="TEMPLATE_B.1" escape="false"><div style="color:#0066DF;"><p>False</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">B.2: Name</td>
<td id="_TEMPLATE_B.2" style="color:#0066DF;"><ix:nonNumeric name="mica:NameOfOtherTokenIssuer" contextRef="_ctx1" id="TEMPLATE_B.2" escape="false"><div style="color:#0066DF;"><p>Not applicable as the issuer is the person seeking admission to trading.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">B.3: Legal form</td>
<td id="_TEMPLATE_B.3" style="color:#0066DF;"><ix:nonNumeric name="mica:IssuersLegalForm" contextRef="_ctx1" id="TEMPLATE_B.3" escape="false"><div style="color:#0066DF;"><p>Not applicable as the issuer is the person seeking admission to trading.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">B.4: Registered address</td>
<td id="_TEMPLATE_B.4" style="color:#0066DF;"><ix:nonNumeric name="mica:IssuersRegisteredAddressDetailsAbstract" contextRef="_ctx1" id="TEMPLATE_B.4" escape="false"><div style="color:#0066DF;"><p>Not applicable as the issuer is the person seeking admission to trading.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">B.5: Head office</td>
<td id="_TEMPLATE_B.5" style="color:#0066DF;"><ix:nonNumeric name="mica:IssuersHeadOfficeDetailsAbstract" contextRef="_ctx1" id="TEMPLATE_B.5" escape="false"><div style="color:#0066DF;"><p>Not applicable as the issuer is the person seeking admission to trading.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">B.6: Registration date</td>
<td id="_TEMPLATE_B.6" style="color:#0066DF;"><ix:nonNumeric name="mica:IssuersRegistrationDate" contextRef="_ctx1" id="TEMPLATE_B.6" escape="false"><div style="color:#0066DF;"><p>Not applicable as the issuer is the person seeking admission to trading.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">B.7: Legal entity identifier</td>
<td id="_TEMPLATE_B.7" style="color:#0066DF;"><ix:nonNumeric name="mica:IssuersLegalEntityIdentifier" contextRef="_ctx1" id="TEMPLATE_B.7" escape="false"><div style="color:#0066DF;"><p>Not applicable as the issuer is the person seeking admission to trading.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">B.8: Another identifier required pursuant to applicable national law</td>
<td id="_TEMPLATE_B.8" style="color:#0066DF;"><ix:nonNumeric name="mica:IssuersAnotherIdentifierRequiredPursuantToApplicableNationalLaw" contextRef="_ctx1" id="TEMPLATE_B.8" escape="false"><div style="color:#0066DF;"><p>Not applicable as the issuer is the person seeking admission to trading.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">B.9: Parent company</td>
<td id="_TEMPLATE_B.9" style="color:#0066DF;"><ix:nonNumeric name="mica:IdentificationOfIssuersParentCompany" contextRef="_ctx1" id="TEMPLATE_B.9" escape="false"><div style="color:#0066DF;"><p>Not applicable as the issuer is the person seeking admission to trading.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">B.10: Members of management body</td>
<td id="_TEMPLATE_B.10" style="color:#0066DF;"><ix:nonNumeric name="mica:MembersOfIssuersManagementBodyForOtherTokenAbstract" contextRef="_ctx1" id="TEMPLATE_B.10" escape="false"><div style="color:#0066DF;"><p>Not applicable as the issuer is the person seeking admission to trading.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">B.11: Business activity</td>
<td id="_TEMPLATE_B.11" style="color:#0066DF;"><ix:nonNumeric name="mica:IssuersBusinessActivityExplanatory" contextRef="_ctx1" id="TEMPLATE_B.11" escape="false"><div style="color:#0066DF;"><p>Not applicable as the issuer is the person seeking admission to trading.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">B.12: Parent company business activity</td>
<td id="_TEMPLATE_B.12" style="color:#0066DF;"><ix:nonNumeric name="mica:ParentCompanyBusinessActivityOfIssuerSideExplanatory" contextRef="_ctx1" id="TEMPLATE_B.12" escape="false"><div style="color:#0066DF;"><p>Not applicable as the issuer is the person seeking admission to trading.</p>
</div></ix:nonNumeric></td>
</tr>
<tr><td colspan="2" style="color:#FFF;height:20px;border-width:0;"/></tr>
<tr><td colspan="2" style="text-align:center;background-color:#0066DF;color:white;font-weight:bold;padding:10px;"><a id="Part_C_-_Information_about_the_Operator_of_the_Trading_Platform">Part C - Information about the Operator of the Trading Platform</a></td></tr>
<tr>
<td style="background-color:#92D050; width:30%;">C.1: Name</td>
<td id="_TEMPLATE_C.1" style="color:#0066DF;"><ix:nonNumeric name="mica:NameOfOtherTokenOperator" contextRef="_ctx1" id="TEMPLATE_C.1" escape="false"><div style="color:#0066DF;"><p>Not applicable as the person seeking admission to trading is not the operator of the trading platform.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">C.2: Legal form</td>
<td id="_TEMPLATE_C.2" style="color:#0066DF;"><ix:nonNumeric name="mica:OperatorsLegalForm" contextRef="_ctx1" id="TEMPLATE_C.2" escape="false"><div style="color:#0066DF;"><p>Not applicable as the person seeking admission to trading is not the operator of the trading platform.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">C.3: Registered address</td>
<td id="_TEMPLATE_C.3" style="color:#0066DF;"><ix:nonNumeric name="mica:OperatorsRegisteredAddressDetailsAbstract" contextRef="_ctx1" id="TEMPLATE_C.3" escape="false"><div style="color:#0066DF;"><p>Not applicable as the person seeking admission to trading is not the operator of the trading platform.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">C.4: Head office</td>
<td id="_TEMPLATE_C.4" style="color:#0066DF;"><ix:nonNumeric name="mica:OperatorsHeadOfficeDetailsAbstract" contextRef="_ctx1" id="TEMPLATE_C.4" escape="false"><div style="color:#0066DF;"><p>Not applicable as the person seeking admission to trading is not the operator of the trading platform.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">C.5: Registration date</td>
<td id="_TEMPLATE_C.5" style="color:#0066DF;"><ix:nonNumeric name="mica:OperatorsRegistrationDate" contextRef="_ctx1" id="TEMPLATE_C.5" escape="false"><div style="color:#0066DF;"><p>Not applicable as the person seeking admission to trading is not the operator of the trading platform.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">C.6: Legal entity identifier</td>
<td id="_TEMPLATE_C.6" style="color:#0066DF;"><ix:nonNumeric name="mica:OperatorsLegalEntityIdentifier" contextRef="_ctx1" id="TEMPLATE_C.6" escape="false"><div style="color:#0066DF;"><p>Not applicable as the person seeking admission to trading is not the operator of the trading platform.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">C.7: Another identifier required pursuant to applicable national law</td>
<td id="_TEMPLATE_C.7" style="color:#0066DF;"><ix:nonNumeric name="mica:OperatorsAnotherIdentifierRequiredPursuantToApplicableNationalLaw" contextRef="_ctx1" id="TEMPLATE_C.7" escape="false"><div style="color:#0066DF;"><p>Not applicable as the person seeking admission to trading is not the operator of the trading platform.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">C.8: Parent company</td>
<td id="_TEMPLATE_C.8" style="color:#0066DF;"><ix:nonNumeric name="mica:IdentificationOfOperatorsParentCompany" contextRef="_ctx1" id="TEMPLATE_C.8" escape="false"><div style="color:#0066DF;"><p>Not applicable as the person seeking admission to trading is not the operator of the trading platform.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">C.9: Reason for crypto-asset white paper preparation</td>
<td id="_TEMPLATE_C.9" style="color:#0066DF;"><ix:nonNumeric name="mica:ReasonForCryptoassetWhitePaperPreparationExplanatory" contextRef="_ctx1" id="TEMPLATE_C.9" escape="false"><div style="color:#0066DF;"><p>Not applicable as the person seeking admission to trading is not the operator of the trading platform.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">C.10: Members of management body</td>
<td id="_TEMPLATE_C.10" style="color:#0066DF;"><ix:nonNumeric name="mica:MembersOfOperatorsManagementBodyForOtherTokenAbstract" contextRef="_ctx1" id="TEMPLATE_C.10" escape="false"><div style="color:#0066DF;"><p>Not applicable as the person seeking admission to trading is not the operator of the trading platform.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">C.11: Operator business activity</td>
<td id="_TEMPLATE_C.11" style="color:#0066DF;"><ix:nonNumeric name="mica:OperatorsBusinessActivityExplanatory" contextRef="_ctx1" id="TEMPLATE_C.11" escape="false"><div style="color:#0066DF;"><p>Not applicable as the person seeking admission to trading is not the operator of the trading platform.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">C.12: Parent company business activity</td>
<td id="_TEMPLATE_C.12" style="color:#0066DF;"><ix:nonNumeric name="mica:ParentCompanyBusinessActivityOfOperatorSideExplanatory" contextRef="_ctx1" id="TEMPLATE_C.12" escape="false"><div style="color:#0066DF;"><p>Not applicable as the person seeking admission to trading is not the operator of the trading platform.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">C.13: Other persons drawing up the crypto-asset white paper according to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114</td>
<td id="_TEMPLATE_C.13" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherPersonsDrawingUpCryptoassetWhitePaperExplanatory" contextRef="_ctx1" id="TEMPLATE_C.13" escape="false"><div style="color:#0066DF;"><p>Not applicable as the person seeking admission to trading is not the operator of the trading platform.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">C.14: Reason for drawing the white paper by persons referred to in Article 6(1), second subparagraph, of Regulation (EU) 2023/1114</td>
<td id="_TEMPLATE_C.14" style="color:#0066DF;"><ix:nonNumeric name="mica:ReasonForDrawingWhitePaperExplanatory" contextRef="_ctx1" id="TEMPLATE_C.14" escape="false"><div style="color:#0066DF;"><p>Not applicable as the person seeking admission to trading is not the operator of the trading platform.</p>
</div></ix:nonNumeric></td>
</tr>
<tr><td colspan="2" style="color:#FFF;height:20px;border-width:0;"/></tr>
<tr><td colspan="2" style="text-align:center;background-color:#0066DF;color:white;font-weight:bold;padding:10px;"><a id="Part_D_-_Information_about_the_Crypto-Asset_Project">Part D - Information about the Crypto-Asset Project</a></td></tr>
<tr>
<td style="background-color:#92D050; width:30%;">D.1: Crypto-asset project name</td>
<td id="_TEMPLATE_D.1" style="color:#0066DF;"><ix:nonNumeric name="mica:NameOfOtherTokenProject" contextRef="_ctx1" id="TEMPLATE_D.1" escape="false"><div style="color:#0066DF;"><p>USD.AI</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">D.2: Crypto-asset name</td>
<td id="_TEMPLATE_D.2" style="color:#0066DF;"><ix:nonNumeric name="mica:NameOfOtherToken" contextRef="_ctx1" id="TEMPLATE_D.2" escape="false"><div style="color:#0066DF;"><p>CHIP</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">D.3: Abbreviation</td>
<td id="_TEMPLATE_D.3" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokenProjectAbbreviation" contextRef="_ctx1" id="TEMPLATE_D.3" escape="false"><div style="color:#0066DF;"><p>CHIP</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">D.4: Crypto-asset project description</td>
<td id="_TEMPLATE_D.4" style="color:#0066DF;"><ix:nonNumeric name="mica:DescriptionOfOtherTokenProjectExplanatory" contextRef="_ctx1" id="TEMPLATE_D.4" escape="false"><div style="color:#0066DF;"><p>Purpose and Goals:<br />
USD.AI is a crypto-asset project designed to provide dollar-denominated liquidity for the AI infrastructure ecosystem, with a particular focus on financing compute infrastructure such as GPUs and servers. The protocol aims to enable permissionless, on-chain financing by connecting stable, fiat-referenced liquidity with real-world AI infrastructure assets, while maintaining transparency, capital efficiency, and risk isolation.</p>
<p>Key Features and Operation:</p>
<p>Real-World Asset (RWA) Collateralization:<br />
Borrowers may tokenize economic rights associated with GPUs or server hardware as on-chain collateral. These rights are represented using ERC-721 tokens and are supported by contractual and operational structures designed to enable enforceability and off-chain execution in the event of default. These RWA-related tokens and structures operate independently from the $CHIP token. The $CHIP token does not represent, grant, or relate to any ownership, economic, or other rights in respect of the underlying real-world assets, nor does it serve as collateral or a claim on such assets.</p>
<p>Governance and Risk Management:<br />
Protocol governance is coordinated through the $CHIP token, which enables participation in decisions related to protocol upgrades, risk parameters, and governance mechanisms intended to mitigate bad debt and maintain overall system health. The governance role of $CHIP is limited to protocol-level decision-making and does not extend to the issuance, performance, or enforcement of real-world asset collateral.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">D.5: Details of all natural or legal persons involved in implementation of crypto-asset project</td>
<td id="_TEMPLATE_D.5" style="color:#0066DF;"><ix:nonNumeric name="mica:DetailsOfAllNaturalOrLegalPersonsInvolvedInImplementationOfOtherTokenProjectAbstract" contextRef="_ctx1" id="TEMPLATE_D.5" escape="false"><div style="color:#0066DF;"><p>USD.AI Foundation – Primary tokenizing agent that facilitates the creation of onchain property rights for AI infrastructure assets, enables tokenization of AI hardware and infrastructure, and primarily serves the AI infrastructure industry and related markets that require asset-backed lending and liquidity solution.</p>
<p>CCP Financial Consultants Limited  –Registered address and head office provider: 2nd Floor, Ellen L. Skelton Building, Fishers Lane, Road Town, Tortola, British Virgin Islands</p>
<p>Cantina – Security audits and advisory services</p>
<p>Spearbit – Security audits and advisory services</p>
<p>Immunefi – Bug bounty and security platform</p>
<p>PYUSD – Stablecoin infrastructure provider</p>
<p>Anchorage Digital – Digital asset custody infrastructure</p>
<p>TRM – Transaction monitoring and risk scoring services</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">D.6: Utility token classification</td>
<td id="_TEMPLATE_D.6" style="color:#0066DF;"><ix:nonNumeric name="mica:UtilityTokenClassificationForOtherTokenProjectIndicator" contextRef="_ctx1" id="TEMPLATE_D.6" escape="false"><div style="color:#0066DF;"><p>False</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">D.7: Key features of goods or services for utility token projects</td>
<td id="_TEMPLATE_D.7" style="color:#0066DF;"><ix:nonNumeric name="mica:KeyFeaturesOfGoodsOrServicesForUtilityTokenProjectsExplanatory" contextRef="_ctx1" id="TEMPLATE_D.7" escape="false"><div style="color:#0066DF;"><p>Not applicable as CHIP is not a utility token as defined under MiCA.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">D.8: Plans for the token</td>
<td id="_TEMPLATE_D.8" style="color:#0066DF;"><ix:nonNumeric name="mica:PlansForTokenAbstract" contextRef="_ctx1" id="TEMPLATE_D.8" escape="false"><div style="color:#0066DF;"><p>Achievements:</p>
<p>USD.AI has been developed as a permissionless, overcollateralized protocol designed to finance the AI infrastructure industry. Certain components of the project are undertaken and supported by Genesys Protocol Holdings Ltd. as the issuer. Governance within the USD.AI protocol is coordinated through the $CHIP token and is limited to protocol-level mechanisms, including parameter adjustments and risk management frameworks, and does not extend to the corporate governance, ownership, or management of Genesys Protocol Holdings Ltd.</p>
<p>The protocol has introduced mechanisms such as the GPU Inventory Maker (GIM) for managing defaulted collateral and the Queue Extractable Value (QEV) system to support liquidity management and yield optimization for protocol participants. These mechanisms operate at the protocol level and are distinct from the issuer’s corporate activities.</p>
<p>Future Milestones:</p>
<p>2026 (TGE): Token Generation Event (TGE) for $CHIP, including ICO and airdrop distribution.</p>
<p>2026: Progressive unlocking of team, investor, and ecosystem token allocations in accordance with predefined vesting schedules.</p>
<p>2026: Expansion of protocol-level governance, including the introduction of USD.AI Improvement Proposals (UIPs) and community-driven upgrades, which relate solely to the operation and parameters of the USD.AI protocol.</p>
<p>2026: Further integration of tokenized GPU-related economic rights and scaling of the lending protocol to additional AI infrastructure partners, as part of the project activities undertaken by the issuer.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">D.9: Resource allocation</td>
<td id="_TEMPLATE_D.9" style="color:#0066DF;"><ix:nonNumeric name="mica:ResourceAllocationExplanatory" contextRef="_ctx1" id="TEMPLATE_D.9" escape="false"><div style="color:#0066DF;"><p>Financial Resources:<br />
$CHIP token is targeting an approximate $21 million raise through its token offering to support protocol development and ecosystem growth. ICO proceeds are intended to be used flexibly across a range of initiatives that promote protocol stability and adoption, including (by way of example) capitalizing protocol-owned facilities such as a GPU Inventory Maker (GIM), funding first-loss risk positions, paying service providers, and satisfying operational, legal, and compliance requirements.</p>
<p>Human Resources:<br />
Protocol development and ongoing operations are supported by a combination of internal contributors and external service providers. USD.AI Foundation acts as a core support entity to the USD.AI protocol, ensuring technical and operational functions. Token allocations intended for contributors and service providers represent a material but non-controlling portion of total supply and are subject to long-term vesting arrangements designed to align incentives with the protocol’s longevity.</p>
<p>Technological Resources:<br />
Resources have been allocated to the development of the USD.AI protocol’s core infrastructure, including smart contracts supporting the $USDai and $sUSDai system, the Queue Extractable Value (QEV) redemption mechanism, risk and underwriting modules, and infrastructure enabling the tokenization and use of GPU-related collateral. The protocol also integrates third-party stablecoin and custody infrastructure as part of its technical stack.</p>
<p>Other Significant Investments:<br />
Additional resources are allocated to ecosystem development, risk management tooling, compliance systems, audits, and security reviews. Token allocations for investors, contributors, and ecosystem incentives are subject to change and are expected to vest over multi-year periods to support long-term protocol sustainability.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">D.10: Planned use of collected funds or other tokens</td>
<td id="_TEMPLATE_D.10" style="color:#0066DF;"><ix:nonNumeric name="mica:PlannedUseOfCollectedFundsOrOtherTokensExplanatory" contextRef="_ctx1" id="TEMPLATE_D.10" escape="false"><div style="color:#0066DF;"><p>Funds and crypto-assets collected by the USD.AI protocol are intended to be used flexibly to promote, expand, and maintain the health of the protocol and its surrounding ecosystem. Planned uses include supporting core protocol development, operational expenses, security and risk management, and providing incentives to ecosystem participants and AI infrastructure stakeholders to expand the protocol’s value chain.</p>
<p>By way of example, a portion of the collected resources may be allocated to capitalizing protocol-owned facilities such as a GPU Inventory Maker (GIM), which could act as a buyer of last resort for defaulted GPU collateral and help preserve protocol liquidity. Other potential uses include funding first-loss risk positions, compensating service providers, incentivizing adoption by developers and infrastructure providers, and supporting initiatives that position the protocol as a scalable settlement and financing layer for AI infrastructure.</p>
<p>The specific allocation of funds remains subject to governance decisions and may evolve over time in response to protocol needs, market conditions, and ecosystem growth objectives.</p>
</div></ix:nonNumeric></td>
</tr>
<tr><td colspan="2" style="color:#FFF;height:20px;border-width:0;"/></tr>
<tr><td colspan="2" style="text-align:center;background-color:#0066DF;color:white;font-weight:bold;padding:10px;"><a id="Part_E_-_Information_about_the_Offer_to_the_Public_of_Crypto-Assets_or_their_Admission_to_Trading">Part E - Information about the Offer to the Public of Crypto-Assets or their Admission to Trading</a></td></tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.1: Public offering or admission to trading</td>
<td id="_TEMPLATE_E.1" style="color:#0066DF;"><ix:nonNumeric name="mica:PublicOfferingOrAdmissionToTrading" contextRef="_ctx1" id="TEMPLATE_E.1" escape="false"><div style="color:#0066DF;"><p>ATTR</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.2: Reasons for public offer or admission to trading</td>
<td id="_TEMPLATE_E.2" style="color:#0066DF;"><ix:nonNumeric name="mica:ReasonsForPublicOfferOrAdmissionToTradingExplanatory" contextRef="_ctx1" id="TEMPLATE_E.2" escape="false"><div style="color:#0066DF;"><p>Enable EU market access for CHIP holders.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.3: Fundraising target</td>
<td id="_TEMPLATE_E.3" style="color:#0066DF;"><ix:nonNumeric name="mica:FundraisingTargetDetailsAbstract" contextRef="_ctx1" id="TEMPLATE_E.3" escape="false"><div style="color:#0066DF;"><p>Not applicable. This whitepaper is published solely in relation to the admission to trading of the CHIP token and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.4: Minimum subscription goals</td>
<td id="_TEMPLATE_E.4" style="color:#0066DF;"><ix:nonNumeric name="mica:MinimumSubscriptionGoalsDetailsAbstract" contextRef="_ctx1" id="TEMPLATE_E.4" escape="false"><div style="color:#0066DF;"><p>Not applicable. This whitepaper is published solely in relation to the admission to trading of the CHIP token and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.5: Maximum subscription goals</td>
<td id="_TEMPLATE_E.5" style="color:#0066DF;"><ix:nonNumeric name="mica:MaximumSubscriptionGoalsDetailsAbstract" contextRef="_ctx1" id="TEMPLATE_E.5" escape="false"><div style="color:#0066DF;"><p>Not applicable. This whitepaper is published solely in relation to the admission to trading of the CHIP token and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.6: Oversubscription acceptance</td>
<td id="_TEMPLATE_E.6" style="color:#0066DF;"><ix:nonNumeric name="mica:OversubscriptionAcceptanceIndicator" contextRef="_ctx1" id="TEMPLATE_E.6" escape="false"><div style="color:#0066DF;"><p>Not applicable. This whitepaper is published solely in relation to the admission to trading of the CHIP token and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.7: Oversubscription allocation</td>
<td id="_TEMPLATE_E.7" style="color:#0066DF;"><ix:nonNumeric name="mica:OversubscriptionAllocationExplanatory" contextRef="_ctx1" id="TEMPLATE_E.7" escape="false"><div style="color:#0066DF;"><p>Not applicable. This whitepaper is published solely in relation to the admission to trading of the CHIP token and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.8: Issue price</td>
<td id="_TEMPLATE_E.8" style="color:#0066DF;"><ix:nonNumeric name="mica:IssuePrice" contextRef="_ctx1" id="TEMPLATE_E.8" escape="false"><div style="color:#0066DF;"><p>Not applicable. This whitepaper is published solely in relation to the admission to trading of the CHIP token and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.9: Official currency determining issue price</td>
<td id="_TEMPLATE_E.9" style="color:#0066DF;"><ix:nonNumeric name="mica:OfficialCurrencyDeterminingIssuePrice" contextRef="_ctx1" id="TEMPLATE_E.9" escape="false"><div style="color:#0066DF;"><p>Not applicable. This whitepaper is published solely in relation to the admission to trading of the CHIP token and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.10: Subscription fee</td>
<td id="_TEMPLATE_E.10" style="color:#0066DF;"><ix:nonNumeric name="mica:SubscriptionFeeDetailsAbstract" contextRef="_ctx1" id="TEMPLATE_E.10" escape="false"><div style="color:#0066DF;"><p>Not applicable. This whitepaper is published solely in relation to the admission to trading of the CHIP token and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.11: Offer price determination method</td>
<td id="_TEMPLATE_E.11" style="color:#0066DF;"><ix:nonNumeric name="mica:OfferPriceDeterminationMethodExplanatory" contextRef="_ctx1" id="TEMPLATE_E.11" escape="false"><div style="color:#0066DF;"><p>Not applicable. This whitepaper is published solely in relation to the admission to trading of the CHIP token and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.12: Total number of offered or traded other tokens</td>
<td id="_TEMPLATE_E.12" style="color:#0066DF;"><ix:nonNumeric name="mica:TotalNumberOfOfferedOrTradedOtherTokens" contextRef="_ctx1" id="TEMPLATE_E.12" escape="false"><div style="color:#0066DF;"><p>10,000,000,000</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.13: Targeted holders</td>
<td id="_TEMPLATE_E.13" style="color:#0066DF;"><ix:nonNumeric name="mica:TargetedHoldersForOtherToken" contextRef="_ctx1" id="TEMPLATE_E.13" escape="false"><div style="color:#0066DF;"><p>All.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.14: Holder restrictions</td>
<td id="_TEMPLATE_E.14" style="color:#0066DF;"><ix:nonNumeric name="mica:HolderRestrictionsExplanatory" contextRef="_ctx1" id="TEMPLATE_E.14" escape="false"><div style="color:#0066DF;"><p>There are no restrictions.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.15: Reimbursement notice</td>
<td id="_TEMPLATE_E.15" style="color:#0066DF;"><ix:nonNumeric name="mica:ReimbursementNotice" contextRef="_ctx1" id="TEMPLATE_E.15" escape="false"><div style="color:#0066DF;"><p>There are no reimbursement rights.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.16: Refund mechanism</td>
<td id="_TEMPLATE_E.16" style="color:#0066DF;"><ix:nonNumeric name="mica:RefundMechanismExplanatory" contextRef="_ctx1" id="TEMPLATE_E.16" escape="false"><div style="color:#0066DF;"><p>There is no refund mechanism.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.17: Refund timeline</td>
<td id="_TEMPLATE_E.17" style="color:#0066DF;"><ix:nonNumeric name="mica:RefundTimelineExplanatory" contextRef="_ctx1" id="TEMPLATE_E.17" escape="false"><div style="color:#0066DF;"><p>There is no refund mechanism.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.18: Offer phases</td>
<td id="_TEMPLATE_E.18" style="color:#0066DF;"><ix:nonNumeric name="mica:DescriptionOfOtherTokenProjectPhasesExplanatory" contextRef="_ctx1" id="TEMPLATE_E.18" escape="false"><div style="color:#0066DF;"><p>Not applicable. This whitepaper is published solely in relation to the admission to trading of the CHIP token and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.19: Early purchase discount</td>
<td id="_TEMPLATE_E.19" style="color:#0066DF;"><ix:nonNumeric name="mica:DisclosureOfEarlyPurchaseDiscountExplanatory" contextRef="_ctx1" id="TEMPLATE_E.19" escape="false"><div style="color:#0066DF;"><p>Not applicable. This whitepaper is published solely in relation to the admission to trading of the CHIP token and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.20: Time-limited offer</td>
<td id="_TEMPLATE_E.20" style="color:#0066DF;"><ix:nonNumeric name="mica:TimelimitedOfferIndicator" contextRef="_ctx1" id="TEMPLATE_E.20" escape="false"><div style="color:#0066DF;"><p>Not applicable. This whitepaper is published solely in relation to the admission to trading of the CHIP token and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.21: Subscription period beginning</td>
<td id="_TEMPLATE_E.21" style="color:#0066DF;"><ix:nonNumeric name="mica:SubscriptionPeriodBeginning" contextRef="_ctx1" id="TEMPLATE_E.21" escape="false"><div style="color:#0066DF;"><p>Not applicable. This whitepaper is published solely in relation to the admission to trading of the CHIP token and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.22: Subscription period end</td>
<td id="_TEMPLATE_E.22" style="color:#0066DF;"><ix:nonNumeric name="mica:SubscriptionPeriodEnd" contextRef="_ctx1" id="TEMPLATE_E.22" escape="false"><div style="color:#0066DF;"><p>Not applicable. This whitepaper is published solely in relation to the admission to trading of the CHIP token and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.23: Safeguarding arrangements for offered funds or other tokens</td>
<td id="_TEMPLATE_E.23" style="color:#0066DF;"><ix:nonNumeric name="mica:SafeguardingArrangementsForOfferedFundsOrOtherTokensExplanatory" contextRef="_ctx1" id="TEMPLATE_E.23" escape="false"><div style="color:#0066DF;"><p>Not applicable. This whitepaper is published solely in relation to the admission to trading of the CHIP token and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.24: Payment methods for other token purchase</td>
<td id="_TEMPLATE_E.24" style="color:#0066DF;"><ix:nonNumeric name="mica:PaymentMethodsForOtherTokenPurchaseExplanatory" contextRef="_ctx1" id="TEMPLATE_E.24" escape="false"><div style="color:#0066DF;"><p>Fiat or other crypto-assets.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.25: Value transfer methods for reimbursement</td>
<td id="_TEMPLATE_E.25" style="color:#0066DF;"><ix:nonNumeric name="mica:ValueTransferMethodsForReimbursementExplanatory" contextRef="_ctx1" id="TEMPLATE_E.25" escape="false"><div style="color:#0066DF;"><p>There are no reimbursement rights.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.26: Right of withdrawal</td>
<td id="_TEMPLATE_E.26" style="color:#0066DF;"><ix:nonNumeric name="mica:RighOfWithdrawalExplanatory" contextRef="_ctx1" id="TEMPLATE_E.26" escape="false"><div style="color:#0066DF;"><p>Not applicable. This whitepaper is published solely in relation to the admission to trading of the CHIP token and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.27: Transfer of purchased other tokens</td>
<td id="_TEMPLATE_E.27" style="color:#0066DF;"><ix:nonNumeric name="mica:TransferOfPurchasedOtherTokensExplanatory" contextRef="_ctx1" id="TEMPLATE_E.27" escape="false"><div style="color:#0066DF;"><p>Via crypto-asset trading platforms on which CHIP is admitted to trading.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.28: Transfer time schedule</td>
<td id="_TEMPLATE_E.28" style="color:#0066DF;"><ix:nonNumeric name="mica:TransferTimeSchedule" contextRef="_ctx1" id="TEMPLATE_E.28" escape="false"><div style="color:#0066DF;"><p>There is no relevant time schedule.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.29: Purchaser&#39;s technical requirements</td>
<td id="_TEMPLATE_E.29" style="color:#0066DF;"><ix:nonNumeric name="mica:PurchasersTechnicalRequirementsExplanatory" contextRef="_ctx1" id="TEMPLATE_E.29" escape="false"><div style="color:#0066DF;"><p>There are no technical requirements.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.30: Other token service provider (CASP) name</td>
<td id="_TEMPLATE_E.30" style="color:#0066DF;"><ix:nonNumeric name="mica:NameOfOtherTokenServiceProvider" contextRef="_ctx1" id="TEMPLATE_E.30" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.31: CASP identifier</td>
<td id="_TEMPLATE_E.31" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokenServiceProviderIdentifier" contextRef="_ctx1" id="TEMPLATE_E.31" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.32: Placement form</td>
<td id="_TEMPLATE_E.32" style="color:#0066DF;"><ix:nonNumeric name="mica:PlacementFormForOtherToken" contextRef="_ctx1" id="TEMPLATE_E.32" escape="false"><div style="color:#0066DF;"><p>NTAV</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.33: Trading platforms name</td>
<td id="_TEMPLATE_E.33" style="color:#0066DF;"><ix:nonNumeric name="mica:TradingPlatformsName" contextRef="_ctx1" id="TEMPLATE_E.33" escape="false"><div style="color:#0066DF;"><p>Coinbase Luxembourg S.A.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.34: Trading platforms market identifier code (MIC)</td>
<td id="_TEMPLATE_E.34" style="color:#0066DF;"><ix:nonNumeric name="mica:TradingPlatformsIdentifierCode" contextRef="_ctx1" id="TEMPLATE_E.34" escape="false"><div style="color:#0066DF;"><p>XNAS</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.35: Trading platforms access</td>
<td id="_TEMPLATE_E.35" style="color:#0066DF;"><ix:nonNumeric name="mica:TradingPlatformsAccessExplanatory" contextRef="_ctx1" id="TEMPLATE_E.35" escape="false"><div style="color:#0066DF;"><p>Online via the platform.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.36: Involved costs</td>
<td id="_TEMPLATE_E.36" style="color:#0066DF;"><ix:nonNumeric name="mica:DescriptionOfInvolvedCostsExplanatory" contextRef="_ctx1" id="TEMPLATE_E.36" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.37: Offer expenses</td>
<td id="_TEMPLATE_E.37" style="color:#0066DF;"><ix:nonNumeric name="mica:DescriptionOfOfferExpensesExplanatory" contextRef="_ctx1" id="TEMPLATE_E.37" escape="false"><div style="color:#0066DF;"><p>Not applicable. This white paper is published solely in relation to the admission to trading and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.38: Conflicts of interest</td>
<td id="_TEMPLATE_E.38" style="color:#0066DF;"><ix:nonNumeric name="mica:InformationAboutPotentialConflictsOfInterestForOtherTokenExplanatory" contextRef="_ctx1" id="TEMPLATE_E.38" escape="false"><div style="color:#0066DF;"><p>The issuer is not aware of any potential conflict of interest of the persons involved in its offer to the public.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.39: Applicable law</td>
<td id="_TEMPLATE_E.39" style="color:#0066DF;"><ix:nonNumeric name="mica:ApplicableLawForOtherTokenOfferExplanatory" contextRef="_ctx1" id="TEMPLATE_E.39" escape="false"><div style="color:#0066DF;"><p>Not applicable. This white paper is published solely in relation to the admission to trading and does not relate to any public offering.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">E.40: Competent court</td>
<td id="_TEMPLATE_E.40" style="color:#0066DF;"><ix:nonNumeric name="mica:CompetentCourtForOtherTokenOfferExplanatory" contextRef="_ctx1" id="TEMPLATE_E.40" escape="false"><div style="color:#0066DF;"><p>British Virgin Islands</p>
</div></ix:nonNumeric></td>
</tr>
<tr><td colspan="2" style="color:#FFF;height:20px;border-width:0;"/></tr>
<tr><td colspan="2" style="text-align:center;background-color:#0066DF;color:white;font-weight:bold;padding:10px;"><a id="Part_F_-_Information_about_the_Crypto-Assets">Part F - Information about the Crypto-Assets</a></td></tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.1: Other token type</td>
<td id="_TEMPLATE_F.1" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokenType" contextRef="_ctx1" id="TEMPLATE_F.1" escape="false"><div style="color:#0066DF;"><p>The Token is a crypto-asset under Regulation (EU) 2023/1114 of the European Parliament and of the Council which is not an e-money token, an asset-referenced token or a utility token, each as defined under such Regulation. Therefore, it falls in the &quot;Other&quot; category.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.2: Other token functionality</td>
<td id="_TEMPLATE_F.2" style="color:#0066DF;"><ix:nonNumeric name="mica:InformationAboutOtherTokenFunctionalityExplanatory" contextRef="_ctx1" id="TEMPLATE_F.2" escape="false"><div style="color:#0066DF;"><p>The $CHIP token is the governance token of the USD.AI protocol and enables holders to participate in decentralized decision-making within the ecosystem. Key functionalities include:</p>
<p>Protocol Governance: $CHIP holders can vote on protocol upgrades, underwriting parameters, interest rate models, and other system-wide parameters.</p>
<p>Insurance &amp; Risk Mitigation: $CHIP can be staked in an insurance module to protect protocol participants against losses from GPU-backed loans or other operational risks.</p>
<p>Incentive Alignment: Staking and governance functions create alignment between token holders, borrowers, and the broader protocol, ensuring responsible participation in ecosystem decisions.</p>
<p>Non-Securities Nature: $CHIP does not confer equity, dividends, or profit rights; its functionality is limited to governance and ecosystem utility within USD.AI.</p>
<p>These functionalities are entirely onchain, permissionless, and designed to support the operation, growth, and security of the USD.AI ecosystem.</p>
<p>Insurance and incentive alignment are seperate features and not automatically avaliable as part of holding the token.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.3: Planned application of functionalities</td>
<td id="_TEMPLATE_F.3" style="color:#0066DF;"><ix:nonNumeric name="mica:InformationAboutPlannedApplicationOfFunctionalitiesExplanatory" contextRef="_ctx1" id="TEMPLATE_F.3" escape="false"><div style="color:#0066DF;"><ul>
<li>
<p><strong>Token Generation Event (TGE):</strong> The TGE for CHIP is expected in Q1 2026. This is the key event after which vesting schedules, token allocations, and other token-specific functionalities commence.</p>
</li>
<li>
<p><strong>Vesting Schedules:</strong></p>
<ul>
<li>Team and Investor tokens have a 1-year cliff and 3-year unlock from TGE. This means the first vesting for these allocations will occur 1 year after TGE (i.e., earliest Q1 2027), with full unlock by Q1 2030 if TGE is in Q1 2026.</li>
<li>Foundation Reserve: 10% is fully unlocked at TGE for liquidity, while 20.64% is subject to the same 1-year cliff and 3-year unlock as above.</li>
<li>Larger Liquidity Providers: 2.5% unlocks 8 months after TGE, 5% follows the 1-year cliff and 3-year unlock.<br />
These numbers are approximate and subject to change</li>
</ul>
</li>
<li>
<p><strong>Token Utility and Governance:</strong></p>
<ul>
<li>The CHIP governance token is introduced with Stage 3 of the protocol, which is tied to the TGE and subsequent decentralization of protocol governance. This includes the ability for tokenholders to participate in protocol decisions and improvement proposals.</li>
</ul>
</li>
</ul>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.4: Type of crypto-asset white paper</td>
<td id="_TEMPLATE_F.4" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokenTypeOfWhitePaper" contextRef="_ctx1" id="TEMPLATE_F.4" escape="false"><div style="color:#0066DF;"><p>OTHR</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.5: Type of submission</td>
<td id="_TEMPLATE_F.5" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokenTypeOfSubmission" contextRef="_ctx1" id="TEMPLATE_F.5" escape="false"><div style="color:#0066DF;"><p>NEWT</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.6: Other token characteristics</td>
<td id="_TEMPLATE_F.6" style="color:#0066DF;"><ix:nonNumeric name="mica:DescriptionOfOtherTokenCharacteristicsExplanatory" contextRef="_ctx1" id="TEMPLATE_F.6" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.7: Commercial name or trading name</td>
<td id="_TEMPLATE_F.7" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokenIssuersCommercialOrTradingName" contextRef="_ctx1" id="TEMPLATE_F.7" escape="false"><div style="color:#0066DF;"><p>Genesys Protocol Holdings Ltd.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.8: Website of the issuer</td>
<td id="_TEMPLATE_F.8" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokenIssuersWebsite" contextRef="_ctx1" id="TEMPLATE_F.8" escape="false"><div style="color:#0066DF;"><p>https://usd.ai.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.9: Starting date of offer to the public or admission to trading</td>
<td id="_TEMPLATE_F.9" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokenOfferStartingDate" contextRef="_ctx1" id="TEMPLATE_F.9" escape="false"><div style="color:#0066DF;"><p>2026-02-19</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.10: Publication date</td>
<td id="_TEMPLATE_F.10" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokenWhitePaperPublicationDate" contextRef="_ctx1" id="TEMPLATE_F.10" escape="false"><div style="color:#0066DF;"><p>2026-02-18</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.11: Any other services provided by the issuer</td>
<td id="_TEMPLATE_F.11" style="color:#0066DF;"><ix:nonNumeric name="mica:InformationAboutOtherServicesProvidedByOtherTokenIssuerExplanatory" contextRef="_ctx1" id="TEMPLATE_F.11" escape="false"><div style="color:#0066DF;"><p>Nothing other than already stated in the whitepaper.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.12: Language or languages of white paper</td>
<td id="_TEMPLATE_F.12" style="color:#0066DF;"><ix:nonNumeric name="mica:InformationAboutLanguagesUsedInOtherTokenWhitePaper" contextRef="_ctx1" id="TEMPLATE_F.12" escape="false"><div style="color:#0066DF;"><p>English.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.13: Digital token identifier code used to uniquely identify the crypto-asset or each of the several crypto assets to which the white paper relates, where available</td>
<td id="_TEMPLATE_F.13" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokenDigitalTokenIdentifierCode" contextRef="_ctx1" id="TEMPLATE_F.13" escape="false"><div style="color:#0066DF;"><p>MR60BP4N0</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.14: Functionally fungible group digital token identifier, where available</td>
<td id="_TEMPLATE_F.14" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokenFunctionallyFungibleGroupDigitalTokenIdentifier" contextRef="_ctx1" id="TEMPLATE_F.14" escape="false"><div style="color:#0066DF;"><p>Not available.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.15: Voluntary data flag</td>
<td id="_TEMPLATE_F.15" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokenVoluntaryDataFlagIndicator" contextRef="_ctx1" id="TEMPLATE_F.15" escape="false"><div style="color:#0066DF;"><p>False.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.16: Personal data flag</td>
<td id="_TEMPLATE_F.16" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokenPersonalDataFlagIndicator" contextRef="_ctx1" id="TEMPLATE_F.16" escape="false"><div style="color:#0066DF;"><p>True.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.17: LEI eligibility</td>
<td id="_TEMPLATE_F.17" style="color:#0066DF;"><ix:nonNumeric name="mica:LEIEligibilityIndicatorForOtherToken" contextRef="_ctx1" id="TEMPLATE_F.17" escape="false"><div style="color:#0066DF;"><p>True.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.18: Home member state</td>
<td id="_TEMPLATE_F.18" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokenHomeMemberState" contextRef="_ctx1" id="TEMPLATE_F.18" escape="false"><div style="color:#0066DF;"><p>Luxembourg</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">F.19: Host member states</td>
<td id="_TEMPLATE_F.19" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokenHostMemberStates" contextRef="_ctx1" id="TEMPLATE_F.19" escape="false"><div style="color:#0066DF;"><p>Austria, Belgium, Bulgaria, Croatia, Republic of Cyprus, Czechia, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Liechtenstein, Lithuania, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden.</p>
</div></ix:nonNumeric></td>
</tr>
<tr><td colspan="2" style="color:#FFF;height:20px;border-width:0;"/></tr>
<tr><td colspan="2" style="text-align:center;background-color:#0066DF;color:white;font-weight:bold;padding:10px;"><a id="Part_G_-_Information_on_the_Rights_and_Obligations_attached_to_the_Crypto-Assets">Part G - Information on the Rights and Obligations attached to the Crypto-Assets</a></td></tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.1: Purchaser rights and obligations</td>
<td id="_TEMPLATE_G.1" style="color:#0066DF;"><ix:nonNumeric name="mica:InformationAboutPurchaserRightsAndObligationsExplanatory" contextRef="_ctx1" id="TEMPLATE_G.1" escape="false"><div style="color:#0066DF;"><p>Purchasers of the $CHIP token do not receive ownership rights, voting rights, or rights to share in profits in any legal entity or unincorporated association. The token does not entitle holders to receive payments, additional tokens, interest, or other considerations by virtue of holding the token.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.2: Exercise of rights and obligations</td>
<td id="_TEMPLATE_G.2" style="color:#0066DF;"><ix:nonNumeric name="mica:ExerciseOfRightsAndObligationExplanatory" contextRef="_ctx1" id="TEMPLATE_G.2" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.3: Conditions for modifications of rights and obligations</td>
<td id="_TEMPLATE_G.3" style="color:#0066DF;"><ix:nonNumeric name="mica:InformationAboutConditionsForModificationsOfRightsAndObligationsExplanatory" contextRef="_ctx1" id="TEMPLATE_G.3" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.4: Future public offers</td>
<td id="_TEMPLATE_G.4" style="color:#0066DF;"><ix:nonNumeric name="mica:InformationAboutFuturePublicOffersExplanatory" contextRef="_ctx1" id="TEMPLATE_G.4" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.5: Issuer retained other token</td>
<td id="_TEMPLATE_G.5" style="color:#0066DF;"><ix:nonNumeric name="mica:NumberOfIssuersRetainedOtherTokens" contextRef="_ctx1" id="TEMPLATE_G.5" escape="false"><div style="color:#0066DF;"><p>5,444,000,000</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.6: Utility token classification</td>
<td id="_TEMPLATE_G.6" style="color:#0066DF;"><ix:nonNumeric name="mica:UtilityTokenClassificationForOtherTokenIndicator" contextRef="_ctx1" id="TEMPLATE_G.6" escape="false"><div style="color:#0066DF;"><p>FALSE</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.7: Key features of goods or services utility tokens</td>
<td id="_TEMPLATE_G.7" style="color:#0066DF;"><ix:nonNumeric name="mica:KeyFeaturesOfGoodsAndServicesOfUtilityTokensExplanatory" contextRef="_ctx1" id="TEMPLATE_G.7" escape="false"><div style="color:#0066DF;"><p>Not applicable as CHIP is not a utility token.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.8: Utility tokens redemption</td>
<td id="_TEMPLATE_G.8" style="color:#0066DF;"><ix:nonNumeric name="mica:UtilityTokensRedemptionExplanatory" contextRef="_ctx1" id="TEMPLATE_G.8" escape="false"><div style="color:#0066DF;"><p>Not applicable as CHIP is not a utility token.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.9: Non-trading request</td>
<td id="_TEMPLATE_G.9" style="color:#0066DF;"><ix:nonNumeric name="mica:NontradingRequestIndicatorRelatedToOtherTokens" contextRef="_ctx1" id="TEMPLATE_G.9" escape="false"><div style="color:#0066DF;"><p>False</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.10: Other tokens purchase or sale modalities</td>
<td id="_TEMPLATE_G.10" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokensPurchaseOrSaleModalitiesExplanatory" contextRef="_ctx1" id="TEMPLATE_G.10" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.11: Other tokens transfer restrictions</td>
<td id="_TEMPLATE_G.11" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokensTransferRestrictionsExplanatory" contextRef="_ctx1" id="TEMPLATE_G.11" escape="false"><div style="color:#0066DF;"><p>$CHIP tokens are subject to transfer restrictions primarily through lock-up and vesting schedules for certain allocations:</p>
<p>ICO: 7% of total supply sold at TGE; fully unlocked at TGE; no restrictions; distributed via ICO partner platform.</p>
<p>Airdrop: 3% of total supply; fully unlocked at TGE; no restrictions; distributed via airdrop smart contract.</p>
<p>Team: ~24% of total supply; subject to 1-year cliff followed by 3-year linear vesting (33% per year); tokens cannot be transferred until vested; allocation for team members; managed via vesting smart contract.</p>
<p>Investors: ~29% of total supply; subject to 1-year cliff followed by 3-year linear vesting; tokens cannot be transferred until vested; distributed via vesting smart contract.</p>
<p>Larger Liquidity Providers / Ecosystem Rewards: 7.5% of total supply; 2.5% unlocked 8 months from TGE, remaining 5% subject to 1-year cliff and 3-year unlock; no direct benefit to team or insiders; distributed via vesting smart contract.</p>
<p>Foundation Reserve: ~29% of total supply; 10% fully unlocked at TGE for liquidity purposes; remaining 20.64% subject to 1-year cliff and 3-year unlock; tokens held in Foundation multisig under Security Council control; used for grants, incentives, and service provider compensation.</p>
<p>General Rules: Tokens cannot be staked or transferred until fully vested. No additional peer-to-peer transfer restrictions exist beyond the vesting and lock-up schedules</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.12: Supply adjustment protocols</td>
<td id="_TEMPLATE_G.12" style="color:#0066DF;"><ix:nonNumeric name="mica:SupplyAdjustmentProtocolsIndicator" contextRef="_ctx1" id="TEMPLATE_G.12" escape="false"><div style="color:#0066DF;"><p>False</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.13: Supply adjustment mechanisms</td>
<td id="_TEMPLATE_G.13" style="color:#0066DF;"><ix:nonNumeric name="mica:SupplyAdjustmentMechanismsExplanatory" contextRef="_ctx1" id="TEMPLATE_G.13" escape="false"><div style="color:#0066DF;"><p>There are no supply adjustment protocols.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.14: Token value protection schemes</td>
<td id="_TEMPLATE_G.14" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokenValueProtectionSchemesIndicator" contextRef="_ctx1" id="TEMPLATE_G.14" escape="false"><div style="color:#0066DF;"><p>False</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.15: Token value protection schemes description</td>
<td id="_TEMPLATE_G.15" style="color:#0066DF;"><ix:nonNumeric name="mica:DescriptionOfOtherTokenValueProtectionSchemesExplanatory" contextRef="_ctx1" id="TEMPLATE_G.15" escape="false"><div style="color:#0066DF;"><p>There is no protection scheme available.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.16: Compensation schemes</td>
<td id="_TEMPLATE_G.16" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokenCompensationSchemesIndicator" contextRef="_ctx1" id="TEMPLATE_G.16" escape="false"><div style="color:#0066DF;"><p>False</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.17: Compensation schemes description</td>
<td id="_TEMPLATE_G.17" style="color:#0066DF;"><ix:nonNumeric name="mica:DescriptionOfOtherTokenCompensationSchemesExplanatory" contextRef="_ctx1" id="TEMPLATE_G.17" escape="false"><div style="color:#0066DF;"><p>There are no compensation schemes.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.18: Applicable law</td>
<td id="_TEMPLATE_G.18" style="color:#0066DF;"><ix:nonNumeric name="mica:ApplicableLawForOtherTokenExplanatory" contextRef="_ctx1" id="TEMPLATE_G.18" escape="false"><div style="color:#0066DF;"><p>British Virgin Islands.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">G.19: Competent court</td>
<td id="_TEMPLATE_G.19" style="color:#0066DF;"><ix:nonNumeric name="mica:CompetentCourtForOtherTokenExplanatory" contextRef="_ctx1" id="TEMPLATE_G.19" escape="false"><div style="color:#0066DF;"><p>British Virgin Islands.</p>
</div></ix:nonNumeric></td>
</tr>
<tr><td colspan="2" style="color:#FFF;height:20px;border-width:0;"/></tr>
<tr><td colspan="2" style="text-align:center;background-color:#0066DF;color:white;font-weight:bold;padding:10px;"><a id="Part_H_-_Information_on_the_underlying_technology">Part H - Information on the underlying technology</a></td></tr>
<tr>
<td style="background-color:#92D050; width:30%;">H.1: Distributed ledger technology (DTL)</td>
<td id="_TEMPLATE_H.1" style="color:#0066DF;"><ix:nonNumeric name="mica:DistributedLedgerTechnologyForOtherTokenExplanatory" contextRef="_ctx1" id="TEMPLATE_H.1" escape="false"><div style="color:#0066DF;"><p>The $CHIP token is implemented as a smart contract on the Ethereum blockchain, a public, permissionless, and decentralized ledger technology (DLT). Ethereum provides a decentralized environment for secure, transparent, and immutable record-keeping of token issuance, transfers, and ownership. The network uses the Ethereum Virtual Machine (EVM) to execute smart contracts, ensuring automated enforcement of token logic and compliance with the defined token standards (e.g., ERC-20 or ERC-721). The use of Ethereum enables global accessibility, interoperability with other Ethereum-based assets and services, and real-time verification of all token-related transactions.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">H.2: Protocols and technical standards</td>
<td id="_TEMPLATE_H.2" style="color:#0066DF;"><ix:nonNumeric name="mica:ProtocolsAndTechnicalStandardsForOtherTokenExplanatory" contextRef="_ctx1" id="TEMPLATE_H.2" escape="false"><div style="color:#0066DF;"><p>The CHIP token ($CHIP) is an Ethereum-based ERC-20 governance token operating within the USD.AI Protocol, a permissionless, decentralized lending platform. Collateralization includes tokenized GPUs represented via ERC-721 documents of title under the CALIBER legal framework. USD.AI leverages smart contracts for on-chain loan origination, staking, governance, risk curation (FiLo positions), and Queue Extractable Value (QEV) mechanisms for liquidity management. Integration with the M^0 Protocol and PYUSD provides programmable stablecoin infrastructure with US Treasury-backed collateral, T+0 redemption finality, and deep on-chain liquidity. The protocol supports major wallets (Coinbase Wallet, Binance Wallet, OKX Wallet, Coin98) and uses LayerZero for cross-chain messaging and bridging, ensuring scalability, interoperability, and secure on-chain operations.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">H.3: Technology used</td>
<td id="_TEMPLATE_H.3" style="color:#0066DF;"><ix:nonNumeric name="mica:InformationAboutTechnologyUsedForOtherTokenExplanatory" contextRef="_ctx1" id="TEMPLATE_H.3" escape="false"><div style="color:#0066DF;"><p>The CHIP token ($CHIP) is held, stored, and transferred on the Ethereum blockchain using ERC-20 smart contracts. Wallets compatible with Ethereum (e.g., MetaMask, Coinbase Wallet, Binance Wallet) can securely store and interact with $CHIP. Transfers are executed via Ethereum transactions or LayerZero-enabled cross-chain messaging for interoperability across supported EVM-compatible networks. Custody can be self-managed by users or facilitated by compliant third-party custodians supporting ERC-20 assets.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">H.4: Consensus mechanism</td>
<td id="_TEMPLATE_H.4" style="color:#0066DF;"><ix:nonNumeric name="mica:ConsensusMechanismForOtherTokenExplanatory" contextRef="_ctx1" id="TEMPLATE_H.4" escape="false"><div style="color:#0066DF;"><p>The CHIP token ($CHIP) operates on the Ethereum blockchain, which currently uses a Proof-of-Stake (PoS) consensus mechanism. Transactions and token transfers are validated by staked Ethereum validators who propose and attest blocks. This ensures network security, finality, and decentralization while enabling efficient, energy-conscious processing of $CHIP transactions.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">H.5: Incentive mechanisms and applicable fees</td>
<td id="_TEMPLATE_H.5" style="color:#0066DF;"><ix:nonNumeric name="mica:IncentiveMechanismsAndApplicableFeesForOtherTokenExplanatory" contextRef="_ctx1" id="TEMPLATE_H.5" escape="false"><div style="color:#0066DF;"><p>The CHIP token relies entirely on the security and incentive structure of the Ethereum blockchain and does not introduce a separate or proprietary consensus mechanism. Transactions involving CHIP are subject to the standard Ethereum gas fee model, with fees paid by users and distributed to Ethereum validators in accordance with the network’s protocol rules.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">H.6: Use of distributed ledger technology</td>
<td id="_TEMPLATE_H.6" style="color:#0066DF;"><ix:nonNumeric name="mica:UseOfDistributedLedgerTechnologyIndicatorForOtherToken" contextRef="_ctx1" id="TEMPLATE_H.6" escape="false"><div style="color:#0066DF;"><p>False.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">H.7: DLT functionality description</td>
<td id="_TEMPLATE_H.7" style="color:#0066DF;"><ix:nonNumeric name="mica:DescriptionOfDLTFunctionalityForOtherTokenExplanatory" contextRef="_ctx1" id="TEMPLATE_H.7" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">H.8: Audit</td>
<td id="_TEMPLATE_H.8" style="color:#0066DF;"><ix:nonNumeric name="mica:AuditIndicatorForOtherToken" contextRef="_ctx1" id="TEMPLATE_H.8" escape="false"><div style="color:#0066DF;"><p>True.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">H.9: Audit outcome</td>
<td id="_TEMPLATE_H.9" style="color:#0066DF;"><ix:nonNumeric name="mica:AuditOutcomeForOtherTokenExplanatory" contextRef="_ctx1" id="TEMPLATE_H.9" escape="false"><div style="color:#0066DF;"><p>USD.AI is a permissionless lending protocol and stablecoin system designed to finance AI infrastructure, with a strong focus on transparency, risk mitigation, and robust technical controls. The protocol is overcollateralized, primarily by short-dated U.S. Treasury Bills and tokenized GPU assets.</p>
<p>Key findings from technical and security reviews include:</p>
<ul>
<li>Multiple independent audits have been conducted, with recent reports available from Cantina and KTL (May 2025), covering smart contract security and protocol logic. The project also maintains an active bug bounty program to incentivize ongoing vulnerability discovery and remediation.</li>
<li>No adverse media or public records of major security incidents have been found in the provided context.</li>
</ul>
<p>Risk mitigation and remediation measures include:</p>
<ul>
<li>A conservative (70%-80%) loan-to-value (LTV) ratio to buffer against asset value fluctuations and defaults.</li>
<li>Regular amortization schedules and a market-based Queue Extractable Value (QEV) mechanism to manage liquidity and redemption pressure.</li>
<li>A dedicated insurance fund and a robust legal framework (CALIBER) for collateralization, ensuring enforceable on-chain property rights and regulatory compliance.</li>
<li>Comprehensive onboarding diligence, ongoing software oversight, and community governance to ensure long-term sustainability and rapid response to emerging risks.<br />
-Loans may feature a first loss postion or residual value insurance to protect lenders in case of default</li>
</ul>
<p>Transparency is further enhanced by a public proof-of-reserves dashboard, allowing investors to verify underlying collateral, loan health, and yield sources in real time.</p>
<p>These measures collectively support the robustness and reliability of the USDai protocol, providing multiple layers of protection and transparency for investors.</p>
</div></ix:nonNumeric></td>
</tr>
<tr><td colspan="2" style="color:#FFF;height:20px;border-width:0;"/></tr>
<tr><td colspan="2" style="text-align:center;background-color:#0066DF;color:white;font-weight:bold;padding:10px;"><a id="Part_I_-_Information_on_Risks">Part I - Information on Risks</a></td></tr>
<tr>
<td style="background-color:#92D050; width:30%;">I.1: Offer-related risks</td>
<td id="_TEMPLATE_I.1" style="color:#0066DF;"><ix:nonNumeric name="mica:DescriptionOfOfferrelatedRisksForOtherTokenExplanatory" contextRef="_ctx1" id="TEMPLATE_I.1" escape="false"><div style="color:#0066DF;"><p>Legal/Regulatory Risk:<br />
The protocol uses tokenized documents of title for GPU collateral, designed to comply with UCC Article 12 and structured to avoid classification as securities. However, regulatory interpretations may evolve, and there is no guarantee that future legal or regulatory changes will not impact the protocol or its participants.</p>
<p>AML/KYC Risk:<br />
No public evidence found about specific AML/KYC procedures or requirements for participants in the protocol. The provided context does not include evidence of comprehensive AML/KYC controls.</p>
<p>Technical/Operational Risk:<br />
USDai is a permissionless protocol with complex smart contract interactions, including collateralization, lending, and redemption mechanisms. Technical failures, smart contract vulnerabilities, or operational errors could result in loss of funds or protocol malfunction.</p>
<p>Tokenomics/Vesting Risk:<br />
A significant portion of $CHIP tokens allocated to the team, investors, ecosystem incentives, and the Foundation is subject to lock-up and vesting schedules, which may create future supply overhang as tokens gradually unlock and potentially impact market price and liquidity. Conversely, tokens that are fully unlocked at the Token Generation Event, such as ICO and airdrop allocations, may be subject to immediate selling pressure, increasing short-term price volatility.</p>
<p>Governance/Centralization Risk:<br />
Governance is controlled by the $CHIP token, which allows holders to vote on protocol upgrades and underwriting standards. Centralization risks may arise if governance tokens are concentrated among a small group, potentially impacting protocol decisions and risk management.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">I.2: Issuer-related risks</td>
<td id="_TEMPLATE_I.2" style="color:#0066DF;"><ix:nonNumeric name="mica:DescriptionOfIssuerrelatedRisksForOtherTokenExplanatory" contextRef="_ctx1" id="TEMPLATE_I.2" escape="false"><div style="color:#0066DF;"><p>Not applicable, as the issuer is the same as the offeror.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">I.3: Other tokens-related risks</td>
<td id="_TEMPLATE_I.3" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherTokensrelatedRisksExplanatory" contextRef="_ctx1" id="TEMPLATE_I.3" escape="false"><div style="color:#0066DF;"><p>Legal/Regulatory Risk: The protocol leverages a legal framework (CALIBER) for tokenizing GPU assets, aiming for compliance with UCC Article 12 for &quot;Controllable Electronic Records.&quot; The ERC721 tokens represent enforceable onchain property rights but are not connected to cash flows or fractionalized, and are designed to be non-securities. However, regulatory interpretations may evolve, and full AML/KYC procedures are forthcoming.</p>
<p>AML/Privacy Risk: Details on AML/KYC procedures are not yet available, indicating potential uncertainty regarding anti-money laundering and privacy compliance at this stage.</p>
<p>Technical/Security Risk: The protocol is decentralized and permissionless, with smart contract audit reports and penetration testing results not yet confirmed as available. This introduces potential technical and security risks until such audits are completed and published.</p>
<p>Governance Risk: Governance includes updates to curators, interest rate models, collateral types, and a tokenholder fee switch, as well as broader improvement proposals (UIPs) with a multi-stage voting process. Governance decisions could impact protocol parameters and risk exposure.</p>
<p>Listings Risk: No specific information on exchange or platform listings is provided in the context, so risks related to secondary market access or delistings cannot be assessed from the available information.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">I.4: Project implementation-related risks</td>
<td id="_TEMPLATE_I.4" style="color:#0066DF;"><ix:nonNumeric name="mica:ProjectImplementationrelatedRisksExplanatory" contextRef="_ctx1" id="TEMPLATE_I.4" escape="false"><div style="color:#0066DF;"><p>Technical risks include potential delays in the development and deployment of the protocol, as the system relies on novel mechanisms such as the CALIBER legal framework for tokenizing GPU assets and the Queue Extractable Value (QEV) redemption mechanism. The protocol's onchain, permissionless, and decentralized design, while reducing reliance on oracles, may introduce unforeseen technical challenges.</p>
<p>Operational and resource risks stem from the need for effective coordination among team members and partners, particularly USD.AI Foundation and its warehouse partners, who are responsible for issuing tokenized documents of title. Resource constraints could impact the timely issuance and management of these assets.</p>
<p>Third-party dependency risks are present due to reliance on USD.AI Foundation for asset tokenization and on warehouse partners for physical custody and title issuance. Any failure or delay from these parties could hinder protocol operations.</p>
<p>Market and liquidity risks include the possibility of insufficient liquidity for redemptions, especially during periods of high utilization. The QEV mechanism is designed to mitigate exit spirals, but its effectiveness in extreme market conditions remains unproven.</p>
<p>Legal and compliance risks arise from the use of tokenized documents of title under the CALIBER framework, which aims for compliance with UCC Article 12. However, evolving regulatory interpretations or enforcement actions could impact the protocol's operations or asset classification.</p>
<p>Governance and tokenomics risks include potential misalignment of incentives among $CHIP holders, underwriters, and depositors. The protocol's governance structure, which allows for updates to curators, interest rate models, and collateral types, may be subject to coordination challenges or governance attacks. Token unlock schedules for team and investors could also introduce supply shocks or affect market stability.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">I.5: Technology-related risks</td>
<td id="_TEMPLATE_I.5" style="color:#0066DF;"><ix:nonNumeric name="mica:DescriptionOfTechnologyrelatedRisksForOtherTokenExplanatory" contextRef="_ctx1" id="TEMPLATE_I.5" escape="false"><div style="color:#0066DF;"><p>Smart Contracts: USD.AI operates entirely onchain and permissionless, with smart contracts handling lending, collateralization, and redemption. The protocol is designed to be oracle-less, reducing reliance on external data feeds, and uses ERC721 tokens for collateral representation. Smart contracts have undergone multiple audits by Cantina and others, with reports available for review.</p>
<p>Cross-Chain: USDai and sUSDai are available as LayerZero OFTs (Omnichain Fungible Tokens) on multiple EVM chains, using LayerZero for cross-chain messaging. This introduces dependencies on LayerZero’s security and the underlying chains’ consensus mechanisms.</p>
<p>Scalability: The protocol is deployed on Arbitrum, an Ethereum Layer 2 solution using optimistic rollups to improve scalability and cost-efficiency. This allows for higher throughput and lower fees compared to Ethereum mainnet.</p>
<p>Wallet/Privacy: USD.AI supports integration with major wallets such as Coinbase Wallet, Binance Wallet, OKX Wallet, and Coin98 Wallet. There is no mention of privacy-preserving features; standard EVM wallet privacy limitations apply.</p>
<p>L2 Dependencies: USD.AI relies on Arbitrum for scalability and LayerZero for cross-chain operations, making it dependent on the security and uptime of these Layer 2 and interoperability solutions.</p>
<p>Audits/Security: Multiple smart contract audits have been conducted by Cantina, with reports dated from June 2023 to May 2025. The protocol also lists security partners such as Cantina, Spearbit, and Immunefi, indicating ongoing security oversight and bug bounty programs.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">I.6: Mitigation measures</td>
<td id="_TEMPLATE_I.6" style="color:#0066DF;"><ix:nonNumeric name="mica:MitigationMeasuresForTechnologyRiskForOtherTokenExplanatory" contextRef="_ctx1" id="TEMPLATE_I.6" escape="false"><div style="color:#0066DF;"><p><strong>1. Smart Contract Risk:</strong><br />
USD.AI employs a permissionless, onchain protocol architecture, similar to Aave, which reduces centralized points of failure. The protocol uses a risk register and ongoing software oversight to monitor and address technical risks. Additionally, the protocol is designed to be decentralized and oracle-less, which can reduce attack surfaces related to external data feeds.</p>
<p><strong>2. Oracle Risk:</strong><br />
USD.AI is designed to be oracle-less for its core lending and redemption mechanisms, which eliminates the risk of oracle manipulation for most protocol operations. Where price oracles are required (e.g., for asset pricing in lending pools), Chainlink oracles are used, and the protocol provides interfaces for price verification.</p>
<p><strong>3. Redemption/Peg Risk:</strong><br />
USD.AI uses a Queue Extractable Value (QEV) mechanism to manage redemption liquidity and prevent exit spirals. Redemptions are placed in a global queue, and users can bid for priority, turning redemption pressure into a source of protocol yield. This market-driven queue system is designed to stabilize liquidity and compensate long-term stakers.</p>
<p><strong>4. Liquidation/Default Risk:</strong><br />
Loans are overcollateralized, and underwriters must retain a junior (first-loss) position, aligning their incentives with depositors. In the event of default, first-loss depositors are impaired before sUSDai holders, providing a buffer. The protocol also maintains an insurance fund and enforces a 70% loan-to-value ratio to further mitigate default risk.</p>
<p><strong>5. Governance Risk:</strong><br />
Governance is structured with a multi-stage proposal process (temperature check, consensus check, and formal proposal) and community oversight of underwriter and asset selection. This is intended to ensure robust, transparent decision-making and reduce the risk of governance capture.</p>
<p><strong>6. Custody/Key Management Risk:</strong><br />
The protocol currently uses multisig wallets for administrative operations, with plans to transition to onchain, governance-driven strategies. This approach is intended to reduce single points of failure and improve operational security.</p>
<p><strong>7. Cross-Chain/Bridge Risk:</strong><br />
USDai and sUSDai support omnichain token transfers using a burn/mint model, with bridge operations managed by a designated admin role. LayerZero is supported for messaging, and the protocol uses dedicated contracts for secure cross-chain operations.</p>
<p><strong>Limitations:</strong><br />
No public evidence was found in the provided context regarding specific mitigations for certain risks such as detailed key management procedures, third-party audits, or explicit bug bounty programs.</p>
</div></ix:nonNumeric></td>
</tr>
<tr><td colspan="2" style="color:#FFF;height:20px;border-width:0;"/></tr>
<tr><td colspan="2" style="text-align:center;background-color:#0066DF;color:white;font-weight:bold;padding:10px;"><a id="Part_J_–_Information_on_the_sustainability_indicators_in_relation_to_adverse_impact_on_the_climate_and_other_environment-related_adverse_impacts">Part J – Information on the sustainability indicators in relation to adverse impact on the climate and other environment-related adverse impacts</a></td></tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.1: Name</td>
<td id="_TEMPLATE_S.1" style="color:#0066DF;"><ix:nonNumeric name="mica:Name" contextRef="_ctx1" id="TEMPLATE_S.1" escape="false"><div style="color:#0066DF;"><p>Genesys Protocol Holdings Ltd.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.2: Relevant legal entity identifier</td>
<td id="_TEMPLATE_S.2" style="color:#0066DF;"><ix:nonNumeric name="mica:RelevantLegalEntityIdentifier" contextRef="_ctx1" id="TEMPLATE_S.2" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.3: Name of the crypto-asset</td>
<td id="_TEMPLATE_S.3" style="color:#0066DF;"><ix:nonNumeric name="mica:NameOfCryptoAssetSustainability" contextRef="_ctx1" id="TEMPLATE_S.3" escape="false"><div style="color:#0066DF;"><p>CHIP</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.4: Consensus mechanism</td>
<td id="_TEMPLATE_S.4" style="color:#0066DF;"><ix:nonNumeric name="mica:ConsensusMechanismSustainabilityExplanatory" contextRef="_ctx1" id="TEMPLATE_S.4" escape="false"><div style="color:#0066DF;"><p>Token - therefore, no consensus mechanism.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.5: Incentive mechanisms and applicable fees</td>
<td id="_TEMPLATE_S.5" style="color:#0066DF;"><ix:nonNumeric name="mica:IncentiveMechanismsAndApplicableFeesSustainabilityExplanatory" contextRef="_ctx1" id="TEMPLATE_S.5" escape="false"><div style="color:#0066DF;"><p>Tokens do not have an own consensus mechanism, but rely on the consensus mechanism of one or multiple underlying crypto-asset networks. Depending on the token design, incentive mechanisms arise from the utility, scarcity, or governance rights.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.6: Beginning of period to which disclosed information relates</td>
<td id="_TEMPLATE_S.6" style="color:#0066DF;"><ix:nonNumeric name="mica:BeginningOfPeriodToWhichDisclosedInformationRelates" contextRef="_ctx1" id="TEMPLATE_S.6" escape="false"><div style="color:#0066DF;"><p>2025-11-13.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.7: End of period to which disclosed information relates</td>
<td id="_TEMPLATE_S.7" style="color:#0066DF;"><ix:nonNumeric name="mica:EndOfPeriodToWhichDisclosedInformationRelates" contextRef="_ctx1" id="TEMPLATE_S.7" escape="false"><div style="color:#0066DF;"><p>2025-11-26.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.8: Energy consumption</td>
<td id="_TEMPLATE_S.8" style="color:#0066DF;"><ix:nonNumeric name="mica:EnergyConsumption" contextRef="_ctx1" id="TEMPLATE_S.8" escape="false"><div style="color:#0066DF;"><p>27.00077</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.9: Energy consumption sources and methodologies</td>
<td id="_TEMPLATE_S.9" style="color:#0066DF;"><ix:nonNumeric name="mica:DescriptionOfEnergyConsumptionSourcesAndMethodologiesExplanatory" contextRef="_ctx1" id="TEMPLATE_S.9" escape="false"><div style="color:#0066DF;"><p>Data provided by CCRI; all indicators are based on a  set of assumptions and thus represent estimates;  methodology description and overview of input  data, external datasets and underlying assumptions available at:<br />
https://carbon-ratings.com/dl/whitepaper-mica methods-2024 and https://docs.mica.api.carbon ratings.com. We do not account for any offsetting of energy consumption or other market-based  mechanism as of today.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.10: Renewable energy consumption</td>
<td id="_TEMPLATE_S.10" style="color:#0066DF;"><ix:nonNumeric name="mica:RenewableEnergyConsumptionPercentage" contextRef="_ctx1" id="TEMPLATE_S.10" escape="false"><div style="color:#0066DF;"><p>Not applicable as the annual energy consumption is less than 500 kWh.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.11: Energy intensity</td>
<td id="_TEMPLATE_S.11" style="color:#0066DF;"><ix:nonNumeric name="mica:EnergyIntensity" contextRef="_ctx1" id="TEMPLATE_S.11" escape="false"><div style="color:#0066DF;"><p>Not applicable as the annual energy consumption is less than 500 kWh.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.12: Scope 1 DLT GHG emissions - controlled</td>
<td id="_TEMPLATE_S.12" style="color:#0066DF;"><ix:nonNumeric name="mica:Scope1DLTGHGEmissionsControlled" contextRef="_ctx1" id="TEMPLATE_S.12" escape="false"><div style="color:#0066DF;"><p>Not applicable as the annual energy consumption is less than 500 kWh.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.13: Scope 2 DLT GHG emissions - purchased</td>
<td id="_TEMPLATE_S.13" style="color:#0066DF;"><ix:nonNumeric name="mica:Scope2DLTGHGEmissionsPurchased" contextRef="_ctx1" id="TEMPLATE_S.13" escape="false"><div style="color:#0066DF;"><p>Not applicable as the annual energy consumption is less than 500 kWh.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.14: GHG intensity</td>
<td id="_TEMPLATE_S.14" style="color:#0066DF;"><ix:nonNumeric name="mica:GHGIntensity" contextRef="_ctx1" id="TEMPLATE_S.14" escape="false"><div style="color:#0066DF;"><p>Not applicable as the annual energy consumption is less than 500 kWh.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.15: Key energy sources and methodologies</td>
<td id="_TEMPLATE_S.15" style="color:#0066DF;"><ix:nonNumeric name="mica:DescriptionOfKeyEnergySourcesAndMethodologiesExplanatory" contextRef="_ctx1" id="TEMPLATE_S.15" escape="false"><div style="color:#0066DF;"><p>Not applicable as the annual energy consumption is less than 500 kWh.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.16: Key GHG sources and methodologies</td>
<td id="_TEMPLATE_S.16" style="color:#0066DF;"><ix:nonNumeric name="mica:DescriptionOfKeyGHGSourcesAndMethodologiesExplanatory" contextRef="_ctx1" id="TEMPLATE_S.16" escape="false"><div style="color:#0066DF;"><p>Not applicable as the annual energy consumption is less than 500 kWh.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.17: Energy mix</td>
<td id="_TEMPLATE_S.17" style="color:#0066DF;"><ix:nonNumeric name="mica:EnergyMixPercentage" contextRef="_ctx1" id="TEMPLATE_S.17" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.18: Energy use reduction</td>
<td id="_TEMPLATE_S.18" style="color:#0066DF;"><ix:nonNumeric name="mica:EnergyUseReductionDetailsAbstract" contextRef="_ctx1" id="TEMPLATE_S.18" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.19: Carbon intensity</td>
<td id="_TEMPLATE_S.19" style="color:#0066DF;"><ix:nonNumeric name="mica:CarbonIntensity" contextRef="_ctx1" id="TEMPLATE_S.19" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.20: Scope 3 DLT GHG emissions - value chain</td>
<td id="_TEMPLATE_S.20" style="color:#0066DF;"><ix:nonNumeric name="mica:Scope3DLTGHGEmissionsValueChain" contextRef="_ctx1" id="TEMPLATE_S.20" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.21: GHG emissions reduction targets or commitments</td>
<td id="_TEMPLATE_S.21" style="color:#0066DF;"><ix:nonNumeric name="mica:GHGEmissionsReductionTargetsOrCommitmentsExplanatory" contextRef="_ctx1" id="TEMPLATE_S.21" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.22: Generation of waste electrical and electronic equipment (WEEE)</td>
<td id="_TEMPLATE_S.22" style="color:#0066DF;"><ix:nonNumeric name="mica:GenerationOfWasteElectricalAndElectronicEquipmentWEEE" contextRef="_ctx1" id="TEMPLATE_S.22" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.23: Non-recycled WEEE ratio</td>
<td id="_TEMPLATE_S.23" style="color:#0066DF;"><ix:nonNumeric name="mica:NonrecycledWEEEratio" contextRef="_ctx1" id="TEMPLATE_S.23" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.24: Generation of hazardous waste</td>
<td id="_TEMPLATE_S.24" style="color:#0066DF;"><ix:nonNumeric name="mica:GenerationOfHazardousWaste" contextRef="_ctx1" id="TEMPLATE_S.24" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.25: Generation of waste (all types)</td>
<td id="_TEMPLATE_S.25" style="color:#0066DF;"><ix:nonNumeric name="mica:GenerationOfWasteAllTypes" contextRef="_ctx1" id="TEMPLATE_S.25" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.26: Non-recycled waste ratio (all types)</td>
<td id="_TEMPLATE_S.26" style="color:#0066DF;"><ix:nonNumeric name="mica:NonrecycledWasteRatioAllTypes" contextRef="_ctx1" id="TEMPLATE_S.26" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.27: Waste intensity (all types)</td>
<td id="_TEMPLATE_S.27" style="color:#0066DF;"><ix:nonNumeric name="mica:WasteIntensityAllTypes" contextRef="_ctx1" id="TEMPLATE_S.27" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.28: Waste reduction targets or commitments (all types)</td>
<td id="_TEMPLATE_S.28" style="color:#0066DF;"><ix:nonNumeric name="mica:WasteReductionTargetsOrCommitmentsAllTypesExplanatory" contextRef="_ctx1" id="TEMPLATE_S.28" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.29: Impact of the use of equipment on natural resources</td>
<td id="_TEMPLATE_S.29" style="color:#0066DF;"><ix:nonNumeric name="mica:ImpactOfUseOfEquipmentOnNaturalResourcesExplanatory" contextRef="_ctx1" id="TEMPLATE_S.29" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.30: Natural resources use reduction targets or commitments</td>
<td id="_TEMPLATE_S.30" style="color:#0066DF;"><ix:nonNumeric name="mica:NaturalResourcesUseReductionTargetsOrCommitmentsExplanatory" contextRef="_ctx1" id="TEMPLATE_S.30" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.31: Water use</td>
<td id="_TEMPLATE_S.31" style="color:#0066DF;"><ix:nonNumeric name="mica:WaterUse" contextRef="_ctx1" id="TEMPLATE_S.31" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.32: Non recycled water ratio</td>
<td id="_TEMPLATE_S.32" style="color:#0066DF;"><ix:nonNumeric name="mica:NonRecycledWaterRatio" contextRef="_ctx1" id="TEMPLATE_S.32" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.33: Other energy sources and methodologies</td>
<td id="_TEMPLATE_S.33" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherEnergySourcesAndMethodologiesExplanatory" contextRef="_ctx1" id="TEMPLATE_S.33" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.34: Other GHG sources and methodologies</td>
<td id="_TEMPLATE_S.34" style="color:#0066DF;"><ix:nonNumeric name="mica:OtherGHGSourcesAndMethodologiesExplanatory" contextRef="_ctx1" id="TEMPLATE_S.34" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.35: Waste sources and methodologies</td>
<td id="_TEMPLATE_S.35" style="color:#0066DF;"><ix:nonNumeric name="mica:WasteSourcesAndMethodologiesExplanatory" contextRef="_ctx1" id="TEMPLATE_S.35" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
<tr>
<td style="background-color:#92D050; width:30%;">S.36: Natural resources sources and methodologies</td>
<td id="_TEMPLATE_S.36" style="color:#0066DF;"><ix:nonNumeric name="mica:NaturalResourcesSourcesAndMethodologiesExplanatory" contextRef="_ctx1" id="TEMPLATE_S.36" escape="false"><div style="color:#0066DF;"><p>Not applicable.</p>
</div></ix:nonNumeric></td>
</tr>
</table>
</body>
</html>