| [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 | Core protocol functions include transaction processing, protocol governance, and network security through validator participation. The LEA Token is the native utility token of the LEA Blockchain and is technically required to access and operate these core network functions. The token is used for the payment of transaction and protocol-level fees, participation in staking and validation, and on-chain governance through LEA Improvement Proposals (LIPs). The LEA Token does not represent ownership, profit participation, repayment, or any other financial right vis-à-vis the offeror or any affiliated entity and is not redeemable for fiat currency or other assets. Existence: The token is issued and exists exclusively within the LEA blockchain architecture, which currently operates in a controlled mainnet-beta environment managed by the offeror. Consensus: The consensus mechanism is under active development. Validator-based decentralisation will be introduced in a subsequent project phase. Architecture: The protocol follows a modular design separating consensus and execution layers, with execution performed through WebAssembly-based smart contracts ("Decoders"). Total supply: The total supply of LEA tokens is fixed at 100,000,000,000 units. No mechanism exists to increase the maximum supply beyond this limit. All token issuance and distribution mechanisms described in this white paper operate exclusively within this fixed supply. Custody: LEA tokens are held in user-managed non-custodial wallets under full self-custody of the token holder. Backing: The token is not backed by fiat currency, commodities, or other assets and does not provide any guaranteed value. Category: Other crypto-asset (Utility Token) within the meaning of Article 3(5) of Regulation (EU) 2023/1114. The functional necessity of the LEA Token within the protocol does not imply any economic entitlement, expected return, or value preservation. Access to protocol functions may change over time based on technical parameters and governance decisions and does not constitute a contractual service obligation. |
|||
| 09 Further information about utility tokens | textBlock | Token holders may submit transactions, interact with and deploy smart contracts ("Decoders"), participate in on-chain governance through LEA Improvement Proposals (LIPs), and pay for network resources such as transaction execution, state storage, and related protocol fees. Access to specific network functions is subject to technical requirements and protocol rules. Certain activities, such as participation in validation or block production, require compliance with predefined staking and validator criteria and are not available solely by virtue of token ownership. The extent of network usage is limited by technical parameters, including available gas, protocol capacity, and applicable network rules, rather than by any entitlement to economic benefits. The LEA Utility Token does not entitle the holder to any interest, profit participation, revenue share, or access to off-chain services provided by the offeror or any affiliated entity. |
|||
| 10 Key information about the offer to the public or admission to trading | textBlock | In addition, a limited portion of the community and ecosystem allocation may be made available for acquisition against consideration as an auxiliary access mechanism to the network. Such acquisition is not intended as a fundraising or investment activity but serves to enable broader participation in network functions where tokens are required for usage. Where applicable, token acquisition may be facilitated through an automated pricing mechanism designed to reflect network usage levels and protocol capacity constraints and to ensure neutral and non-discretionary access. The pricing mechanism is not intended to create expectations of profit, value appreciation, or secondary market liquidity. No minimum acquisition amount is required. There is no guaranteed liquidity, redemption right, or obligation to establish or support a secondary market for the LEA Token. The offer of LEA Tokens does not constitute an investment product or a financial instrument. Offer Details Total amount made available: A limited portion of the community and ecosystem allocation, corresponding to up to approximately 7.8 % of the total token supply, may be made available for distribution or acquisition prior to the formal establishment of the LEA Foundation. Total token supply: 100,000,000,000 LEA (fixed). Issue Price No fixed issue price is set in advance. Where an automated pricing mechanism is applied, the acquisition price of LEA Tokens is determined algorithmically at the time of acquisition based on predefined protocol parameters. The pricing mechanism serves solely as a technical access and allocation mechanism and does not imply any financial return or profit expectation. Payment Methods Acquisition of LEA Tokens may be possible using fiat currency or other crypto-assets through compliant payment channels. Payment processing may involve regulated payment service providers or crypto-asset service providers operating in accordance with applicable EU regulatory requirements. Accepted payment methods and technical parameters may vary over time and are disclosed prior to any acquisition. Offer Period The offer of LEA Tokens may be conducted on a time-limited or ongoing basis, depending on network requirements, technical conditions, and operational considerations. Specific start or end dates, where applicable, are communicated separately and do not constitute a commitment to conduct an offer for a fixed duration. Subscription limits: No minimum subscription amount applies. Form of placement: Direct protocol-based distribution or acquisition mechanisms within the LEA network. Distribution and delivery: Tokens are credited to user-controlled LEA wallets within the operational network environment following completion of applicable technical and compliance requirements. |
|||
| Part A - Information about offeror or person seeking admission to trading | |||||
| A.1 Name | text | ||||
| A.2 Legal form | text | ||||
| A.3 Registered address | |||||
| Registered addess | text | ||||
| Country | enumeration | ||||
| Sub-division | text | ||||
| A.4 Head office | |||||
| Head office | text | ||||
| Country | enumeration | ||||
| Sub-division | text | ||||
| A.5 Registration date | date | ||||
| A.6 Legal entity identifier | LEI | ||||
| A.7 Another identifier required pursuant to applicable national law | text | ||||
| A.8 Contact telephone number | text | ||||
| A.9 E-mail address | text | ||||
| A.10 Response time (days) | integer | ||||
| A.11 Parent company | text | ||||
| A.12 Members of the management body | |||||
| Member #1 | id | 1 | |||
| Identity | text | ||||
| Business address | text | ||||
| Function | text | ||||
| A.13 Business activity | textBlock | ||||
| A.14 Parent company business activity | textBlock | ||||
| A.15 Newly established | boolean | ||||
| A.16 Financial condition for the past three years | textBlock | The most recent adopted annual financial statements relate to the financial year ending 31 December 2023. The annual financial statements were adopted on 28 March 2025. As of 31 December 2023: Total assets amounted to EUR 20,863.36. Equity amounted to EUR 17,896.36. Provisions amounted to EUR 857.00. Liabilities amounted to EUR 2,110.00, all of which had a remaining maturity of less than one year and were owed to shareholders. Fixed assets amounted to EUR 1,200.00. Current assets amounted to EUR 19,663.36. Historically, the company operated primarily as a holding entity and did not conduct material operational business activities. Accordingly, the balance sheet reflects limited administrative operations consistent with such holding structure. Operational activities in connection with the LEA Blockchain project commenced during the current financial period. |
|||
| A.17 Financial condition since registration | textBlock | ||||
| 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 | N/A | . | |||
| B.3 Legal form | N/A | . | |||
| B.4 Registered address | |||||
| Registered addess | N/A | . | |||
| Country | N/A | . | |||
| Sub-division | N/A | . | |||
| B.5 Head office | |||||
| Head office | N/A | . | |||
| Country | N/A | . | |||
| Sub-division | 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 | |||||
| Member #1 | N/A | . | |||
| Identity | N/A | . | |||
| Business address | N/A | . | |||
| Function | N/A | . | |||
| B.11 Business activity | N/A | . | |||
| B.12 Parent company business activity | N/A | . | |||
| 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 | N/A | . | |||
| C.2 Legal form | N/A | . | |||
| C.3 Registered address | |||||
| Registered address | N/A | . | |||
| Country | N/A | . | |||
| Sub-division | N/A | . | |||
| C.4 Head office | |||||
| Head office | N/A | . | |||
| Country | N/A | . | |||
| Sub-division | 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 | |||||
| Member #1 | N/A | . | |||
| Identity | N/A | . | |||
| Business address | N/A | . | |||
| Function | 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 | . | |||
| 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 | ||||
| D.6 Utility token classification | boolean | ||||
| D.7 Key features of goods or services for utility token projects | text | 1 Network participation: use LEA to pay transaction and protocol-level fees. 2 Staking and validation: stake tokens to help secure the network and participate in validator selection. 3 Governance: vote on LEA Improvement Proposals (LIPs) to influence protocol updates and ecosystem policies. 4 Access to services: interact with Programmable Object Domains (PODs) that enable modular applications such as tokenized assets, decentralized organizations, and privacy solutions. The token does not represent a financial instrument, investment contract, or e-money. It serves solely as a functional digital asset for utility and governance within the LEA Blockchain network. |
|||
| D.8 Plans for the token | |||||
| Description of past milestones | textBlock | Completion of core protocol modules (Consensus & Execution Layer). Initiation of the community onboarding and XP reward system. Initial validator framework and developer SDK released for testing. |
|||
| Description of future milestones | textBlock | 2026 Q2 Activation of decentralized validator network and PoH-based consensus. 2026 Q2 Mainnet launch and start of public token availability planned. 2026 Q2 to Q4 Deployment of reference PODs (RWA, Privacy, DAO) and on-chain governance. Continuous SDK improvements and cross-POD composability. |
|||
| D.9 Resource allocation | text | To date, the project has been financed exclusively through private contributions of the founders. No external investors or institutional financing have been involved. Each of the two founders has contributed approximately two years of development time to the project. This contribution has not been compensated and does not constitute a financial liability of the issuer. Direct operational expenses related to the project, including server infrastructure and related operating costs, have been borne entirely by the founders. Such operating expenses have amounted to approximately EUR 1,500 over the past 18 months. The project has not generated revenue to date. The proceeds from the planned public token offering are intended to support continued development activities, infrastructure expansion, security reviews, legal and compliance expenses, and the planned establishment of the LEA Foundation. The founders currently continue to support the project financially and operationally during the ongoing development phase. |
|||
| D.10 Planned use of collected funds or other tokens | text | No distributions, dividends, or financial returns to token holders are planned. Funds will cover software development, security audits, validator incentives, community programs, and regulatory compliance costs. The use of funds does not create any entitlement, claim, or expectation for purchasers of LEA Tokens with respect to project continuation, success, or token utility. |
|||
| 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 | The public offer is intended to support decentralised network usage, validator participation, governance processes, and other on-chain activities that rely on the availability of the LEA Token. |
|||
| 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 | The price determination serves solely as a technical access and allocation mechanism and is applied uniformly at the time of each individual acquisition. It does not constitute a market-based pricing process, does not reflect secondary market conditions, and is not intended to create expectations regarding value development or liquidity. The parameters used for price calculation are defined in advance as part of the distribution logic and are applied in an objective and automated manner without discretionary intervention by the issuer. |
|||
| E.12 Total number of offered or traded other tokens | integer | ||||
| E.13 Targeted holders | enumeration | ||||
| E.14 Holder restrictions | text | This includes, in particular, compliance with Regulation (EU) 2023/1114 (MiCAR), applicable sanctions regimes, and identity verification or eligibility checks where required by law or operational procedures. |
|||
| E.15 Reimbursement notice | boolean true | ||||
| E.16 Refund mechanism | textBlock | Where applicable, refunds are processed using the original payment method within a period of up to 14 calendar days, subject to technical and compliance-related requirements. Once LEA Utility Tokens have been transferred on-chain to the purchaser's wallet, the transaction is completed at protocol level and cannot be reversed through the network. |
|||
| E.17 Refund timeline | text | ||||
| E.18 Offer phases | textBlock | Explanation: The public offer of LEA Utility Tokens is not structured into predefined offering phases or tranches. |
|||
| E.19 Early purchase discount | textBlock | Explanation: No early purchase discounts, preferential pricing, or similar incentive mechanisms apply to the public offer of LEA Utility Tokens. |
|||
| 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 | Reimbursements may be subject to transaction fees imposed by payment service providers or blockchain networks. |
|||
| 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 | A limited number of LEA tokens have been minted and allocated as development compensation to a founder. No tokens from the planned founder allocation under the tokenomics structure have been distributed as of the date of this Whitepaper. Founder allocation tokens remain subject to the defined vesting schedule, with the first vesting tranche scheduled for a future date. During the current transitional phase prior to the establishment of the planned LEA Foundation, the founders technically control the deployment of future minting contracts within the predefined maximum supply. The issuer, Hassan Systems GmbH, is authorized solely to mint the fixed quantity of tokens specified for the public offering. These structural relationships may give rise to potential conflicts of interest between the founders, the issuer and token holders. Following the establishment of the LEA Foundation, it is intended that governance and emission oversight will be transferred to the Foundation in order to reduce concentration of control. At the time of publication of this Whitepaper, no additional material conflicts of interest have been identified. |
|||
| 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 | These services are not covered by Regulation (EU) 2023/1114 and are conducted independently of the LEA token issuance. |
|||
| 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 | The maximum theoretical supply of 100,000,000,000 LEA represents an upper cap and does not reflect tokens in circulation. Tokens are not pre-minted at genesis. LEA tokens are created exclusively through dedicated smart-contract-based minting mechanisms. Tokens come into existence only at the moment of execution of a specific minting transaction and do not exist prior to such execution. The issuer (Hassan Systems GmbH) is authorized to mint only the fixed quantity of tokens specified in field E.12 (7,775,000,000 LEA) for the purpose of the public offering. This minting authorization is technically restricted to that predefined maximum amount. Tokens intended for sale are minted only upon purchase and are not generated in advance. Additional minting contracts may be technically deployed by the protocol founders. Each minting contract is purpose-bound and capped by a predefined maximum amount. No unlimited or discretionary mint function exists outside these capped smart contracts. At the time of publication of this Whitepaper, no treasury reserve of pre-minted tokens exists. Tokens that have not been minted do not exist on-chain and are not held by the issuer or the founders. Following the planned establishment of the LEA Foundation, it is intended that remaining emission rights be transferred to the Foundation, which will assume governance oversight of future minting mechanisms. |
|||
| 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 | ||||
| H.3 Technology used | textBlock | (i) a minimal consensus layer responsible solely for the ordering of transactions, and (ii) an execution layer composed of programmable smart-contract interpreters called Decoders (PODs). The design enables future scalability through verifiable state compression using zero-knowledge proofs (zk-STARKs), which are currently under development and not yet implemented in the active network. |
|||
| H.4 Consensus mechanism | text | ||||
| H.5 Incentive mechanisms and applicable fees | text | ||||
| 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 | The acquisition price of LEA tokens is determined at the time of acquisition based on a protocol-defined pricing mechanism and may vary over time. LEA tokens are not admitted to trading on any crypto-asset trading platform at the time of the offer, and no secondary market liquidity is guaranteed. The offer does not include any redemption, buy-back, or investment-protection mechanisms. Regulatory frameworks applicable to crypto-assets at European Union or national level may evolve over time. Future regulatory developments could affect the legal classification, permitted use, or compliance requirements applicable to LEA tokens or to the entities involved in their issuance or distribution. |
|||
| I.2 Issuer-related risks | textBlock | The issuer's role is limited to the execution of the public offer and related administrative and technical coordination tasks prior to the establishment of the LEA Foundation. Delays in the formation of the LEA Foundation or in the transition of governance and operational responsibilities may temporarily affect project coordination, communication, or decision-making processes. The issuer may rely on external technical infrastructure providers and development partners. Disruptions, termination of services, or failures of such third parties could affect network availability or development progress. Reputational risks, project execution challenges, or insufficient communication may adversely affect stakeholder confidence and ecosystem participation. |
|||
| I.3 Other tokens-related risks | textBlock | Their functional utility depends on the continued development, availability, and operation of the LEA protocol. LEA tokens do not represent a claim to monetary value, are not redeemable, and do not confer any guaranteed economic benefit. Loss of access credentials, private keys, or wallet data may result in the irreversible loss of access to tokens. Changes in applicable legal or regulatory frameworks may affect the recognition, use, or transferability of utility tokens. In addition, vulnerabilities or failures in third-party wallet software, interfaces, or infrastructure may result in operational errors or loss outside the control of the issuer. The absence of secondary market support may materially limit the ability to transfer LEA Tokens outside the protocol environment. |
|||
| I.4 Project implementation-related risks | textBlock | Development timelines and the transition to a decentralised network architecture may be affected by technical complexity, resource availability, coordination among contributors, or regulatory considerations. The planned establishment of the LEA Foundation is intended to assume long-term governance and maintenance responsibilities. Delays or organisational challenges related to its formation could affect the timing of decentralisation or ecosystem expansion. Limited early adoption by developers, validators, or users may slow network growth and reduce participation in governance or validation activities. |
|||
| I.5 Technology-related risks | textBlock | This configuration may create dependencies on specific infrastructure components and increase exposure to service interruptions during development. Software defects, configuration errors, or weaknesses in cryptographic implementations could adversely affect system integrity, transaction processing, or token balances. The introduction of consensus mechanisms, validator participation, and staking functionality introduces additional technical risks, including potential synchronisation issues, validator misbehaviour, or consensus failures. Reliance on third-party libraries, development tools, or hosting services may introduce external dependencies that are outside the direct control of the issuer. |
|||
| I.6 Mitigation measures | textBlock | Prior to broader network deployment, the project intends to conduct independent external security assessments and testing, subject to technical readiness and resource availability. Progressive decentralisation through validator participation and on-chain governance is intended to reduce single points of failure over time. The planned LEA Foundation is intended to establish governance, maintenance, and security oversight structures to support long-term operational resilience. |
|||
| 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 | The technical infrastructure uses conventional cloud and server resources comparable to those of standard web applications. No specialized mining or high-intensity computation is performed. Upon activation of the full consensus layer, the network will implement a Proof-of-Stake (PoS) mechanism combined with sequential timestamping (Proof-of-History concept). This design minimizes electricity usage compared to energy-intensive Proof-of-Work systems and therefore limits adverse climate impacts. No material emissions, hazardous waste, or significant environmental externalities are currently associated with the operation or development of the LEA Blockchain. The issuer and its technical partners will continue to monitor the project's environmental footprint and adopt energy-efficient hosting and validator practices upon decentralization. |
|||
| 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 | The current infrastructure consists of one dedicated server (Intel Core i7-6700, NVMe SSD storage, 64GB RAM), operating continuously (24/7). Based on typical power consumption benchmarks for comparable hardware and an average operational load below 10%, the estimated average power consumption is approximately 70 watts. This corresponds to an estimated annual energy consumption of approximately 613 kWh. The LEA Blockchain does not use proof-of-work mining and does not require GPU-based computation. For estimation purposes, an initial decentralized validator configuration is assumed to consist of approximately 10 validator nodes, each operating comparable server hardware with an estimated average power consumption of approximately 100 watts per node. Under this assumption, estimated annual network energy consumption would amount to approximately 8,760 kWh. Actual energy consumption will depend on the final consensus configuration, validator participation, and infrastructure specifications. Updated quantitative measurements will be provided once the decentralized validator network is fully deployed. |
|||
| 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 | Current prototype phase: Estimated average power consumption: approximately 70 watts Continuous operation (24/7) Estimated annual energy consumption: 0.07 kW × 24 × 365 = approximately 613 kWh per year Planned initial decentralized configuration: For estimation of network-level energy consumption, an initial configuration of approximately 10 validator nodes has been assumed. Each validator node is assumed to operate on comparable dedicated or cloud-based server infrastructure with an estimated average power consumption of approximately 100 watts per node. Estimated annual consumption per validator node: 0.1 kW × 24 × 365 = approximately 876 kWh per year. Estimated annual network consumption (10 validators): approximately 8,760 kWh per year. These calculations are based on: continuous operation (24/7), CPU-based validation, no GPU-intensive mining, no proof-of-work mechanism. Actual consumption may vary depending on final consensus implementation, validator participation levels and infrastructure specifications. No direct measurement of energy consumption at distributed validator level is currently available, as the decentralized validator network has not yet been deployed. |
|||
| 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 | ||||