$LION MiCA White Paper

Index

General information Page 3
Part A - Information about the offeror or the person seeking admission to trading Page 4
Part B - Information about the issuer, if different from the offeror or person seeking admission to trading Page 5
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 Page 6
Part D - Information about the crypto-asset project Page 7
Part E - Information about the offer to the public of crypto-assets or their admission to trading Page 8
Part F - Information about the crypto-assets Page 9
Part G - Information on the rights and obligations attached to the crypto-assets Page 10
Part H - Information on the underlying technology Page 11
Part I - Information on risks Page 12
Part J - Information on the sustainability indicators in relation to adverse impact on the climate and other environment-related adverse impacts Page 13
$LION MiCA White Paper

General information

N Field Content
00 Table of contents General information
Part A: Information about the offeror or the person seeking admission to trading
Part B: Information about the issuer, if different from the offeror or person seeking admission to trading
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
Part D: Information about the crypto-asset project
Part E: Information about the offer to the public of crypto-assets or their admission to trading
Part F: Information about the crypto-assets
Part G: Information on the rights and obligations attached to the crypto-assets
Part H: Information on the underlying technology
Part I: Information on the risks
Part J: Information on the sustainability indicators in relation to adverse impact on the climate and other environment-related adverse impacts
01 Date of notification 2026-03-19
02 Statement in accordance with Article 6(3) of Regulation (EU) 2023/1114 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.
03 Compliance statement in accordance with Article 6(6) of Regulation (EU) 2023/1114 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.
04 Statement in accordance with Article 6(5), points (a), (b), (c), of Regulation (EU) 2023/1114 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.
05 Statement in accordance with Article 6(5), point (d), of Regulation (EU) 2023/1114 FALSE
06 Statement in accordance with Article 6(5), points (e) and (f), of Regulation (EU) 2023/1114 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.
07 Warning in accordance with Article 6(7), second subparagraph, of Regulation (EU) 2023/1114 Warning
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 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 The $LION token is a fungible, transferable, token issued natively on Cronos and bridged to Solana and Arbitrum.
$LION serves multiple in-ecosystem functions, including acting as the native token of Loaded Lions. It is also a payment token which is currently integrated with Crypto.com Pay, Solana Pay, and Portal Pay., giving holders access to various reward tiers and loyalty bonuses when locked into designated vaults. The total supply of LION is 100,000,000,000.
LION is classified as a non-utility token under the MiCA Regulation, as its stated utilities do not involve accessing goods or services provided by an identifiable issuer.
09 This field does not apply as 05 is false.
10 Key information about the offer to the public or admission to trading $LION token has been tradable since March 2025 across multiple centralised and decentralised exchanges worldwide, including Crypto.com, Kraken, and Bitmart. The MiCA Crypto Alliance is seeking its admission to trading within Kraken to enable compliant secondary market liquidity.
This admission would allow existing holders to trade $LION on a regulated EU venue,including Kraken where it is already listed globally outside the EU, ensuring transparent price discovery and stronger market depth. It also supports broader token distribution, which is essential for decentralised governance and wider stakeholder participation in ecosystem decisions.
$LION MiCA White Paper

Part A - Information about the offeror or the person seeking admission to trading

N Field Content
A.1 Name MICA Crypto Alliance OpCo Limited
A.2 Legal form N/A as LEI is provided in A.6
A.3 Registered address N/A as LEI is provided in A.6
A.4 Head office N/A as LEI is provided in A.6
A.5 Registration date 2025-11-19
A.6 Legal entity identifier 984500CEB5773O38LE40
A.7 Another identifier required pursuant to applicable national law N/A as LEI is provided in A.6
A.8 Contact telephone number +44(7441)903166
A.9 E-mail address submissions@micaalliance.com
A.10 Response time (Days) 030
A.11 Parent company N/A as LEI is provided in A.6
A.12 Members of the management body
Identity Business Address Functions
Gabriele Gios 4th Floor Kingsway Place, Triq IR – Repubblika, Valletta, VLT 1115, MT Director
A.13 Business activity Preparation and submission white papers under the EU Markets in Crypto Assets Regulation.
A.14 Parent company business activity The main object of the company is to own, manage and administer property of any kind whether belonging to the company or not. The secondary object of the company is to hold shares and, or equity in other companies.
A.15 Newly established TRUE
A.16 Financial condition for the past three years This field does not apply as A.15 is true.
A.17 Financial condition since registration The company was recently registered and has the following financial resources available to it: USD 2,000,000.
$LION MiCA White Paper

Part B - Information about the issuer, if different from the offeror or person seeking admission to trading

