| [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 | ||||
| Member #2 | id | 1 | |||
| Identity | text | Chi Hoi Lai | |||
| Business address | text | Suite 202, 2nd Floor, Eden Plaza, Eden Island, PO Box 1352, Mahe, Seychelles | |||
| Function | text | Chief Commercial Officer | |||
| 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 OKB 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 | ||||
| Name of person | text | ||||
| Business address of person | text | ||||
| Domicile of company | enumeration | ||||
| Person #2 | id | 2 | |||
| Type of person | enumeration | ||||
| Name of person | text | ||||
| Business address of person | text | ||||
| Domicile of company | enumeration | ||||
| Person #3 | id | 3 | |||
| Type of person | enumeration | ||||
| Name of person | text | ||||
| Business address of person | text | ||||
| Domicile of company | enumeration | ||||
| Person #4 | id | 4 | |||
| Type of person | enumeration | ||||
| Name of person | text | ||||
| Business address of person | text | ||||
| Domicile of company | enumeration | ||||
| Person #5 | id | 5 | |||
| Type of person | enumeration | ||||
| Name of person | text | ||||
| Business address of person | text | ||||
| Domicile of company | enumeration | ||||
| Person #6 | id | 6 | |||
| Type of person | enumeration | ||||
| Name of person | text | ||||
| Business address of person | text | ||||
| Domicile of company | enumeration | ||||
| 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 (ERC-20): The OKB token is implemented using the ERC‑20 token standard on the Ethereum blockchain. ERC‑20 is the widely adopted standard for fungible tokens on Ethereum, defining a common interface for token issuance, transfers, and third-party integrations. ERC‑20 tokens are deployed via smart contracts that control total supply, balances, and permissions, and are compatible with Ethereum wallets, DeFi applications, and decentralized exchanges. The standard supports functions such as transfer, approve, mint, and burn, enabling programmable token logic through Ethereum's account-based architecture. X Layer (Native Gas): The OKB token serves as the native gas token on the X Layer network. While X Layer is EVM-equivalent, OKB functions at the protocol level for gas payments rather than solely as a smart contract token. However, wrapped versions or bridged representations on the network typically follow the standard ERC-20 interface to ensure compatibility with dApps and wallets. |
|||
| H.3 Technology used | textBlock | Ethereum: The OKB token is deployed on the Ethereum blockchain using the ERC‑20 token standard. Ethereum is a general-purpose Layer 1 blockchain that supports smart contract execution via the Ethereum Virtual Machine (EVM). The token contract is written in Solidity and interacts with the Ethereum network using RPC-compatible clients. The Ethereum ecosystem enables composability with DeFi, NFT, and DAO infrastructure, and supports programmable token functionality within a Turing-complete environment. X Layer: The OKB token is the native asset of the X Layer, a Layer 2 blockchain built using the Polygon Chain Development Kit (CDK). X Layer utilises Zero-Knowledge (ZK) technology to bundle transactions off-chain and post validity proofs to the Ethereum mainnet. This architecture ensures high throughput and low fees while inheriting the security of Ethereum. The network is EVM-equivalent, allowing developers to deploy existing Ethereum smart contracts without modification. |
|||
| H.4 Consensus mechanism | text | Ethereum: Ethereum uses a Proof-of-Stake (PoS) consensus mechanism. Validators are selected to propose and attest to new blocks based on the amount of ETH they have staked. Blocks are finalized through a checkpoint-based finality system, with strong economic incentives to penalize dishonest behavior. This mechanism supports decentralization, finality, and high security. This consensus model ensures the integrity of the blockchain, including the execution and recording of all associated transactions for the OKB token. X Layer: X Layer operates as a ZK-rollup, which relies on a sequencer to order transactions and generate blocks. These blocks are then cryptographically verified using Zero-Knowledge proofs (validity proofs) which are submitted to the Ethereum Layer 1 for final settlement. This means that while the sequencer orders transactions, the ultimate security and finality of the network are derived from the underlying Ethereum consensus mechanism. |
|||
| H.5 Incentive mechanisms and applicable fees | text | Ethereum: Ethereum validators earn rewards in the native token (ETH) for producing and attesting to blocks. Gas fees are paid in ETH and are required to execute transactions or smart contract calls, including OKB token transfers. Under EIP-1559, a portion of the base fee is burned while the remainder is distributed to validators. Fees vary depending on network congestion and computational complexity of the transaction. X Layer: On the X Layer, users pay transaction fees (gas) in OKB. These fees are used to compensate the network operators (sequencers) for the computational resources required to process transactions and generate ZK-proofs. The fee structure is designed to be significantly lower than Ethereum Layer 1, enabling cost-effective micro-transactions and high-frequency trading. |
|||
| 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, operational, or regulatory disruptions. Jurisdictional Limitations; OKB 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 issuer's 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 OKB 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 token's legal status in certain jurisdictions. Disclosure Risks; The issuer may not be required to provide financial statements, limiting OKB token holders' visibility into the financial health status of the issuer/project. Issuer Risks; The information provided is based solely on available sources and does not constitute any form of guarantee or warranty as to its accuracy or completeness. Additionally, the issuer of the token is an affiliate of OKX Europe Limited, and therefore OKX takes into account any circumstances which may give rise to a conflict of interest, due to the structure and business activities of other entities within the group. In particular, OKX prevents any abuse resulting from concentrated control, management of related-party transactions (including affiliated companies), and transparency of related-party transactions. |
|||
| I.3 Other tokens-related risks | textBlock | Utility Risk; The OKB token 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 OKB 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 OKB token's 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 sequencer 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 blockchains consensus mechanism could result in halted transactions, unexpected behavior, or loss in network integrity. Smart Contract Vulnerabilities; Although the token uses audited or standard smart contract makeups (ERC-20), undetected bugs, exploits, or implementation errors could compromise functionality or security. Upgradeability Risk; if the token or related contracts are upgradeable and have designated "owner" addresses, this introduces a central point of failure, and could be misused by malicious actors. Third-party Infrastructure Dependency; Interaction with the token or project may rely on external infrastructure (APIs, wallet services, off-chain governance voting). Outages or attacks may interrupt access to token-related services. Interoperability Risk; Other chains, bridges, or oracles may experience failures or exploits, which could affect the OKB token's operations. Blockchain-level Risk; Upgrades or forks of the X Layer blockchain itself may affect the token, which could lead to compatibility issues and/or unexpected token behaviour. Emerging Technology Risk; Advances in computing or undiscovered vulnerabilities in cryptographic algorithms may pose long-term security risks to the blockchain or associated smart contracts. Sequencing Risk: The token may rely on a centralised sequencer(s) to process transactions to the native L1 network. If the sequencer(s) experience downtime, censorship, or misuse, transaction ordering and availability may be adversely affected. |
|||
| I.6 Mitigation measures | textBlock | Blockchain Performance Risk; The Ethereum blockchain has adopted a Proof-of-Stake consensus mechanism to improve network scalability and reduce latency. Ongoing upgrades to the network are designed to enhance throughput, and gas fees help prioritise transactions under load. The X Layer utilizes Polygon CDK technology and Zero-Knowledge proofs to batch transactions, significantly increasing throughput and reducing costs compared to Layer 1. Consensus Failure Risk; Ethereum Proof-of-Stake consensus mechanism includes validator incentives, slashing penalties for malicious actors, and finality checkpoints to ensure integrity. The validator set is large and globally distributed which reinforces decentralization of the network. X Layer inherits the security of Ethereum by posting validity proofs to Layer 1, ensuring that the state cannot be transitioned incorrectly even if the L2 operator is malicious. Smart Contract Vulnerabilities; Smart contracts on Ethereum and X Layer are immutable by design, unless explicitly designed to be upgradeable. The ecosystem encourages open source code, independent audits, and community input. Standardised libraries such as OpenZeppelin reduce coding errors by reusing tested components. Upgradeability Risk; Ethereum does not enforce upgrade functionalities within smart contracts, but supports their technical implementation. Risks related to upgradeable contracts can be mitigated through standard practices such as time delay triggers or multi-sig wallets, which OKX has implemented. Third-party Infrastructure Dependency; The Ethereum blockchain and ecosystem supports decentralized indexing and querying via different protocols to reduce reliance on centralized third-party data services. X Layer integrates with standard RPC providers and data availability layers to ensure robust infrastructure support. Interoperability Risk; Mitigations for cross-chain bridging include usage of audited bridges and token locking mechanisms. The official X Layer bridge utilizes ZK-proofs for secure asset transfers between Ethereum and X Layer. Protocol-level Risk; Ethereum maintains a public roadmap and follows a structured governance process. Core updates to the network undergo extensive testing and community reviews. X Layer upgrades are coordinated by the technical team with testing phases on testnets like Sepolia before mainnet deployment. Emerging Technology Risk; Ethereum developers monitor potential emerging technology threats and are actively researching and developing quantum-resistant solutions. The network's modular design may allow for future cryptographic upgrades if required. Protocols generally monitor cryptographic developments and maintain a modular architecture that enables future upgrades to post-quantum or similar standards. |
|||
| 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 | ||||