| [Table 2] Template for white papers for crypto-assets other than asset-referenced tokens or e-money tokens | |||||
| Template for white papers for crypto-assets other than asset-referenced tokens or e-money tokens [abstract] | |||||
| General information | |||||
| 00 Table of content | boolean true | ||||
| 01 Date of notification | date | ||||
| 02 Statement in accordance with Article 6(3) of Regulation (EU) 2023/1114 | boolean true | ||||
| 03 Compliance statement in accordance with Article 6(6) of Regulation (EU) 2023/1114 | boolean true | ||||
| 04 Statement in accordance with Article 6(5), points (a), (b), (c), of Regulation (EU) 2023/1114 | boolean true | ||||
| 05 Statement in accordance with Article 6(5), point (d), of Regulation (EU) 2023/1114 | boolean true | ||||
| 06 Statement in accordance with Article 6(5), points (e) and (f), of Regulation (EU) 2023/1114 | boolean true | ||||
| SUMMARY | |||||
| 07 Warning in accordance with Article 6(7), second subparagraph, of Regulation (EU) 2023/1114 | boolean true | 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. |
|||
| 08 Characteristics of the crypto-asset | textBlock | ||||
| 09 Further information about utility tokens | textBlock | ||||
| 10 Key information about the offer to the public or admission to trading | textBlock | ||||
| Part A - Information about offeror or person seeking admission to trading | |||||
| A.1 Name | N/A | . | |||
| A.2 Legal form | N/A | . | |||
| A.3 Registered address | |||||
| Registered addess | N/A | . | |||
| Country | N/A | . | |||
| Sub-division | N/A | . | |||
| A.4 Head office | |||||
| Head office | N/A | . | |||
| Country | N/A | . | |||
| Sub-division | N/A | . | |||
| A.5 Registration date | N/A | . | |||
| A.6 Legal entity identifier | N/A | . | |||
| A.7 Another identifier required pursuant to applicable national law | N/A | . | |||
| A.8 Contact telephone number | N/A | . | |||
| A.9 E-mail address | N/A | . | |||
| A.10 Response time (days) | N/A | . | |||
| A.11 Parent company | N/A | . | |||
| A.12 Members of the management body | |||||
| Member #1 | N/A | . | |||
| Identity | N/A | . | |||
| Business address | N/A | . | |||
| Function | N/A | . | |||
| A.13 Business activity | N/A | . | |||
| A.14 Parent company business activity | N/A | . | |||
| A.15 Newly established | N/A | . | |||
| A.16 Financial condition for the past three years | N/A | . | |||
| A.17 Financial condition since registration | N/A | . | |||
| Part B - Information about issuer, if different from offeror or person seeking admission to trading | |||||
| B.1 Issuer different from offerror or person seeking admission to trading | boolean | ||||
| B.2 Name | text | ||||
| B.3 Legal form | text | ||||
| B.4 Registered address | |||||
| Registered addess | text | ||||
| Country | enumeration | ||||
| Sub-division | text | ||||
| B.5 Head office | |||||
| Head office | text | ||||
| Country | enumeration | ||||
| Sub-division | text | ||||
| B.6 Registration date | date | ||||
| B.7 Legal entity identifier | LEI | ||||
| B.8 Another identifier required pursuant to applicable national law | text | ||||
| B.9 Parent company | text | ||||
| B.10 Members of the management body | |||||
| Member #1 | id | 1 | |||
| Identity | text | ||||
| Business address | text | ||||
| Function | text | ||||
| B.11 Business activity | textBlock | ||||
| B.12 Parent company business activity | textBlock | ||||
| Part C - Information about the operator of the trading platform in cases where it draws up the crypto-asset white paper and information about other persons drawing the crypto-asset white paper pursuant to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | |||||
| C.1 Name | text | ||||
| C.2 Legal form | text | ||||
| C.3 Registered address | |||||
| Registered address | text | Triq Ghar il-Lembi, Sliema SLM1562, Malta |
|||
| Country | enumeration | ||||
| Sub-division | text | ||||
| C.4 Head office | |||||
| Head office | text | ||||
| Country | enumeration | ||||
| Sub-division | text | ||||
| C.5 Registration date | date | ||||
| C.6 Legal entity identifier | LEI | ||||
| C.7 Another identifier required pursuant to applicable national law | text | ||||
| C.8 Parent company | text | ||||
| C.9 Reason for crypto-asset white paper preparation | textBlock | (MiCA) for the purpose of: - The admission to trading of AIXBT on regulated platforms, starting with the OKX Exchange. OKX Europe Limited as a result of being a licenced CASP endeavours to fulfill the obligations established under MiCA and the respective MFSA guidelines to: - Notify this whitepaper to the MFSA; - Publish the whitepaper publicly; - And ensure its registration in the MiCA register maintained by the European Securities and Markets Authority (ESMA). This whitepaper has been prepared to provide transparent, accurate, and fair information to prospective token holders and regulatory authorities in line with the principles of MiCA. |
|||
| C.10 Members of the management body | |||||
| Member #1 | id | 1 | |||
| Identity | text | ||||
| Business address | text | ||||
| Function | text | ||||
| Member #2 | id | 2 | |||
| Identity | text | ||||
| Business address | text | ||||
| Function | text | ||||
| Member #3 | id | 3 | |||
| Identity | text | ||||
| Business address | text | ||||
| Function | text | ||||
| Member #4 | id | 4 | |||
| Identity | text | ||||
| Business address | text | ||||
| Function | text | ||||
| C.11 Operator business activity | textBlock | ||||
| C.12 Parent company business activity | textBlock | ||||
| C.13 Other persons drawing up the crypto-asset white paper according to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | text | ||||
| C.14 Reason for drawing the white paper by persons referred to in Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | text | ||||
| Member #2 | id | 2 | |||
| C.12 Parent company business activity | N/A | . | |||
| C.13 Other persons drawing up the crypto-asset white paper according to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | N/A | . | |||
| C.14 Reason for drawing the white paper by persons referred to in Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | N/A | . | |||
| Member #3 | id | 3 | |||
| C.12 Parent company business activity | N/A | . | |||
| C.13 Other persons drawing up the crypto-asset white paper according to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | N/A | . | |||
| C.14 Reason for drawing the white paper by persons referred to in Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | N/A | . | |||
| Member #4 | id | 4 | |||
| C.12 Parent company business activity | N/A | . | |||
| C.13 Other persons drawing up the crypto-asset white paper according to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | N/A | . | |||
| C.14 Reason for drawing the white paper by persons referred to in Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | N/A | . | |||
| Part D - Information about other token project | |||||
| D.1 Crypto-asset project name | text | ||||
| D.2 Crypto-asset name | text | ||||
| D.3 Abbreviation | text | ||||
| D.4 Crypto-asset project description | textBlock | ||||
| D.5 Details of all natural or legal persons involved in implementation of crypto-asset project | |||||
| Person #1 | id | 1 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | Jansen Teng | |||
| Business address of person | text | Kuala Lumpur, Malaysia | |||
| Domicile of company | enumeration | ||||
| Person #2 | id | 2 | |||
| Type of person | enumeration | ||||
| Name of person | text | Wee Kee | |||
| Business address of person | text | Kuala Lumpur, Malaysia | |||
| Domicile of company | enumeration | ||||
| Person #3 | id | 3 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | ||||
| Business address of person | text | No information could be identified in regards to this field at the time of drafting this whitepaper. | |||
| Domicile of company | enumeration | ||||
| Person #4 | id | 4 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | Brianna Chang | |||
| Business address of person | text | ||||
| Domicile of company | enumeration | ||||
| Person #5 | id | 5 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | Weixiong Tay | |||
| Business address of person | text | No information could be identified in regards to this field at the time of drafting this whitepaper. | |||
| Domicile of company | enumeration | ||||
| Person #6 | id | 6 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | Khoon Kheng Teh | |||
| Business address of person | text | No information could be identified in regards to this field at the time of drafting this whitepaper. | |||
| Domicile of company | enumeration | ||||
| Person #7 | id | 7 | |||
| Type of person | enumeration | ||||
| Name of person | text | Jae-Sonn | |||
| Business address of person | text | No information could be identified in regards to this field at the time of drafting this whitepaper. | |||
| Domicile of company | enumeration | ||||
| Person #8 | id | 8 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | ||||
| Business address of person | text | No information could be identified in regards to this field at the time of drafting this whitepaper. | |||
| Domicile of company | enumeration | ||||
| Person #9 | id | 9 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | Sally Wang | |||
| Business address of person | text | ||||
| Domicile of company | enumeration | ||||
| Person #10 | id | 10 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | Hanan N. | |||
| Business address of person | text | No information could be identified in regards to this field at the time of drafting this whitepaper. | |||
| Domicile of company | enumeration | ||||
| Person #11 | id | 11 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | Sean Kyu Won Kim | |||
| Business address of person | text | No information could be identified in regards to this field at the time of drafting this whitepaper. | |||
| Domicile of company | enumeration | ||||
| Person #12 | id | 12 | |||
| Type of person | enumeration | ||||
| Name of person | text | Viktor Anchutin | |||
| Business address of person | text | No information could be identified in regards to this field at the time of drafting this whitepaper. | |||
| Domicile of company | enumeration | ||||
| Person #13 | id | 13 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | ||||
| Business address of person | text | No information could be identified in regards to this field at the time of drafting this whitepaper. | |||
| Domicile of company | enumeration | ||||
| Person #14 | id | 14 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | Harry | |||
| Business address of person | text | ||||
| Domicile of company | enumeration | ||||
| Person #15 | id | 15 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | Xie Ong | |||
| Business address of person | text | No information could be identified in regards to this field at the time of drafting this whitepaper. | |||
| Domicile of company | enumeration | ||||
| Person #16 | id | 16 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | Yifei You | |||
| Business address of person | text | No information could be identified in regards to this field at the time of drafting this whitepaper. | |||
| Domicile of company | enumeration | ||||
| Person #17 | id | 17 | |||
| Type of person | enumeration | ||||
| Name of person | text | Stefano Bury | |||
| Business address of person | text | No information could be identified in regards to this field at the time of drafting this whitepaper. | |||
| Domicile of company | enumeration | ||||
| Person #18 | id | 18 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | ||||
| Business address of person | text | No information could be identified in regards to this field at the time of drafting this whitepaper. | |||
| Domicile of company | enumeration | ||||
| Person #19 | id | 19 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | Yujie Chuah | |||
| Business address of person | text | ||||
| Domicile of company | enumeration | ||||
| Person #20 | id | 20 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | Koo Huang | |||
| Business address of person | text | No information could be identified in regards to this field at the time of drafting this whitepaper. | |||
| Domicile of company | enumeration | ||||
| Person #21 | id | 21 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | Kahwai Chooi | |||
| Business address of person | text | No information could be identified in regards to this field at the time of drafting this whitepaper. | |||
| Domicile of company | enumeration | ||||
| Person #22 | id | 22 | |||
| Type of person | enumeration | ||||
| Name of person | text | Matthew T | |||
| Business address of person | text | No information could be identified in regards to this field at the time of drafting this whitepaper. | |||
| Domicile of company | enumeration | ||||
| Person #23 | id | 23 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | ||||
| Business address of person | text | No information could be identified in regards to this field at the time of drafting this whitepaper. | |||
| Domicile of company | enumeration | ||||
| Person #24 | id | 24 | |||
| Type of person | enumeration | Development team | |||
| Name of person | text | Virtuals Protocol | |||
| Business address of person | text | ||||
| Domicile of company | enumeration | Malaysia | |||
| D.6 Utility token classification | boolean | ||||
| D.7 Key features of goods or services for utility token projects | text | ||||
| D.8 Plans for the token | |||||
| Description of past milestones | textBlock | ||||
| Description of future milestones | textBlock | ||||
| D.9 Resource allocation | text | ||||
| D.10 Planned use of collected funds or other tokens | text | ||||
| Part E - Information about offer to public of other tokens or their admission to trading | |||||
| E.1 Public offering or admission to trading | enumeration | ||||
| E.2 Reasons for public offer or admission to trading | textBlock | ||||
| E.3 Fundraising target | |||||
| Target expressed in currency | monetary | EUR | |||
| Target expressed in units | decimal | ||||
| Target expressed in digital token identifier | text | ||||
| E.4 Minimum subscription goals | |||||
| Goals expressed in currency | monetary | EUR | |||
| Goals expressed in units | decimal | ||||
| Goals expressed in digital token identifier | text | ||||
| E.5 Maximum subscription goals | |||||
| Goasl expressed in currency | monetary | EUR | |||
| Goals expressed in units | decimal | ||||
| Goals expressed in digital token identifier | text | ||||
| E.6 Oversubscription acceptance | boolean | ||||
| E.7 Oversubscription allocation | text | ||||
| Issue price details | |||||
| E.8 Issue price | decimal | ||||
| E.9 Official currency determining issue price | enumeration | ||||
| E.9 Any other tokens determining issue price | text | ||||
| E.10 Subscription fee | |||||
| Fee expressed in currency | monetary | EUR | |||
| Fee expressed in units | decimal | ||||
| Fee expressed in digital token identifier | text | ||||
| E.11 Offer price determination method | text | ||||
| E.12 Total number of offered or traded other tokens | integer | ||||
| E.13 Targeted holders | enumeration | ||||
| E.14 Holder restrictions | text | ||||
| E.15 Reimbursement notice | boolean true | ||||
| E.16 Refund mechanism | textBlock | ||||
| E.17 Refund timeline | text | ||||
| E.18 Offer phases | textBlock | ||||
| E.19 Early purchase discount | textBlock | ||||
| E.20 Time-limited offer | boolean | ||||
| E.21 Subscription period beginning | date | ||||
| E.22 Subscription period end | date | ||||
| E.23 Safeguarding arrangements for offered funds or other tokens | textBlock | ||||
| E.24 Payment methods for other token purchase | textBlock | ||||
| E.25 Value transfer methods for reimbursement | textBlock | ||||
| E.26 Right of withdrawal | textBlock | ||||
| E.27 Transfer of purchased other tokens | textBlock | ||||
| E.28 Transfer time schedule | text | ||||
| E.29 Purchaser's technical requirements | textBlock | ||||
| Other token services provider characteristics | |||||
| E.30 Other token service provider (CASP) name | text | ||||
| E.31 CASP identifier | LEI | ||||
| E.32 Placement form | enumeration | ||||
| Trading platforms characteristics | |||||
| E.33 Trading platforms name | text | ||||
| E.34 Trading platforms market identifier code (MIC) | text | ||||
| E.35 Trading platforms access | text | ||||
| E.36 Involved costs | textBlock | ||||
| E.37 Offer expenses | textBlock | ||||
| E.38 Conflicts of interest | textBlock | ||||
| E.39 Applicable law | textBlock | ||||
| E.40 Competent court | textBlock | ||||
| Part F - Information about other tokens | |||||
| F.1 Crypto-asset type | text | ||||
| F.2 Other token functionality | textBlock | ||||
| F.3 Planned application of functionalities | textBlock | ||||
| A description of the characteristics of the other token, including the data necessary for classification of the crypto-asset white paper in the register referred to in Article 109 of Regulation (EU) 2023/1114, as specified in accordance with paragraph 8 of that Article | |||||
| F.4 Type of crypto-asset white paper | enumeration | ||||
| F.5 Type of submission | enumeration | ||||
| F.6 Other token characteristics | textBlock | ||||
| F.7 Commercial name or trading name | text | ||||
| F.8 Website of the issuer | text | ||||
| F.9 Starting date of offer to the public or admission to trading | date | ||||
| F.10 Publication date | date | ||||
| F.11 Any other services provided by the issuer | textBlock | ||||
| F.12 Language or languages of white paper | text | ||||
| 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 | text | ||||
| F.14 Functionally fungible group digital token identifier, where available | text | ||||
| F.15 Voluntary data flag | boolean | ||||
| F.16 Personal data flag | boolean | ||||
| F.17 LEI eligibility | boolean | ||||
| F.18 Home member state | enumeration | ||||
| F.19 Host member states #1 | enumerationSet | ||||
| F.19 Host member states #2 | enumerationSet | ||||
| F.19 Host member states #3 | enumerationSet | ||||
| F.19 Host member states #4 | enumerationSet | ||||
| F.19 Host member states #5 | enumerationSet | ||||
| F.19 Host member states #6 | enumerationSet | ||||
| F.19 Host member states #7 | enumerationSet | ||||
| F.19 Host member states #8 | enumerationSet | ||||
| F.19 Host member states #9 | enumerationSet | ||||
| F.19 Host member states #10 | enumerationSet | ||||
| F.19 Host member states #11 | enumerationSet | ||||
| F.19 Host member states #12 | enumerationSet | ||||
| F.19 Host member states #13 | enumerationSet | ||||
| F.19 Host member states #14 | enumerationSet | ||||
| F.19 Host member states #15 | enumerationSet | ||||
| F.19 Host member states #16 | enumerationSet | ||||
| F.19 Host member states #17 | enumerationSet | ||||
| F.19 Host member states #18 | enumerationSet | ||||
| F.19 Host member states #19 | enumerationSet | ||||
| F.19 Host member states #20 | enumerationSet | ||||
| F.19 Host member states #21 | enumerationSet | ||||
| F.19 Host member states #22 | enumerationSet | ||||
| F.19 Host member states #23 | enumerationSet | ||||
| F.19 Host member states #24 | enumerationSet | ||||
| F.19 Host member states #25 | enumerationSet | ||||
| F.19 Host member states #26 | enumerationSet | ||||
| F.19 Host member states #27 | enumerationSet | ||||
| F.19 Host member states #28 | enumerationSet | ||||
| F.19 Host member states #29 | enumerationSet | ||||
| F.19 Host member states #30 | enumerationSet | ||||
| Part G - Information on rights and obligations attached to other tokens | |||||
| G.1 Purchaser rights and obligations | textBlock | ||||
| G.2 Exercise of rights and obligations | textBlock | ||||
| G.3 Conditions for modifications of rights and obligations | textBlock | ||||
| G.4 Future public offers | textBlock | ||||
| G.5 Issuer retained other token | integer | ||||
| G.6 Utility token classification | boolean | ||||
| G.7 Key features of goods or services utility tokens | text | ||||
| G.8 Utility tokens redemption | text | ||||
| G.9 Non-trading request | boolean | ||||
| G.10 Other tokens purchase or sale modalities | text | ||||
| G.11 Other tokens transfer restrictions | text | ||||
| G.12 Supply adjustment protocols | boolean | ||||
| G.13 Supply adjustment mechanisms | text | ||||
| Other token schemes details | |||||
| G.14 Token value protection schemes | boolean | ||||
| G.15 Token value protection schemes description | textBlock | ||||
| G.16 Compensation schemes | boolean | ||||
| G.17 Compensation schemes description | textBlock | ||||
| G.18 Applicable law | textBlock | ||||
| G.19 Competent court | textBlock | ||||
| Part H – Information on underlying technology | |||||
| H.1 Distributed ledger technology (DTL) | text | ||||
| H.2 Protocols and technical standards | text | Ethereum and Base: On these networks, the token adheres to the ERC-20 standard. ERC-20 is the most widely adopted technical standard for fungible tokens on the Ethereum blockchain and EVM-compatible networks like Base. It defines a common set of rules and functions that a token contract must implement, ensuring interoperability with wallets, decentralised exchanges, and other applications within the ecosystem. Solana: On this network, the token is implemented using the Solana Program Library (SPL) Token standard. This is the official and authorised standard for creating and managing fungible and non-fungible tokens on the Solana blockchain. SPL tokens are managed via smart contracts (known as "programs" in Solana) and are designed to leverage Solana's high-throughput, low-latency infrastructure. |
|||
| H.3 Technology used | textBlock | Ethereum: A general-purpose Layer-1 blockchain that supports smart contract execution via the Ethereum Virtual Machine (EVM). The AIXBT token contract is written in Solidity and interacts with the decentralised network of nodes that maintain the ledger. Base: A Layer-2 protocol built using the OP Stack that operates as an optimistic rollup. It processes transactions off-chain in a separate execution environment and then posts compressed transaction data to the Ethereum mainnet. This architecture is designed to provide users with significantly lower transaction fees and faster confirmation times while inheriting the security guarantees of the underlying Ethereum network. Solana: A high-performance Layer-1 blockchain designed for scalability. Its architecture uses Rust-based smart contracts and features a hybrid consensus mechanism that includes Proof-of-History (PoH) to create a verifiable sequence of events, enabling high transaction throughput and sub-second block times. |
|||
| H.4 Consensus mechanism | text | Ethereum and Base: The Ethereum blockchain uses a Proof-of-Stake (PoS) consensus mechanism. In this system, validators are chosen to propose and attest to new blocks based on the amount of ETH they have staked as collateral. This model provides high security and energy efficiency. As a Layer-2, Base does not have its own consensus mechanism; it relies on a centralized sequencer to order transactions but ultimately inherits its security and finality from the Ethereum PoS consensus once transaction data is settled on the Layer-1. Solana: The Solana blockchain uses a hybrid consensus mechanism that combines Proof-of-History (PoH) with Proof-of-Stake (PoS). PoH is not a consensus mechanism itself, but a cryptographic technique that creates a verifiable, time-stamped record of all transactions. This ordered sequence is then passed to the PoS mechanism, where a decentralised network of validators vote to confirm blocks, allowing the network to achieve high throughput while maintaining security. |
|||
| H.5 Incentive mechanisms and applicable fees | text | Ethereum: Validators are incentivised to secure the network by earning rewards in ETH, which are composed of newly issued tokens and priority fees (tips) from users. Users must pay a transaction fee, known as "gas," in ETH to execute any transaction involving the AIXBT token. Base: Users pay transaction fees to the network's sequencer for processing and bundling transactions. These fees are significantly lower than on the Ethereum mainnet. The underlying security is provided by Ethereum's validators, who are incentivised through the PoS mechanism. Solana: Validators are incentivised through a PoS system where they earn rewards in the native token (SOL) for validating transactions and producing blocks. Users must pay a small transaction fee in SOL to transfer AIXBT tokens or interact with related smart contracts. |
|||
| H.6 Use of distributed ledger technology | boolean | ||||
| H.7 DLT functionality description | textBlock | ||||
| Other token audit details | |||||
| H.8 Audit | boolean | ||||
| H.9 Audit outcome | textBlock | ||||
| Part I - Information on risks | |||||
| I.1 Offer-related risks | textBlock | Risks associated with the admission to trading include; Service-related Interruption; Holders may be unable to access the utility due to technical, operation, or regulatory disruptions. Jurisdictional limitations; AIXBT services or token utility may not be available in all jurisdictions, potentially restricting access. Platform Reliance; Access depends on third-party infrastructure (wallets,platforms) and service interruptions or failures may affect token utility. Limited Liability; OKX Europe Limited assumes no responsibility for the issuers project continuation, and token ownership does not confer contractual rights or guarantees. Unexpected Risks: Beyond the risks outlined in this whitepaper, there may be additional risks that are currently unforeseen. It is imperative to note that certain risks may emerge from unforeseen events, changes, or interactions among factors that are difficult to predict. These unexpected risks may significantly and negatively impact the crypto-asset, the project, or the parties involved. |
|||
| I.2 Issuer-related risks | textBlock | Counterparty Risks; Counterparty risks may arise where the issuer relies on third-party service providers or technology partners. Reputational Risks; Adverse media and/or damage or loss of key personnel could negatively affect the ecosystem that the AIXBT token lives on. Competition Risk; The issuer may face increased competition or changes in market conditions that affect its ability to carry out its objectives. Regulatory Risks; The issuer may be subject to investigations, enforcement actions, or change in regulation that affect the tokens legal status in certain jurisdictions. Disclosure Risks; The issuer may not be required to provide financial statements, limiting AIXBT token holders visibility into the financial health status of the issuer/project. Issuer Risks; The information provided is based solely on publicly available sources and does not constitute any form of guarantee or warranty as to its accuracy or completeness. Key Person Risk; The project and/or token's success may rely on a small number of individuals or core team. If these individuals depart from the project, the direction and continuity of the project may be negatively affected in the future. |
|||
| I.3 Other tokens-related risks | textBlock | Utility Risk; The AIXBT tokens utility depends on access to certain services, and any modification or discontinuation of those services could reduce the associated utility of the token. Smart Contract Risk; The AIXBT token may operate through smart contracts that may contain vulnerabilities, even if audited, and upgrades to the protocol or governance changes may affect functionality. Liquidity Risk; Periods of low/limited liquidity may occur, particularly if the demand for the token or its use case decreases, which could have adverse effects on the AIXBT tokens price and future use cases. |
|||
| I.4 Project implementation-related risks | textBlock | Governance Risk; The project may be subject to governance processes that involve on-chain voting or community proposals. Misaligned incentives, low participation, or malicious actors may affect the outcome of governance decisions and disrupt the project's roadmap. Centralisation Risk; Similar to governance risks outlined above, centralisation within the governance process, or validator centralisation could lead to a lack of decentralization within the network, which carries future risks in terms of trust within the project, and also in regards to future roadmaps where plans may not reflect the interests of the broader user base. |
|||
| I.5 Technology-related risks | textBlock | Consensus Failure Risk: A failure in the consensus mechanisms of the Layer-1 blockchains (Ethereum's Proof-of-Stake or Solana's PoS/PoH hybrid) could result in halted transactions, reorganisations, or a loss of network integrity. As the Base network settles on Ethereum, its security is directly dependent on the integrity of Ethereum's consensus. Smart Contract Vulnerabilities: Although the token uses standard smart contract makeups (ERC-20 on Ethereum/Base and SPL on Solana), undetected bugs, exploits, or implementation errors in any of the three separate token contracts could compromise functionality or security. Upgradeability Risk: The AIXBT token exists as three separate contracts on Ethereum, Base, and Solana. If any of these contracts are upgradeable (e.g., via proxy patterns) and controlled by designated "owner" addresses, this introduces central points of failure. Such privileges could be misused by malicious actors or compromised, leading to unilateral changes or loss of funds on that specific network. Third-party Infrastructure Dependency: Interaction with the token or the AIXBT project relies on external infrastructure. This includes, but is not limited to, wallet services (for both EVM and Solana chains), RPC nodes for Ethereum, Base, and Solana, and project-specific APIs. Outages, attacks, or deprecation of these third-party services may interrupt access to token-related services. Interoperability Risk: As the token exists on three separate networks (Ethereum, Base, Solana), moving the token between these chains requires the use of token bridges. These bridges, whether official (like the Base bridge) or third-party, are complex smart contracts that are frequent targets for exploits. A failure, hack, or exploit of a bridge used to transfer AIXBT could result in a significant loss of assets and potentially de-peg the token's value on different chains. Protocol-level Risk: Major protocol-level upgrades, hard forks, or other significant changes to the underlying Ethereum, Base, or Solana blockchains may affect the token. Such events could lead to temporary network instability, compatibility issues with the token contracts, or unexpected token behaviour. Emerging Technology Risk: Advances in computing or undiscovered vulnerabilities in cryptographic algorithms may pose long-term security risks to the blockchains or associated smart contracts. AI Associated Risks: This token integrates AI technology which may result in imperfect or biased outputs due to data and model limitations. AI-driven features inherently involve risks including errors, security vulnerabilities, and regulatory uncertainties, thus users should exercise caution, and conduct independent checks. Sequencing Risk: The version of the token on the Base network relies on a centralised sequencer to process and order transactions before they are submitted to the Ethereum Layer-1. If this sequencer experiences downtime, censors transactions, or is otherwise misused, the ordering, processing, and availability of AIXBT transactions on the Base network may be adversely affected. |
|||
| I.6 Mitigation measures | textBlock | Consensus Failure Risk: Each Layer-1 protocol has robust consensus mechanisms. Ethereum's Proof-of-Stake includes validator incentives, slashing penalties for malicious actors, and finality checkpoints. Its large, globally distributed validator set reinforces decentralisation. Solana's hybrid PoH/PoS mechanism is also secured by a large, global validator set, which is incentivised to act honestly through staking rewards and slashing penalties. The Base network mitigates this risk by relying on the consensus and security of the Ethereum blockchain for the final settlement and integrity of its transactions. Smart Contract Vulnerabilities: The token leverages standardised, widely-used contract models on all networks. On Ethereum and Base, it uses the ERC-20 standard, and the ecosystem encourages open-source code, independent audits, and the use of tested libraries (e.g., OpenZeppelin) to reduce errors. On Solana, it uses the SPL token standard, which is a rigorously audited and standardised framework. Solana smart contracts (programs) are often written in Rust, a language that provides memory safety features, further mitigating common vulnerabilities. Upgradeability Risk: The networks support, but do not enforce, upgradeable contracts. Risks related to upgradeability on all three platforms (Ethereum, Base, and Solana) can be mitigated through standard practices such as implementing time-delay triggers for changes, requiring multi-signature wallet approval for upgrades, or placing contract ownership under the control of a decentralised governance process. Third-party Infrastructure Dependency: The ecosystems of Ethereum, Base, and Solana all support a competitive and decentralised market of infrastructure providers. This includes numerous independent RPC providers, node operators, and decentralised indexing protocols, which reduces reliance on any single third-party data service and mitigates the risk of a central point of failure. Interoperability Risk: Mitigations for cross-chain risk vary by the connection. For transfers between Ethereum and Base, the official Base Bridge provides a native, protocol-secured mechanism. For transfers between EVM chains (Ethereum/Base) and Solana, mitigation relies on using third-party bridges. Best practices involve selecting established, independently audited bridge providers that utilise secure token locking mechanisms and have robust security monitoring. Protocol-level Risk: All three protocols maintain public roadmaps and follow structured governance and update processes. Ethereum's core updates undergo extensive testing and community review. Solana's network upgrades are developed and tested by core developers and the community before being activated by the validator network. Base's development is aligned with the public, open-source OP Stack roadmap, ensuring its evolution is transparent and tied to community-driven standards. Emerging Technology Risk: The core development communities for both Ethereum and Solana actively monitor potential emerging technology threats, including advances in quantum computing. Both ecosystems are actively researching and developing quantum-resistant solutions, and the modular designs of the networks may allow for future cryptographic upgrades if required. |
|||
| Part J - Information on the sustainability indicators in relation to adverse impact on the climate and other environment-related adverse impacts | |||||
| J.1 Adverse impacts on climate and other environment-related adverse impacts | textBlock | ||||
| Mandatory information on principal adverse impacts on the climate and other environment-related adverse impacts of the consensus mechanism | |||||
| General information about adverse impacts | |||||
| S.1 Name | text | ||||
| S.2 Relevant legal entity identifier | text | ||||
| S.3 Name of the crypto-asset | text | ||||
| S.4 Consensus mechanism | text | ||||
| S.5 Incentive mechanisms and applicable fees | text | ||||
| S.6 Beginning of period to which disclosed information relates | date | ||||
| S.7 End of period to which disclosed information relates | date | ||||
| Mandatory key indicator | |||||
| S.8 Energy consumption | energy (kWh) | ||||
| Sources and methodologies | |||||
| S.9 Energy consumption sources and methodologies | textBlock | ||||
| Supplementary information on principal adverse impacts on climate and other environment-related adverse impacts of consensus mechanism | |||||
| Supplementary key indicators | |||||
| S.10 Renewable energy consumption | percent | ||||
| S.11 Energy intensity | energy (kWh) | ||||
| S.12 Scope 1 DLT GHG emissions - controlled | GHG emissions (tCO2e) | ||||
| S.13 Scope 2 DLT GHG emissions - purchased | GHG emissions (tCO2e) | ||||
| S.14 GHG intensity | GHG emissions (tCO2e) | ||||
| Sources and methodologies | |||||
| S.15 Key energy sources and methodologies | textBlock | ||||
| S.16 Key GHG sources and methodologies | textBlock | ||||
| Optional information on principal adverse impacts on the climate and on other environment-related adverse impacts of the consensus mechanism | |||||
| Optional indicators | |||||
| S. 17 Energy mix | percent | ||||
| S.18 Energy use reduction | |||||
| Energy use reduction target (absolute value) | energy (kWh) | ||||
| Energy use reduction target (percentage) | percent | ||||
| S.19 Carbon intensity (kgCO2e/kWh) | decimal | ||||
| S.20 Scope 3 DLT GHG emissions - value chain | GHG emissions (tCO2e) | ||||
| S.21 GHG emissions reduction targets or commitments | textBlock | ||||
| S.22 Generation of waste electrical and electronic equipment (WEEE) | mass (tonnes) | ||||
| S.23 Non-recycled WEEE ratio | percent | ||||
| S.24 Generation of hazardous waste | mass (tonnes) | ||||
| S.25 Generation of waste (all types) | mass (tonnes) | ||||
| S.26 Non-recycled waste ratio (all types) | percent | ||||
| S.27 Waste intensity (all types) | mass (tonnes) | ||||
| S.28 Waste reduction targets or commitments (all types) | textBlock | ||||
| S.29 Impact of use of equipment on natural resources | textBlock | ||||
| S.30 Natural resources use reduction targets or commitments | textBlock | ||||
| S.31 Water use | volume (m3) | ||||
| S.32 Non recycled water ratio | percent | ||||
| Sources and methodologies | |||||
| S.33 Other energy sources and methodologies | textBlock | ||||
| S.34 Other GHG sources and methodologies | textBlock | ||||
| S.35 Waste sources and methodologies | textBlock | ||||
| S.36 Natural resources sources and methodologies | textBlock | ||||