Disclaimer: No identifiable legal entity acting as issuer for LION could be determined. Substantively, this would correspond to field B.1 being “TRUE”. However, the MiCA XBRL taxonomy does not support this configuration and requires the completion of issuer-specific fields that are not applicable in this case. Accordingly, field B.1 is set to “FALSE” in the machine-readable version only, while the human-readable version reflects the absence of an identifiable issuer.

N Field Content
B.1 Issuer different from offerror or person seeking admission to trading TRUE
B.2 Name N/A
B.3 Legal form N/A
B.4 Registered address N/A
B.5 Head office N/A
B.6 Registration date N/A
B.7 Legal entity identifier N/A
B.8 Another identifier required pursuant to applicable national law N/A
B.9 Parent company N/A
B.10 Members of the management body N/A
B.11 Business activity N/A
B.12 Parent company business activity N/A
$LION MiCA White Paper

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

N Field Content
C.1 Name N/A
C.2 Legal form N/A
C.3 Registered address N/A
C.4 Head office N/A
C.5 Registration date N/A
C.6 Legal entity identifier N/A
C.7 Another identifier required pursuant to applicable national law N/A
C.8 Parent company N/A
C.9 Reason for crypto-asset white paper Preparation N/A
C.10 Members of the management body N/A
C.11 Operator business activity N/A
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
$LION MiCA White Paper

Part D - Information about the crypto-asset project

N Field Content
D.1 Crypto-asset project name Loaded Lions: Mane City Game
D.2 Crypto-asset name $LION
D.3 Abbreviation $LION
D.4 Crypto-asset project description The Mane City Game is the flagship game within the Loaded Lions ecosystem, a Web3 tycoon strategy game that blends accessible gameplay with blockchain-enabled tech. It is developed to demonstrate the practical utility of NFTs, by providing in-game bonuses to holders of integrated NFTs.
The project originated as a 10,000-piece NFT collection on the Crypto.com NFT platform and has since evolved into a broader interactive universe powered by the $LION token. $LION is the native token of the Loaded Lions ecosystem and serves as a staking asset, giving holders access to various reward tiers, and loyalty bonuses when locked into designated vaults. It is also a payment token which is currently integrated with Crypto.com Pay, Solana Pay and Portal Pay.
The project has shared a five-year roadmap structured around three core pillars, the $LION Economy, Gaming, and Growth.
D.5 Details of all natural or legal persons involved in implementation of crypto-asset project
Name of person Type of person Business address Domicile
Particle B Ventures Limited
Development team
Nerine Chambers, PO Box 905, Road Town, Tortola, British Virgin Islands
Virgin Islands (British)
Foris Dax Global Limited
Advisor
13 Classon House, Dundrum Business Park, D14 W9Y3, IE-D,IE
Ireland
Stepico
Development team
New York City 10016, NY-US, US
United States of America
D.6 Utility Token Classification FALSE
D.7 Key Features of Goods/Services for Utility Token Projects N/A
D.8 Plans for the token Past milestones:
In Q1 and Q2 of 2025, the Loaded Lions ecosystem launched the $LION token across multiple chains, such as Cronos, Solana, and Arbitrum, accompanied by the introduction of staking tiers. Official listings on selected centralised and decentralised exchanges were completed. Additional exchange listings followed, along with the activation of token-based rewards and benefits within the Crypto.com ecosystem.
In Q3 and Q4 of 2025, the $LION token was integrated into the Solana Pay and Portal Pay, enabling additional real-world utility for token holders. The initial phase of the DAO and governance framework was introduced, where token holders will be able to participate in governance discussions, vote on proposals through the DAO structure, strengthening community participation and supporting transparent decision-making across the ecosystem.
D.8 Plans for the token Future milestones
In 2026, the project will integrate $LION into Loaded Lions: Mane City, unlocking additional value for token holders and expand token functionality.
Additionally, a limited-release Loaded Lions debit card will be introduced, expanding the practical use cases of the ecosystem. The DAO pilot programme will continue to evolve, alongside the introduction of new token utilities and the release of a new NFT collection. A new blockchain-based game title with $LION integration will also enter development.
The project plans to host Mane City, World Series III, roll out Season 4 content, and expand its AI-powered NPC system within the game.
In 2027, the project will begin expanding its physical and lifestyle brand presence through global meet-ups. The broader roadmap includes VR/AR experimental features and creator-focused incubator programmes.
Looking ahead to Q1 and Q2 of 2028, the full DAO formation is expected to take place, alongside the expansion of the card programme and additional creator and community incentives. The project will culminate this phase of development with the launch of the annual Lion Summit, serving as a flagship global event for holders, partners, and contributors.
D.9 Resource allocation 50% of the total $LION token supply is allocated to community rewards and strategic partnerships, forming the foundation of user acquisition, engagement programs, and staking incentives. An additional 25% is reserved for liquidity provisioning across decentralised and centralised exchanges, ensuring sufficient market depth, token mobility, and cross-chain interoperability.
15% of the supply is allocated to an ecosystem reserve, which supports future technical development, project expansion, and token-based governance mechanisms, including the formation and funding of the DAO treasury. The remaining 10% is assigned to operations and marketing, covering infrastructure costs, product development, brand collaborations, and marketing campaigns.
D.10 Planned use of Collected funds or crypto-Assets There is no planned use of any funds or other crypto-assets collected.
$LION MiCA White Paper

Part E - Information about the offer to the public of crypto-assets or their admission to trading

N Field Content
E.1 Public offering or admission to trading
ATTR
E.2 Reasons for public offer or admission to trading By admitting the token to trading, holders of the token will gain transparent price discovery and improved liquidity. This enables the Project’s community and ecosystem participants to more easily enter and exit positions, supporting a dynamic and efficient market.
E.3 Fundraising target N/A
E.4 Minimum subscription goals N/A
E.5 Maximum subscription goals N/A
E.6 Oversubscription acceptance N/A
E.7 Oversubscription allocation N/A
E.8 Issue price N/A
E.9 Official currency or any other crypto-assets determining the issue price N/A
E.9 Any other tokens determining issue price N/A
E.10 Subscription fee N/A
E.11 Offer price determination method N/A
E.12 Total number of offered/traded crypto-assets
30,845,220,686
The upper bound of the asset count is determined by the total supply of $LION, which is set at 100 billion tokens. At the time of drafting this white paper, the circulating supply amounts to 30.84 billion $LION. In line with the MiCA taxonomy, which requires the indication of a numerical value for the traded crypto-assets, the exact circulating supply (30845220686) has been reported in the machine-readable version solely for technical compliance purposes.
E.13 Targeted holders
ALL
E.14 Holder restrictions N/A
E.15 Reimbursement notice N/A
E.16 Refund mechanism N/A
E.17 Refund timeline N/A
E.18 Offer phases N/A
E.19 Early purchase discount N/A
E.20 Time-limited offer N/A
E.21 Subscription period beginning N/A
E.22 Subscription period end N/A
E.23 Safeguarding arrangements for offered funds/crypto-Assets N/A
E.24 Payment methods for crypto-asset purchase N/A
E.25 Value transfer methods for reimbursement N/A
E.26 Right of withdrawal N/A
E.27 Transfer of purchased crypto-assets N/A
E.28 Transfer time schedule N/A
E.29 Purchaser's technical requirements $LION holders must use a compatible digital wallet supporting Cronos, Solana, or Arbitrum to access the Loaded Lions ecosystem.
E.30 Crypto-asset service provider (CASP) name Not Available
E.31 CASP identifier N/A
E.32 Placement form
NTAV
E.33 Trading platforms name Kraken
E.34 Trading platforms market identifier code (MIC) PESL
E.35 Trading platforms access The project is seeking admission to trading on the Kraken Exchange, subject to the platform’s listing procedures, compliance assessments, and technical integration. Once admitted, $LION will become available to Kraken users in supported jurisdictions, further broadening regulated market access and liquidity for the token.
E.36 Involved costs Exchanges may apply a service fee calculated as a percentage of each transaction, with the exact amount disclosed to the user prior to execution. Deposits and withdrawals involving fiat currency may also be subject to additional commissions imposed by external payment service providers.
E.37 Offer expenses This field does not apply, as there is no offer to the public.
E.38 Conflicts of interest No potential conflicts of interest have been identified at this stage.
E.39 Applicable law Ireland
E.40 Competent court Ireland
$LION MiCA White Paper

Part F - Information about the crypto-assets

N Field Content
F.1 Crypto-asset type Crypto-assets other than asset-referenced tokens or e-money tokens
F.2 Crypto-asset functionality The $LION token functions as the primary token within the Loaded Lions ecosystem, enabling access to a range of services, digital assets, and incentives across the project’s community, and financial infrastructure. Its current and planned functionalities are designed to support long-term engagement, token-based governance, and the seamless integration of Web3 experiences across the Loaded Lions ecosystem. This will allow $LION holders to participate in early-stage decision-making through a DAO structure, with voting rights on treasury usage, ecosystem funding, and roadmap direction. Participation in governance is planned for the future and they should not be relied upon as a promise until implemented.

Under the DAO framework, $LION will allow holders to submit proposals to the community within four main areas: the allocation and management of DAO funds, the development and use of the Loaded Lions brand and intellectual property, any other DAO-related proposals, and informational matters relevant to the community.

Holders of $LION tokens also have the power to vote on these proposals, with one token corresponding to one vote. Token holders can vote with the options ‘In favor’, ‘Against’ or ‘Abstain’. Proposals that receive a majority of ‘In favor’ votes move forward to implementation, while proposals that are rejected or receive no votes (or result in a tie) are marked as ‘Stalled’ and may be resubmitted.

The token will be integrated into the Crypto.com Visa Card platform, allowing token holders to link their $LION holdings to real-world payments and benefits. This integration is expected to enable spending incentives, merchant partnerships, and lifestyle perks tied to on-chain activity.

Presently, the $LION token can be staked through vaults that offer tiered rewards and bonuses, with higher tiers granting higher multipliers.

The token is fungible, transferable, and deployed across Cronos, Solana, and Arbitrum networks, with cross-chain operability maintained through official bridge infrastructure.
F.3 Planned application of functionalities The phased rollout of the decentralised governance framework, which will allow $LION holders to participate in decision-making through a DAO structure introduced in Q3 2025 and is planned to rollout in 2026 to 2027.
F.4 Type of crypto-asset white paper
OTHR
F.5 The type of submission
MODI
F.6 Crypto-asset characteristics The $LION token is a fungible, transferable, token issued natively on Cronos and bridged to Solana and Arbitrum.
LION serves multiple in-ecosystem functions, firstly as a staking asset, giving holders access to various reward tiers and loyalty bonuses when locked into designated vaults, and as a governance token giving access to token holders to vote on ecosystem decisions.
F.7 Commercial name or trading name N/A as DTI is provided in F.13.
F.8 Website of the issuer This field does not apply as LION is issued by a non-identifiable legal entity.
F.9 Starting date of offer to the public or admission to trading 2026-01-21
F.10 Publication date 2026-03-30
F.11 Any other services provided by the issuer This field does not apply as LION is issued by a non-identifiable legal entity.
F.12 Language or languages of the crypto-asset white paper English
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 Cronos: TZ1SD9FRZ
Solana: 6728MTJH0
Arbitrum: FP20NXW1P
F.14 Functionally fungible group digital token identifier, where available QW6T8C2WG
F.15 Voluntary data flag FALSE
F.16 Personal data flag TRUE
F.17 LEI eligibility TRUE
F.18 Home Member State
Malta
F.19 Host Member States
Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Liechtenstein, Lithuania, Luxembourg, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden
$LION MiCA White Paper

Part G - Information on the rights and obligations attached to the crypto-assets

N Field Content
G.1 Purchaser rights and obligations This field does not apply as the token is not associated with any legal claim of ownership, profit participation, entitlement to dividends, or repayment obligations from an issuer or its affiliates.

As reflected in the governance framework made available on the Loaded Lions website (https://loadedlions.com/governance/) as of the date of this white paper, it is expected that $LION holders will eventually receive DAO governance non-contractual functional rights, which are further described as crypto-asset functionalities in F.2.
G.2 Exercise of rights and obligations This field does not apply as the token confers no ownership or financial claims. The requirements set out below constitute technical preconditions and user responsibilities necessary to access and maintain the DAO governance functional rights mentioned in G.1 and further described in F.2.

As part of the planned DAO governance framework, holders wishing to participate in the decision-making of the Loaded Lions ecosystem must follow the proposal process starting from the initial drafting of the idea.

While there is no formal requirement for a specific format, it is strongly recommended that each proposal be structured using a comprehensive template. This template should include an executive summary outlining all relevant information, context explaining the origin of the idea and the problem the proposal aims to address, a team description identifying those responsible for implementation, key terms clarifying the main elements, and key benefits for the Loaded Lions, highlighting how the proposal benefits the community. Additionally, the proposal should specify an implementation timeline, the required budget, the expected economic impact in terms of revenue or profit, and an assessment of risks associated with execution.

Once the first draft is submitted, the proposal is shared with the community for feedback and subsequently moves to the voting phase, where a majority of ‘In favor’ votes leads to implementation.

$LION holders are solely responsible for safeguarding their wallets and private keys. Loss or compromise of keys results in irreversible loss of access.
G.3 Conditions for modifications of rights and obligations This field does not apply as the token confers no ownership or financial claims as of the date of this white paper.
G.4 Future public offers There are no future public offers planned at this stage.
G.5 Issuer retained crypto-assets 0
G.6 Utility Token Classification FALSE
G.7 Key features of goods/services of utility tokens This field does not apply as G.6 is false.
G.8 Utility tokens redemption This field does not apply as G.6 is false.
G.9 Non-trading request TRUE
G.10 Crypto-assets purchase or sale modalities The token has been listed on selected centralised exchanges (CEXs), including Kraken , subject to the platform’s jurisdictional availability, account requirements, and compliance controls. On decentralised exchanges (DEXs), LION can be traded using automated market maker (AMM) protocols such as VVS Finance (Cronos) or platforms compatible with Solana and Arbitrum liquidity pools.
G.11 Crypto-assets transfer restrictions There are no restrictions on the transferability of the crypto-assets admitted to trading.
G.12 Supply adjustment protocols FALSE
G.13 Supply adjustment mechanisms This field does not apply, as G.12 is false.
G.14 Token value protection schemes FALSE
G.15 Token value protection schemes description This field does not apply, as G.14 is false.
G.16 Compensation schemes FALSE
G.17 Compensation schemes description This field does not apply, as G.16 is false.
G.18 Applicable law There is no written legal agreement between an issuer and the crypto asset-holder that sets out the laws that govern the legal relationship between those two parties. In the absence of such an agreement, the laws that govern that relationship will depend on the location of an issuer and the given crypto asset-holder and characteristic performance of the legal relationship, and any agreed intention of an issuer and crypto asset-holder.
G.19 Competent court There is no written legal agreement between an issuer and the crypto asset-holder that sets out the laws that govern the legal relationship between those two parties. In the absence of such an agreement, the laws that govern that relationship will depend on the location of an issuer and the given crypto asset-holder and characteristic performance of the legal relationship, and any agreed intention of an issuer and crypto asset-holder.
$LION MiCA White Paper

Part H - Information on the underlying technology

N Field Content
H.1 Distributed ledger technology (DTL) N/A as DTI is provided in F.13
H.2 Protocols and technical standards $LION is a fungible token deployed on the Cronos EVM Chain, a public Layer 1 blockchain built using the Cosmos SDK and Ethermint frameworks. The chain supports Ethereum Virtual Machine compatibility.

Networking layer
$LION utilises the networking stack of Cronos EVM, which is built atop CometBFT. Nodes establish encrypted peer‑to‑peer connections using Secret Connection which employs Ed25519 identity keys and X25519 session keys. Streams are multiplexed over a single TCP connection via MConnection, and traffic is channelled by category. Peer discovery relies on static seed nodes, persistent peers and a peer exchange (PEX) address book. This setup underpins $LION’s settlement layer and avoids libp2p/gossipsub dependencies.

Serialisation layer
$LION transactions on Cronos EVM are serialised via Protocol Buffers (Protobuf) as defined in Cosmos SDK ADR‑020. Although $LION uses the CRC‑20 standard within the Ethermint EVM, the outer Cosmos SDK envelope remains Protobuf encoded, providing structured and upgrade‑compatible messaging.

Cryptographic primitives
$LION leverages secp256k1 for account‑level signatures and Ed25519 for validator consensus keys. Within the EVM environment, Keccak‑256 is used for contract and internal execution; for consensus and state hashes Cronos uses SHA‑256. Merkle inclusion proofs conform to ICS‑23.

Ledger model
The Cronos blockchain which supports $LION is account‑based. Each account may store balances, metadata and contract storage where applicable. State is maintained in a Merkleised key‑value structure, enabling verifiable proofs.

Execution model
$LION executes on the Cronos EVM chain via Ethermint. This means standard CRC‑20 token transfers and approvals take place in the EVM, while underlying state and modules may interact through the Cosmos SDK stack. The chain maintains deterministic execution semantics, and the fee‑market model is EIP‑1559‑inspired.

Token standards
$LION is issued as a CRC‑20 token on Cronos EVM. The CRC‑20 standard is functionally equivalent to Ethereum’s ERC‑20 token interface (Ethereum Request for Comment 20), supporting core functions such as transfer, approve, transferFrom, balanceOf, and allowance. This compatibility ensures that $LION can be used with standard Ethereum-based wallets, decentralised applications, and infrastructure tools while benefiting from Cronos’s integration with the Cosmos SDK ecosystem. Following its initial launch on Cronos, $LION has also been deployed to other blockchains: on Arbitrum as an ERC‑20 token and on Solana as an SPL token (Solana Program Library standard), which defines token behaviour within Solana’s runtime environment. Despite these multichain deployments, Cronos remains the canonical chain for $LION.

APIs and interfaces
Cronos EVM provides JSON-RPC endpoints for interacting with the $LION CRC-20 contract. Cronos also offers gRPC and REST APIs via the Cosmos SDK, and event subscriptions via CometBFT’s WebSocket interface. Public explorers such as explorer.cronos.org allow for inspection of $LION token transfers and contract activity.
H.3 Technology used Implementation and architecture
$LION runs on Cronos EVM, which is implemented in Go using the Cosmos SDK and Ethermint. The validator set on Cronos EVM comprises around 33 invited entities (for example major infrastructure providers). $LION’s architecture consists of a CRC‑20 token contract and associated staking vaults within the Ethermint EVM, sharing state with native Cosmos SDK modules.

Runtime and build parameters
Node software for Cronos EVM is built via reproducible pipelines, using CI processes and version control. Parameters such as gas limits, slashing thresholds and upgrade heights are set on‑chain. Upgrades are scheduled via the SDK upgrade module but require validators to manually install the updated binary and restart at the designated block height.

Dependencies
The Cronos EVM chain relies on CometBFT for consensus and P2P networking, Cosmos SDK for state and modules and Ethermint for EVM compatibility. $LION inherits this stack and operates atop it. Infrastructure components explorers, RPC gateways, analytics services are provided by Cronos Labs and ecosystem partners.
H.4 Consensus Mechanism $LION does not participate in consensus. Its transactions are executed as part of the block processing workflow and are considered final once included in a valid block produced by Cronos' consensus participants.
$LION is deployed on Cronos, which uses CometBFT engine, a Byzantine Fault Tolerant protocol derived from Tendermint. The validator set on this chain is permissioned, meaning that validators are not elected by public staking but instead selected through an internal admission process. Only entities that have been explicitly invited to join can participate in consensus.
H.5 Incentive Mechanisms and Applicable Fees Network-level execution fees
Transactions involving $LION on the Cronos EVM Chain are subject to standard network gas fees denominated in CRO. The chain uses an EIP-1559-style fee market where each transaction includes a base fee and an optional tip to validators. Unlike Ethereum, both the base fee and the tip are fully rewarded to validators. Users interacting with $LION, including transfers and staking vault actions, pay these fees upon inclusion in a block. There are no protocol-specific surcharges or taxes applied by the $LION project itself.

Application-level staking incentives
The $LION ecosystem includes on-chain staking vaults that offer fixed lock periods with corresponding reward multipliers. There are five lock options: 3, 6, 12, 36, and 60 months. Longer lock durations yield proportionally higher staking rewards. Users may deposit, upgrade, or withdraw from these vaults directly via the project interface. The vault guide on the project’s website outlines the full process, and there are no project-level protocol fees disclosed for these operations beyond standard network gas.
H.6 Use of distributed ledger technology False
H.7 DLT functionality description This field does not apply as H.6 is false.
H.8 Audit TRUE
H.9 Audit outcome Audit reports for $LION have not been published via official project channels. In the absence of $LION-specific audits, this section presents independent assessments of a Cronos EVM implementation and the Cosmos SDK.

Kudelski Security’s Ethermint Audit 2022
  • Object: Carried out on selected Ethermint components used by Cronos such as JSONRPC, ante handler and the EVM state transition.
  • Results: The audit results include 1 high, 5 medium, 10 low, 7 informational findings.
  • Actions: All High and most medium issues were remediated. One medium was partially remediated.
    1. Least Authority’s Cosmos SDK Framework Audit 2019
  • Object: Security and correctness review of the Cosmos SDK framework, including BaseApp structure, module initialisation, transaction handling, and specifications for authentication, bank, fee distribution, and tombstone mechanisms. The audit explicitly excluded consensuslevel or gametheoretic evaluations.
  • Results: The audit offered structural and documentationfocused recommendations. While no severity levels were assigned, the report highlighted ambiguities in module definitions and gaps in state initialisation procedures.
  • Actions: The Cosmos team removed the custom RNG and aligned to OS PRNG usage.
    1. Least Authority’s Cosmos SDK Liquidity Module Audit 2021
  • Object: Codelevel audit of the Cosmos SDK Liquidity Module used in Gravity DEX, including the CLI interface, protobuf definitions, gRPC services, and full module integration.
  • Results: No critical vulnerabilities were found. Observations included the use of truncated SHA256 in address generation and several recommendations to improve testing practices, error handling, and documentation clarity.
  • Actions: The team added the linter to CI and fixed all outstanding lintererrors.
$LION MiCA White Paper

Part I - Information on risks

N Field Content
I.1 Offer-related risks Market volatility
The market price of $LION may fluctuate sharply due to broader crypto-asset sentiment, exchange depth, and the discretionary release of tokens by affiliated entities.

Liquidity conditions
$LION may experience low trading volumes or wide bid-ask spreads, particularly during early distribution or campaign-driven activity.

Large transactions and discretionary unlocks
Pre-allocated $LION tranches may be released at the discretion of the project team; this discretionary supply and linear emissions can affect market pricing.

Listing/access and venue dependency
Market access for $LION depends on third-party platforms and may be affected by geo-blocking, policy changes, or delisting decisions.

Off-chain programme dependency
Some $LION benefits such as rebates, Earn campaigns, referrals are offered in partnership with Crypto.com, and such third parties may change, suspend, or exclude users at the platform’s discretion.
I.2 Issuer-related risks No identifiable legal or natural person could be confirmed as the issuer of $LION. This does not imply that no issuer exists, but rather that no verifiable information is publicly available.
I.3 Crypto-assets-related risks Irreversibility
$LION transfers on Cronos EVM are final and cannot be reversed at the protocol level; key loss or misdirection is permanent.

Utility-delivery risk
Some $LION utilities are roadmap-based or conditional such as in-game use, debit-card linkage, governance. Delivery may be delayed or altered.

Demand concentration and promotional exposure
Demand for $LION may depend on off-chain campaigns or product tie-ins (e.g., Crypto.com Earn), which can start or end without notice.

Custody and key management
Token holders bear responsibility for safekeeping of private keys or custodial arrangements; loss may result in permanent asset loss.

Bridging and supply fragmentation
$LION is deployed across multiple chains (Cronos, Solana, Arbitrum); misconfigured bridges or peg mechanisms could create circulating-supply mismatch or cross-chain state divergence.

Illiquidity from long-term locks
Vault participation may involve lock-in periods up to 60 months, limiting user flexibility and resale options.
I.4 Project implementation-related risks Timeline and delivery delays
Roadmap items or smart-contract updates (e.g., new vaults, utility expansion) may be postponed or cancelled.

Operational interruptions
RPC access, vault UI performance, and data integrations depend on Cronos node infrastructure, which may experience latency or service degradation.

Third-party dependency
$LION’s visibility and usability rely on wallets, explorers, indexers, and programmatic endpoints maintained by Cronos Labs or partners.
I.5 Technology-related risks Protocol-level defects
$LION transactions execute on Cronos EVM, where flaws in Ethermint or Cosmos SDK including fee market logic, module behaviour may affect execution and settlement.

Code quality and bugs
Software bugs and defects in new Cronos EVM releases or updates could compromise system functionality, security, and user trust.

Interoperability-related risk
$LION exists on multiple chains; relay, mint/burn, or bridge module faults may result in peg instability or duplicated supply.
I.6 Mitigation measures Offer-related risks
  • Listing/access and venue dependency:The $LION token is listed across a diversified set of centralised and decentralised exchanges, which reduces reliance on any single thirdparty trading venue. This multiplatform approach limits the impact of potential geoblocking, policy changes, or unilateral delisting decisions by a specific exchange. In the event that access becomes restricted in certain jurisdictions or on specific platforms, users retain the ability to trade $LION through alternative venues, thereby preserving market accessibility and continuity of liquidity.
    1. Technology- related risks
    1. Protocol - level defects: $LION inherits a chain that uses the Cosmos SDK and Ethermint stack, which have undergone audits (e.g., Least Authority on Ethermint).
  • Interopeability - related risk: Deployment and bridge information is transparently listed to reduce fragmentation and mitigate confusion over canonical supply.
$LION MiCA White Paper

Part J - Information on the sustainability indicators in relation to adverse impact on the climate and other environment-related adverse impacts

N Field Content
S.1 Name MiCA Crypto Alliance Opco Limited
S.2 Relevant legal entity identifier 984500CEB5773O38LE40
S.3 Name of the crypto-asset $LION
S.4 Consensus Mechanism $LION does not participate in consensus. Its transactions are executed as part of the block processing workflow and are considered final once included in a valid block produced by Cronos' consensus participants.
$LION is deployed on Cronos chain, which uses CometBFT engine, a Byzantine Fault Tolerant protocol derived from Tendermint. The validator set on this chain is permissioned, meaning that validators are not elected by public staking but instead selected through an internal admission process. Only entities that have been explicitly invited to join can participate in consensus.
S.5 Incentive Mechanisms and Applicable Fees See H.5
S.6 Beginning of period to which disclosed information relates 2025-06-24
S.7 End of period to which disclosed information relates 2025-11-04
S.8 Energy consumption 0.25281
S.9 Energy consumption sources and methodologies Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5).
Full methodology available at : www.micacryptoalliance.com/methodology
S.10 Renewable energy consumption 44.2283783492
S.11 Energy intensity 0.0000016450
S.12 Scope 1 DLT GHG emissions - controlled 0.00000
S.13 Scope 2 DLT GHG emissions - purchased 0.00008
S.14 GHG intensity 0.0000004877
S.15 Key energy sources and methodologies Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5).
Full methodology available at: www.micacryptoalliance.com/methodologies
S.16 Key GHG sources and methodologies Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5).
Full methodology available at: www.micacryptoalliance.com/methodologies
S.17 Energy mix
Energy Source Percentage
Bioenergy 4.753499379
Coal 15.3983005322
Flared Methane 0
Gas 30.2479338222
Hydro 4.2433903781
Nuclear 8.2307612856
Other Fossil 1.8946260106
Other Renewables 0.5467464721
Solar 15.0817201704
Vented Methane 0
Wind 19.6030219496
S.18 Energy use reduction N/A
S.19 Carbon intensity 0.30116
S.20 Scope 3 DLT GHG emissions – Value chain N/A
S.21 GHG emissions reduction targets or commitments N/A
S.22 Generation of waste electrical and electronic equipment (WEEE) 0.0000003234
S.23 Non-recycled WEEE ratio 61.5379840451
S.24 Generation of hazardous waste 0.0000000002
S.25 Generation of waste (all types) 0.0000003234
S.26 Non-recycled waste ratio (all types) 61.5379840451
S.27 Waste intensity (all types) 0.0000021046
S.28 Waste reduction targets or commitments (all types) N/A
S.29 Impact of the use of equipment on natural resources Land use: 0.00607 m²
S.30 Natural resources use reduction targets or commitments N/A
S.31 Water use 0.00103
S.32 Non recycled water ratio 74.2745351393
S.33 Other energy sources and methodologies Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5).
Full methodology available at: www.micacryptoalliance.com/methodologies
S.34 Other GHG sources and methodologies Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5).
Full methodology available at: www.micacryptoalliance.com/methodologies
S.35 Waste sources and methodologies Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5).Estimates on individual node weight, hazardous components and deprecation rate are used.
Full methodology available at: www.micacryptoalliance.com/methodologies
S.36 Natural resources sources and methodologies Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5). Usage of natural resources is approximated through land use metrics. Land use, water use and water recycling are calculated based on energy mix-specific estimates of purchased electricity land intensity, purchased electricity water intensity, and water recycling rates. Full methodology available at: www.micacryptoalliance.com/methodologies
Disclaimer: This document is made available by the MiCA Crypto Alliance Limited ("MiCA Crypto Alliance"), trading as “The MiCA Crypto Alliance”. MiCA Crypto Alliance does not provide any warranty of any kind, express or implied, including but not limited to warranties of accuracy, fitness for a particular purpose, compliance with any laws and/or non-infringement. MiCA Crypto Alliance also assumes no responsibility for any errors, defects, or omissions in the document. To the maximum extent permitted by applicable laws, MiCA Crypto Alliance will not be liable for any direct, indirect, incidental, special, consequential, or exemplary damages, including but not limited to, damages for loss of profits, goodwill, data, or other intangible losses arising out of or relating to any use and/or reliance on the information in this document, however arising, including negligence.
https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#DevelopmentTeam https://xbrl.org/2024/iso3166#VG https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#Advisor https://xbrl.org/2024/iso3166#GB https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#DevelopmentTeam https://xbrl.org/2024/iso3166#US https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#AdmissionToTrading 30845220686 https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#AllTypesOfInvestors https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#NotApplicablePlacementForm https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#OtherCryptoassetWhitePaper https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#ModifyTypeOfSubmission https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#MaltaMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#AustriaMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#BelgiumMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#BulgariaMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#CroatiaMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#CyprusMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#DenmarkMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#EstoniaMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#FinlandMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#FranceMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#GermanyMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#GreeceMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#HungaryMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#IcelandMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#IrelandMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#ItalyMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#LatviaMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#LiechtensteinMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#LithuaniaMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#LuxembourgMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#NetherlandsMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#NorwayMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#PolandMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#PortugalMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#RomaniaMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#SlovakiaMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#SloveniaMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#SpainMemberState https://www.esma.europa.eu/taxonomy/2025-03-31/mica/#SwedenMemberState 1 984500CEB5773O38LE40 2025-12-31 984500CEB5773O38LE40 2025-01-01 2025-12-31 984500CEB5773O38LE40 2025-01-01 2025-12-31 10 984500CEB5773O38LE40 2025-01-01 2025-12-31 11 984500CEB5773O38LE40 2025-01-01 2025-12-31 12 984500CEB5773O38LE40 2025-01-01 2025-12-31 7 984500CEB5773O38LE40 2025-01-01 2025-12-31 8 984500CEB5773O38LE40 2025-01-01 2025-12-31 9 984500B6F8407AE38911 2025-01-01 2025-12-31 4 984500B6F8407AE38911 2025-01-01 2025-12-31 5 984500B6F8407AE38911 2025-01-01 2025-12-31 6 utr:D iso4217:USD xbrli:pure utr:tCO2e xbrli:pure utr:kg utr:m3 utr:t utr:J utr:kWh