White paper drafted under the European Markets in Crypto-Assets Regulation (EU) 2023/1114 for FFG MNCR2MKHP
Preamble
00. Table of Contents
- Preamble
- 01. Date of notification
- 02. Statement in accordance with Article 6(3) of Regulation (EU) 2023/1114
- 03. Compliance statement in accordance with Article 6(6) of Regulation (EU) 2023/1114
- 04. Statement in accordance with Article 6(5), points (a), (b), (c), of Regulation (EU) 2023/1114
- 05. Statement in accordance with Article 6(5), point (d), of Regulation (EU) 2023/1114
- 06. Statement in accordance with Article 6(5), points (e) and (f), of Regulation (EU) 2023/1114
- Summary
- 07. Warning in accordance with Article 6(7), second subparagraph, of Regulation (EU) 2023/1114
- 08. Characteristics of the crypto-asset
- 09. Information about the quality and quantity of goods or services to which the utility tokens give access and restrictions on the transferability
- 10. Key information about the offer to the public or admission to trading
- Part A – Information about the offeror or the person seeking admission to trading
- A.1 Name
- A.2 Legal form
- A.3 Registered address
- A.4 Head office
- A.5 Registration date
- A.6 Legal entity identifier
- A.7 Another identifier required pursuant to applicable national law
- A.8 Contact telephone number
- A.9 E-mail address
- A.10 Response time (Days)
- A.11 Parent company
- A.12 Members of the management body
- A.13 Business activity
- A.14 Parent company business activity
- A.15 Newly established
- A.16 Financial condition for the past three years
- A.17 Financial condition since registration
- Part B – Information about the issuer, if different from the offeror or person seeking admission to trading
- B.1 Issuer different from offeror or person seeking admission to trading
- B.2 Name
- B.3 Legal form
- B.4 Registered address
- B.5 Head office
- B.6 Registration date
- B.7 Legal entity identifier
- B.8 Another identifier required pursuant to applicable national law
- B.9 Parent company
- B.10 Members of the management body
- B.11 Business activity
- B.12 Parent company business activity
- 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
- C.2 Legal form
- C.3 Registered address
- C.4 Head office
- C.5 Registration date
- C.6 Legal entity identifier
- C.7 Another identifier required pursuant to applicable national law
- C.8 Parent company
- C.9 Reason for crypto-asset white paper preparation
- C.10 Members of the management body
- C.11 Operator business activity
- C.12 Parent company business activity
- C.13 Other persons drawing up the crypto-asset white paper according to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114
- C.14 Reason for drawing the white paper by persons referred to in Article 6(1), second subparagraph, of Regulation (EU) 2023/1114
- Part D – Information about the crypto-asset project
- D.1 Crypto-asset project name
- D.2 Crypto-assets name
- D.3 Abbreviation
- D.4 Crypto-asset project description
- D.5 Details of all natural or legal persons involved in the implementation of the crypto-asset project
- D.6 Utility Token Classification
- D.7 Key Features of Goods/Services for Utility Token Projects
- D.8 Plans for the token
- D.9 Resource allocation
- D.10 Planned use of collected funds or crypto-assets
- Part E – Information about the offer to the public of crypto-assets or their admission to trading
- E.1 Public offering or admission to trading
- E.2 Reasons for public offer or admission to trading
- E.3 Fundraising target
- E.4 Minimum subscription goals
- E.5 Maximum subscription goals
- E.6 Oversubscription acceptance
- E.7 Oversubscription allocation
- E.8 Issue price
- E.9 Official currency or any other crypto-assets determining the issue price
- E.10 Subscription fee
- E.11 Offer price determination method
- E.12 Total number of offered/traded crypto-assets
- E.13 Targeted holders
- E.14 Holder restrictions
- E.15 Reimbursement notice
- E.16 Refund mechanism
- E.17 Refund timeline
- E.18 Offer phases
- E.19 Early purchase discount
- E.20 Time-limited offer
- E.21 Subscription period beginning
- E.22 Subscription period end
- E.23 Safeguarding arrangements for offered funds/crypto-assets
- E.24 Payment methods for crypto-asset purchase
- E.25 Value transfer methods for reimbursement
- E.26 Right of withdrawal
- E.27 Transfer of purchased crypto-assets
- E.28 Transfer time schedule
- E.29 Purchaser's technical requirements
- E.30 Crypto-asset service provider (CASP) name
- E.31 CASP identifier
- E.32 Placement form
- E.33 Trading platforms name
- E.34 Trading platforms Market identifier code (MIC)
- E.35 Trading platforms access
- E.36 Involved costs
- E.37 Offer expenses
- E.38 Conflicts of interest
- E.39 Applicable law
- E.40 Competent court
- Part F – Information about the crypto-assets
- F.1 Crypto-asset type
- F.2 Crypto-asset functionality
- F.3 Planned application of functionalities
- A description of the characteristics of the crypto asset, 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
- F.5 The type of submission
- F.6 Crypto-asset characteristics
- F.7 Commercial name or trading name
- F.8 Website of the issuer
- F.9 Starting date of offer to the public or admission to trading
- F.10 Publication date
- F.11 Any other services provided by the issuer
- F.12 Language or languages of the crypto-asset white paper
- 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
- F.14 Functionally fungible group digital token identifier
- F.15 Voluntary data flag
- F.16 Personal data flag
- F.17 LEI eligibility
- F.18 Home Member State
- F.19 Host Member States
- Part G – Information on the rights and obligations attached to the crypto-assets
- G.1 Purchaser rights and obligations
- G.2 Exercise of rights and obligations
- G.3 Conditions for modifications of rights and obligations
- G.4 Future public offers
- G.5 Issuer retained crypto-assets
- G.6 Utility token classification
- G.7 Key features of goods/services of utility tokens
- G.8 Utility tokens redemption
- G.9 Non-trading request
- G.10 Crypto-assets purchase or sale modalities
- G.11 Crypto-assets transfer restrictions
- G.12 Supply adjustment protocols
- G.13 Supply adjustment mechanisms
- G.14 Token value protection schemes
- G.15 Token value protection schemes description
- G.16 Compensation schemes
- G.17 Compensation schemes description
- G.18 Applicable law
- G.19 Competent court
- Part H – information on the underlying technology
- H.1 Distributed ledger technology (DLT)
- H.2 Protocols and technical standards
- H.3 Technology used
- H.4 Consensus mechanism
- H.5 Incentive mechanisms and applicable fees
- H.6 Use of distributed ledger technology
- H.7 DLT functionality description
- H.8 Audit
- H.9 Audit outcome
- Part I – Information on risks
- I.1 Offer-related risks
- I.2 Issuer-related risks
- I.3 Crypto-assets-related risks
- I.4 Project implementation-related risks
- I.5 Technology-related risks
- I.6 Mitigation measures
- 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
- S.1 Name
- S.2 Relevant legal entity identifier
- S.3 Name of the crypto-asset
- S.4 Consensus Mechanism
- S.5 Incentive Mechanisms and Applicable Fees
- S.6 Beginning of the period to which the disclosure relates
- S.7 End of the period to which the disclosure relates
- S.8 Energy consumption
- S.9 Energy consumption sources and methodologies
- S.10 Renewable energy consumption
- S.11 Energy intensity
- S.12 Scope 1 DLT GHG emissions – Controlled
- S.13 Scope 2 DLT GHG emissions – Purchased
- S.14 GHG intensity
- S.15 Key energy sources and methodologies
- S.16 Key GHG sources and methodologies
01. Date of notification
02. Statement in accordance with Article 6(3) of Regulation (EU) 2023/1114
03. Compliance statement in accordance with Article 6(6) of Regulation (EU) 2023/1114
04. Statement in accordance with Article 6(5), points (a), (b), (c), of Regulation (EU) 2023/1114
05. Statement in accordance with Article 6(5), point (d), of Regulation (EU) 2023/1114
06. Statement in accordance with Article 6(5), points (e) and (f), of Regulation (EU) 2023/1114
Summary
07. Warning in accordance with Article 6(7), second subparagraph, of Regulation (EU) 2023/1114
08. Characteristics of the crypto-asset
The GRASS crypto-asset referred to in this white paper is a crypto-asset other than EMTs and ARTs and is implemented on the Solana network as a token under the SPL token standard, according to the DTI FFG shown in section F.14, as of 2026-09-01. Its token address is Grass7B4RdKfBCjTKgSqnXkqjwiGvQyFbuSCUJr3XXjs (source: https://solscan.io/token/Grass7B4RdKfBCjTKgSqnXkqjwiGvQyFbuSCUJr3XXjs, accessed 2026-09-01). The maximum supply of GRASS is 1,000,000,000 tokens. The first activity of the crypto-asset can be viewed on 2024-08-03 (transaction hash: SjfxfALUqCjZQCty5UjoSjcspG2MCAAmjTbh9yFc3eXhTkGFmGZRF9Bpi4PkkxtsDrsKmjYsS1mQd6aDXTdChpB, source: https://solscan.io/tx/SjfxfALUqCjZQCty5UjoSjcspG2MCAAmjTbh9yFc3eXhTkGFmGZRF9Bpi4PkkxtsDrsKmjYsS1mQd6aDXTdChpB, accessed 2026-09-01).
According to publicly available information (sources: https://www.grass.io/, https://grass-foundation.gitbook.io/grass-docs, accessed 2026-09-01), Grass is a network through which individual users make their unused internet bandwidth available for the collection of publicly accessible web data. Users install the Grass application, which forwards web requests over their connection while that connection is idle, and a network of nodes, routers and validators routes the traffic and assembles the results into structured datasets that are supplied to artificial-intelligence developers and other enterprise customers. The stated purpose of the project is to compensate individual users for a resource they already hold and would otherwise leave unused, while providing purchasers of web data with a traceable source of that data.
Within that project, GRASS is the token through which the network rewards and coordinates the participants it depends on. It is the reward paid to users who contribute bandwidth, and it is the asset that holders stake to routers, the participants that carry traffic across the network, which is how capacity is directed and the network is intended to be secured. Public sources indicate that a governance function for token holders is intended but is not implemented as at the date of this white paper. GRASS does not entitle its holders to any share of the revenue of the network, to any dividend, interest or repayment, to any claim against any operator of the network, or to any right of redemption.
The crypto-asset does not grant any legally enforceable or contractual rights or obligations to its holders or purchasers. Any functionalities accessible through the underlying technology are purely technical or operational in nature and do not confer rights comparable to ownership, profit participation, governance, or similar entitlements known from traditional financial instruments.
09. Information about the quality and quantity of goods or services to which the utility tokens give access and restrictions on the transferability
As defined in Article 3(9) of Regulation (EU) 2023/1114 of the European Parliament and of the Council of 31 May 2023 on Markets in Crypto-Assets – amending Regulations (EU) No 1093/2010 and (EU) No 1095/2010 and Directives 2013/36/EU and (EU) 2019/1937 – a utility token is “a type of crypto-asset that is only intended to provide access to a good or a service supplied by its issuer”. This crypto-asset does not qualify as a utility token, as its intended use goes beyond providing access to a good or a service supplied solely by the issuer.
10. Key information about the offer to the public or admission to trading
Crypto Risk Metrics GmbH is seeking admission to trading on the Payward Global Solutions LTD (“Kraken”) platform in the European Union in accordance with Article 5 of Regulation (EU) 2023/1114 of the European Parliament and of the Council of 31 May 2023 on Markets in Crypto-Assets, and amending Regulations (EU) No 1093/2010 and (EU) No 1095/2010 and Directives 2013/36/EU and (EU) 2019/1937. The admission to trading is not accompanied by a public offer of the crypto-asset.
Part A – Information about the offeror or the person seeking admission to trading
A.1 Name
A.2 Legal form
A.3 Registered address
A.4 Head office
A.5 Registration date
A.6 Legal entity identifier
A.7 Another identifier required pursuant to applicable national law
A.8 Contact telephone number
A.9 E-mail address
A.10 Response time (Days)
A.11 Parent company
A.12 Members of the management body
| Identity | Function | Business Address |
|---|---|---|
A.13 Business activity
Crypto Risk Metrics GmbH is a technical service provider that supports regulated entities in fulfilling their regulatory requirements. Among other services, Crypto Risk Metrics GmbH acts as a data provider for ESG data under Article 66(5). In light of the requirements set out in Articles 4(7), 5(4) and 66(3) of Regulation (EU) 2023/1114 of the European Parliament and of the Council of 31 May 2023 on Markets in Crypto-Assets, and amending Regulations (EU) No 1093/2010 and (EU) No 1095/2010 and Directives 2013/36/EU and (EU) 2019/1937, Crypto Risk Metrics GmbH aims to provide central services for crypto-asset white papers.
A.14 Parent company business activity
A.15 Newly established
A.16 Financial condition for the past three years
Crypto Risk Metrics GmbH, founded in 2018 and based in Hamburg (HRB 154488), has undergone several strategic shifts in its business focus since incorporation. Due to these changes in business model and operational direction over time, the financial figures from earlier years are only comparable to a limited extent with the company’s current commercial activities. The present business model – centred on regulatory technology and risk analytics in the context of the MiCA framework – has been developed progressively and can realistically be considered fully operational since approximately 2024.
The company’s financial trajectory over the past three years reflects the transition from exploratory development towards market-ready product delivery. Profit or loss after tax for the last three financial years is as follows:
2024 (unaudited): loss of EUR 50,891.81
2023 (unaudited): loss of EUR 27,665.32
2022: profit of EUR 104,283.00
The profit in 2022 resulted primarily from legacy consulting activities, which were discontinued as part of the company’s repositioning.
The losses in 2023 and 2024 resulted from strategic investments in the development of proprietary software infrastructure, regulatory frameworks, and compliance technology for the MiCA ecosystem. During those periods, no substantial commercial revenues were expected, as resources were directed towards preparing the platform for market entry in a regulated environment.
A fundamental repositioning of the company occurred in 2023 and especially in 2024, when the focus shifted towards providing risk management, regulatory reporting, and supervisory compliance solutions for financial institutions and crypto-asset service providers. This marked a material shift in business operations and monetisation strategy.
Based on preliminary unaudited management information for the financial year 2025, revenues are expected to have exceeded EUR 800,000, while preliminary net profit is expected to exceed EUR 100,000.
These figures are not audited and are not based on a finalised annual financial statement. Accordingly, they remain subject to finalisation and may differ from the figures ultimately reported in the annual financial statements.
With the regulatory environment now taking shape and the platform commercially validated, it is assumed that the effects of the strategic developments will continue to materialise in 2026. The company foresees further scalability of its technology and growing market demand for regulatory compliance tools in the European crypto-asset sector.
No public subsidies or governmental grants have been received to date; all operations have been financed through shareholder contributions and internally generated resources. Crypto Risk Metrics GmbH has never accepted any payments in tokens from projects it has worked with and – due to its internal Conflicts of Interest Policy – never will.
A.17 Financial condition since registration
Part B – Information about the issuer, if different from the offeror or person seeking admission to trading
B.1 Issuer different from offeror or person seeking admission to trading
B.2 Name
B.3 Legal form
B.4 Registered address
B.5 Head office
B.6 Registration date
B.7 Legal entity identifier
B.8 Another identifier required pursuant to applicable national law
B.9 Parent company
B.10 Members of the management body
| Name | Function | Business address |
|---|---|---|
B.11 Business activity
Grass OpCo Ltd. operates the Grass Network and the software through which participants connect to it, comprising the Grass websites, the desktop and mobile applications, the browser extension, the participant dashboard and a non-custodial wallet application. It administers the Grass Rewards Program and the Grass Staking Program, under which it determines eligibility and effects the distribution of rewards in GRASS or USDC, and it operates routers within the network.
B.12 Parent company business activity
Grass Foundation is the parent of Grass OpCo Ltd. and holds the group's treasury, including the reserve allocated to the foundation and to ecosystem growth, which is applied to the ongoing operation and development of the Grass Network. It does not operate the network or contract with participants, those functions sitting with its subsidiaries, and it acts as their director.
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
C.2 Legal form
C.3 Registered address
C.4 Head office
C.5 Registration date
C.6 Legal entity identifier
C.7 Another identifier required pursuant to applicable national law
C.8 Parent company
C.9 Reason for crypto-asset white paper preparation
C.10 Members of the management body
C.11 Operator business activity
C.12 Parent company business activity
C.13 Other persons drawing up the crypto-asset white paper according to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114
C.14 Reason for drawing the white paper by persons referred to in Article 6(1), second subparagraph, of Regulation (EU) 2023/1114
Part D – Information about the crypto-asset project
D.1 Crypto-asset project name
D.2 Crypto-assets name
D.3 Abbreviation
D.4 Crypto-asset project description
According to publicly available information (sources: https://www.grass.io/, https://www.grass.io/learn/grass-101-what-is-grass/, https://grass-foundation.gitbook.io/grass-docs, accessed 2026-09-01), Grass is a network through which individual internet users make the unused capacity of their internet connection available for the collection of publicly accessible web data, and are rewarded for doing so. The project describes unused internet as the difference between the maximum speed of a user's internet plan and the capacity that user's own activity is consuming at a given moment, and states that the software yields automatically when the user's own devices demand the connection. The stated objective is to direct the value of that capacity to the users who already pay for it, on the project's position that institutions have long drawn on residential connections to read public websites without compensating the households concerned. The project states that it accesses public web data only, and does not access personal files, browsing history or other private data on a participant's device.
The network is assembled from four roles, described in the project's own documentation (sources: https://grass-foundation.gitbook.io/grass-docs/architecture/grass-node, https://grass-foundation.gitbook.io/grass-docs/architecture/router, https://grass-foundation.gitbook.io/grass-docs/architecture/validator, accessed 2026-09-01). Nodes are the participants' own devices, running a desktop or mobile application, a browser extension or a dedicated device marketed as the Grasshopper; a node relays web requests and returns the responses, and is assigned a reputation score based on the completeness, consistency, timeliness and availability of the data it handles. Routers are geographically distributed hubs that connect the nodes, meter the traffic passing through them and report volume, latency and node status. A validator initiates the web requests and verifies the results before they are settled, and the documentation states that the validator initially operates as a single centralised component, with a committee of validators employing a consensus mechanism described as a future development. The datasets assembled in this way are supplied to artificial-intelligence developers and other institutional customers. Participants' contributions are measured in Grass Points, which are divided into Uptime Points for making a connection available and Network Points for bandwidth actually used, with a fixed daily pool of 1,000,000 Network Points distributed in proportion to the bandwidth each participant supplied that day (source: https://grass-foundation.gitbook.io/grass-docs/how-to-guide/grass-points, accessed 2026-09-01). The project states expressly that installing or using its software is not a guarantee that any points or associated rewards will be earned (source: https://www.grass.io/learn/unlock-rewards-with-grass-points-earn-refer-and-grow-your-network/, accessed 2026-09-01).
The long-term evolution of the project depends on governance outcomes and technical, economic and regulatory considerations, and all future developments remain subject to change.
D.5 Details of all natural or legal persons involved in the implementation of the crypto-asset project
| Name of person | Type of person | Business address of person | Domicile of company |
|---|---|---|---|
D.6 Utility Token Classification
D.7 Key Features of Goods/Services for Utility Token Projects
D.8 Plans for the token
This section provides an overview of the historical developments related to the GRASS crypto-asset and a description of planned or anticipated project milestones as publicly communicated. All forward-looking elements are subject to significant uncertainty. They do not constitute commitments, assurances or guarantees, and may be modified, delayed or discontinued at any time.
There is no single formally published, dated roadmap for the GRASS token. Relevant developments and plans are communicated through the project's documentation, website and public updates (sources: https://solscan.io/tx/SjfxfALUqCjZQCty5UjoSjcspG2MCAAmjTbh9yFc3eXhTkGFmGZRF9Bpi4PkkxtsDrsKmjYsS1mQd6aDXTdChpB, https://grass-foundation.gitbook.io/grass-docs/introduction/grass-airdrop-one, https://grass-foundation.gitbook.io/grass-docs/introduction/grass, https://grass-foundation.gitbook.io/grass-docs/architecture/overview, https://www.grass.io/learn/grass-and-inference-launch-video-annotation-model-outperforming-claude-4, https://www.grass.io/learn/an-update-to-the-grass-points-model/, https://www.grass.io/learn/how-your-stage-2-rewards-allocation-works/, https://www.grass.io/learn/july-7-grass-token-holder-and-network-participant-call/, https://www.grass.io/learn/what-does-grass-actually-do-with-your-connection/, accessed 2026-09-01).
Past milestones:
- First on-chain activity of GRASS (2024-08-03): public on-chain data records activity involving the GRASS mint account through a multisignature vault execution on Solana. This transaction is treated as the first on-chain activity and does not, by itself, identify the controlling person or establish the complete legal circumstances of issuance.
- Airdrop One claiming opened (2024-10-28): eligible addresses were able to begin claiming from an allocation of 100,000,000 GRASS, representing 10 per cent of the stated maximum supply, for early users and community members.
- Extended Airdrop One claiming ended (2025-03-27): project documentation states that the extended claiming window ended at Solana block 329341917, described as approximately 2025-03-27.
- Commercial data products launched (2025): the project states that it began supplying data products and services in early 2025, which is the activity from which the network fees and revenue described in the token documentation are intended to arise.
- Contribution-points model updated (2025-10-08): the project announced that its points model would distinguish Uptime Points, relating principally to connection availability, from Network Points, relating to bandwidth actually used for web-data requests. The update was stated to apply from Epoch 11.
- Stage 2 reward claiming commenced (2026-07-22): the project made rewards for participation during Epochs 1 to 19 of Stage 2, being the period from 2024-10-14 to 2026-06-08, available in USDC rather than in GRASS. The project stated that the distribution would not create new GRASS emissions or change the circulating GRASS supply. The claim period was announced to run until 2027-01-22 or until all claims were made, whichever occurred first, with unclaimed rewards retained by the project.
- Managed wallet with staking made available (2026-07-22): the project made available a managed Solana wallet within its application, through which participants may claim the Stage 2 distribution, exchange GRASS for other supported tokens and stake GRASS from a minimum of 1 GRASS. The private key is generated and held by a third-party provider rather than by the project. Staking through third-party wallets remains available, and the seven-day unstaking period applies in either case.
Future milestones:
- Live Context Retrieval: the project has communicated plans to expand from training-data services into Live Context Retrieval products that provide current public-web context to artificial-intelligence systems. The recap of a token holder and network participant call held on 2026-07-07 referred to public product launches during summer 2026, while a later article published on 2026-08-26 continued to describe Live Context Retrieval as being developed. Completion and timing therefore remain unconfirmed.
- Prospective GRASS transaction uses: the token documentation states in future-oriented language that GRASS will be used for web-scraping transactions, dataset purchases and Live Context Retrieval usage. These functions are plans rather than confirmed current functionality and no implementation date is stated.
- Validator decentralisation: the architecture documentation states that the validator set is intended to transition from an initial centralised framework with a single validator to a decentralised committee of validators. No binding timetable is published.
- Possible future slashing: the staking documentation states that slashing is not currently part of the network and that future updates may introduce it, while the token documentation describes slashing as currently triggered manually with an expected transition to autonomous operation as the network develops. The current implementation position and any future activation date remain unresolved.
Note: All future milestones are subject to significant uncertainty, including but not limited to technical feasibility, regulatory developments, market adoption and community governance decisions. The project may modify, delay or discontinue any of these initiatives at any time. Past implementation or performance outcomes do not constitute an indication of future results, and any such changes may materially affect the characteristics, availability or perceived value of the GRASS crypto-asset for its holders.
D.9 Resource allocation
According to publicly available information, the development of the project was funded through three private financing rounds. A pre-seed round of approximately USD 1,000,000 closed in January 2023, with No Limit Holdings and Big Brain Holdings. A seed round of approximately USD 3,500,000 closed in December 2023, led by Polychain Capital and Tribe Capital with participation from Bitscale Capital and Big Brain Holdings. A Series A round closed in September 2024, led by Hack VC with participation from investors including Polychain Capital, Delphi Digital and Lattice; the amount raised in that round has not been publicly disclosed. The disclosed amounts across the first two rounds total approximately USD 4,500,000, and no reliable aggregate can be stated for the total amount raised because the Series A round remains undisclosed. These figures rest on public reporting and cannot be independently verified.
The issuer, foundation, or entities associated with the GRASS token have not independently confirmed the occurrence, precise amounts or current status of these reported allocations and fundraising figures. As a result, the referenced allocation figures cannot be independently verified and should be considered indicative only. Token distribution changes can negatively impact the investor.
D.10 Planned use of collected funds or crypto-assets
Part E – Information about the offer to the public of crypto-assets or their admission to trading
E.1 Public offering or admission to trading
E.2 Reasons for public offer or admission to trading
The purpose of seeking admission to trading is to enable the crypto-asset to be listed on a regulated platform in accordance with the applicable provisions of Regulation (EU) 2023/1114 and Commission Implementing Regulation (EU) 2024/2984. The white paper has been drawn up to comply with the transparency requirements applicable to trading venues.
E.3 Fundraising target
E.4 Minimum subscription goals
E.5 Maximum subscription goals
E.6 Oversubscription acceptance
E.7 Oversubscription allocation
E.8 Issue price
E.9 Official currency or any other crypto-assets determining the issue price
E.10 Subscription fee
E.11 Offer price determination method
E.12 Total number of offered/traded crypto-assets
E.13 Targeted holders
E.14 Holder restrictions
Holder restrictions are subject to the rules applicable to the crypto-asset service provider, as well as any additional restrictions that provider may impose.
E.15 Reimbursement notice
E.16 Refund mechanism
E.17 Refund timeline
E.18 Offer phases
E.19 Early purchase discount
E.20 Time-limited offer
E.21 Subscription period beginning
E.22 Subscription period end
E.23 Safeguarding arrangements for offered funds/crypto-assets
E.24 Payment methods for crypto-asset purchase
E.25 Value transfer methods for reimbursement
E.26 Right of withdrawal
E.27 Transfer of purchased crypto-assets
E.28 Transfer time schedule
E.29 Purchaser's technical requirements
E.30 Crypto-asset service provider (CASP) name
E.31 CASP identifier
E.32 Placement form
E.33 Trading platforms name
E.34 Trading platforms Market identifier code (MIC)
E.35 Trading platforms access
The token is intended to be listed on the trading platform operated by Payward Global Solutions LTD ("Kraken"). Access to this platform depends on regional availability and user eligibility under Kraken’s terms and conditions. Investors should consult Kraken’s official documentation to determine whether they meet the requirements for account creation and token trading.
E.36 Involved costs
The costs involved in accessing the trading platform depend on the specific fee structure and terms of the respective crypto-asset service provider. These may include trading fees, deposit or withdrawal charges, and network-related transaction fees. Investors are advised to consult the applicable fee schedule of the chosen platform before engaging in trading activities.
E.37 Offer expenses
Not applicable, as this white paper is written to seek admission to trading, not for the initial offer to the public.
E.38 Conflicts of interest
MiCA-compliant crypto-asset service providers shall have strong measures in place in order to manage conflicts of interest. Due to the broad audience this white paper addresses, potential investors should always check the conflicts-of-interest policy of their respective counterparty.
Crypto Risk Metrics GmbH has established, implemented, and documented comprehensive internal policies and procedures for the identification, prevention, management, and documentation of conflicts of interest in accordance with applicable regulatory requirements. These internal measures are actively applied within the organisation. For the purposes of this specific assessment and the crypto-asset covered by this white paper, a token-specific review has been conducted by Crypto Risk Metrics GmbH. Based on this individual review, no conflicts of interest relevant to this crypto-asset have been identified at the time of preparation of this white paper.
E.39 Applicable law
Not applicable, as this white paper is written to seek admission to trading, not for the initial offer to the public.
E.40 Competent court
Not applicable, as this white paper is written to seek admission to trading, not for the initial offer to the public.
Part F – Information about the crypto-assets
F.1 Crypto-asset type
F.2 Crypto-asset functionality
According to publicly available information (sources: https://grass-foundation.gitbook.io/grass-docs, https://www.grass.io/, accessed 2026-09-01), GRASS is a token on the Solana network and has been transferable since the first distribution to participants opened on 2024-10-28. Its functions are to serve as the asset in which participation in the network is rewarded and as the asset staked to the routers that carry the network's traffic. A governance function is described as intended and is not implemented.
Rewards. Participation is measured in Grass Points rather than in the crypto-asset itself, and the crypto-asset is the asset in which the resulting rewards are settled. The first such distribution allocated 100,000,000 GRASS, being 10 per cent of the total supply, against points earned during the first stage of the network, with claims opening on 2024-10-28 and the extended claiming window closing at Solana block 329341917 (source: https://grass-foundation.gitbook.io/grass-docs/introduction/grass-airdrop-one, accessed 2026-09-01). Points themselves carry no monetary value and are not transferable between participants, and the project states that the award of points and of any associated reward is determined programmatically and is not guaranteed (sources: https://www.grass.io/terms-and-conditions/, https://www.grass.io/learn/unlock-rewards-with-grass-points-earn-refer-and-grow-your-network/, accessed 2026-09-01).
Staking and delegation. Holders may delegate GRASS to a router and thereby become eligible for a share of the rewards awarded to that router, after deduction of the commission that router charges. There is no minimum staking period, and an unstaking request is followed by a seven-day period during which the tokens remain locked before they can be withdrawn. The volume of stake delegated to a router is stated to determine how frequently that router is awarded traffic, which is the mechanism by which stake influences the routing of the network's capacity (sources: https://grass-foundation.gitbook.io/grass-docs/introduction/grass-staking, https://grass-foundation.gitbook.io/grass-docs/architecture/router, accessed 2026-09-01). The documentation states that slashing, the destruction of a portion of a router's stake in response to conduct such as reporting invalid traffic or censoring participants, is not implemented in the protocol at present but may be introduced by a future update. Where slashing is introduced, delegated tokens would be exposed to it.
Governance. Public sources indicate that decisions on the deployment of the reserve held for the foundation and for ecosystem growth are intended to be directed by token-holder governance (source: https://grass-foundation.gitbook.io/grass-docs/introduction/grass-tokenomics, accessed 2026-09-01). No governance process, voting mechanism or scope of decisions reserved to holders has been published, and no such function is exercisable as at the date of this white paper. The realisation of this intended functionality depends on technical implementation and governance decisions, and no binding assurance can be given that all intended uses will be realised as described.
Beyond the functions described above, GRASS has no further protocol-level functionality as of the date of this white paper. It is not used to pay transaction fees on the Solana network, where fees are payable in that network's own native asset, and it plays no role in that network's consensus mechanism.
The GRASS token does not confer ownership, profit participation, governance rights over the issuer or any related entity in a corporate-law sense, or any form of legally enforceable economic entitlement. All functionalities are technical in nature and relate exclusively to interactions within the Grass protocol environment. The actual usability of GRASS depends on factors such as system stability, governance decisions, development progress and the operational conditions of the Solana blockchain, which are outside the control of token holders.
F.3 Planned application of functionalities
Future milestones:
- Live Context Retrieval: the project has communicated plans to expand from training-data services into Live Context Retrieval products that provide current public-web context to artificial-intelligence systems. The recap of a token holder and network participant call held on 2026-07-07 referred to public product launches during summer 2026, while a later article published on 2026-08-26 continued to describe Live Context Retrieval as being developed. Completion and timing therefore remain unconfirmed.
- Prospective GRASS transaction uses: the token documentation states in future-oriented language that GRASS will be used for web-scraping transactions, dataset purchases and Live Context Retrieval usage. These functions are plans rather than confirmed current functionality and no implementation date is stated.
- Validator decentralisation: the architecture documentation states that the validator set is intended to transition from an initial centralised framework with a single validator to a decentralised committee of validators. No binding timetable is published.
- Possible future slashing: the staking documentation states that slashing is not currently part of the network and that future updates may introduce it, while the token documentation describes slashing as currently triggered manually with an expected transition to autonomous operation as the network develops. The current implementation position and any future activation date remain unresolved.
Note: All future milestones are subject to significant uncertainty, including but not limited to technical feasibility, regulatory developments, market adoption and community governance decisions. The project may modify, delay or discontinue any of these initiatives at any time. Past implementation or performance outcomes do not constitute an indication of future results, and any such changes may materially affect the characteristics, availability or perceived value of the GRASS crypto-asset for its holders.
A description of the characteristics of the crypto asset, 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
F.5 The type of submission
F.6 Crypto-asset characteristics
The crypto-asset referred to herein is a crypto-asset other than EMTs and ARTs, and is available on the Solana network. The crypto-asset is fungible up to 9 digits after the decimal point. The crypto-asset constitutes a digital representation recorded on distributed-ledger technology and does not confer ownership, governance, profit participation, or any other legally enforceable rights. Any functionalities associated with the token are limited to potential technical features within the relevant platform environment. These functionalities do not represent contractual entitlements and may depend on future development decisions, technical design choices, and operational conditions. The crypto-asset does not embody intrinsic economic value; instead, its value, if any, is determined exclusively by market dynamics such as supply, demand, and liquidity in secondary markets.
F.7 Commercial name or trading name
F.8 Website of the issuer
F.9 Starting date of offer to the public or admission to trading
F.10 Publication date
F.11 Any other services provided by the issuer
No such services are currently known to be provided by the issuer. However, it cannot be excluded that additional services exist or may be offered in the future outside the scope of Regulation (EU) 2023/1114.
F.12 Language or languages of the crypto-asset white paper
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
F.14 Functionally fungible group digital token identifier
F.15 Voluntary data flag
F.16 Personal data flag
F.17 LEI eligibility
F.18 Home Member State
F.19 Host Member States
Part G – Information on the rights and obligations attached to the crypto-assets
G.1 Purchaser rights and obligations
The crypto-asset does not grant any legally enforceable or contractual rights or obligations to its holders or purchasers. Any functionalities accessible through the underlying technology are of a purely technical or operational nature and do not constitute rights comparable to ownership, profit participation, governance, or similar entitlements known from traditional financial instruments. Accordingly, holders do not acquire any legally enforceable claim against the issuer of the crypto-asset or any third party.
G.2 Exercise of rights and obligations
As the crypto-asset does not confer any legally enforceable rights or obligations, there are no applicable procedures or conditions for their exercise. Any interaction or functionality that may be available within the project’s technical infrastructure – such as participation mechanisms or protocol-level features – serves operational purposes only and does not create, evidence, or constitute any contractual or statutory entitlement.
G.3 Conditions for modifications of rights and obligations
As the crypto-asset does not confer any legally enforceable rights or obligations, there are no conditions or mechanisms for modifying such rights or obligations. Adjustments to the technical protocol, smart contract logic, or related systems may occur in the ordinary course of development or maintenance. Such changes do not alter the legal position of holders, as no contractual rights exist and no rights arise under applicable law or regulation. Holders should not interpret technical updates or governance-related changes as amendments to legally binding entitlements.
G.4 Future public offers
Information on future offers to the public of crypto-assets was not available at the time of writing this white paper (2026-08-31).
G.5 Issuer retained crypto-assets
G.6 Utility token classification
G.7 Key features of goods/services of utility tokens
G.8 Utility tokens redemption
G.9 Non-trading request
G.10 Crypto-assets purchase or sale modalities
G.11 Crypto-assets transfer restrictions
The crypto-assets themselves are not subject to any technical or contractual transfer restrictions and are generally freely transferable. However, crypto-asset service providers may impose restrictions on buyers or sellers in accordance with applicable laws, internal policies or contractual terms agreed with their clients.
G.12 Supply adjustment protocols
G.13 Supply adjustment mechanisms
Not applicable.
G.14 Token value protection schemes
G.15 Token value protection schemes description
G.16 Compensation schemes
G.17 Compensation schemes description
G.18 Applicable law
This white paper is submitted in the context of an application for admission to trading on a trading platform established in the European Union. Accordingly, this white paper shall be governed by the laws of the Federal Republic of Germany.
G.19 Competent court
Any disputes arising in relation to this white paper or the admission to trading may be brought before the competent courts in Hamburg, Germany.
Part H – information on the underlying technology
H.1 Distributed ledger technology (DLT)
The crypto-asset in scope is implemented on the Solana network following the standards described below.
H.2 Protocols and technical standards
The crypto-asset that is the subject of this white paper is available on the Solana network.
The following applies to Solana:
The crypto-asset is implemented on the Solana blockchain, a decentralised distributed-ledger network designed to support transaction processing and the execution of on-chain programs. The network relies on a set of technical protocols, cryptographic standards, and program frameworks intended to enable secure transaction validation, deterministic execution of instructions, and interoperability across the Solana ecosystem. The most relevant technical standards and protocols are outlined below.
1. Network Architecture and Core Protocols
The Solana network is structured as a peer-to-peer validator network in which independent nodes maintain the distributed ledger and process transactions.
- Solana uses Proof-of-History (PoH) as a cryptographic timing and ordering mechanism, while validator participation and voting are stake-weighted under its Proof-of-Stake model and Tower BFT consensus process.
- Tower BFT: A Byzantine fault tolerant consensus mechanism, derived from PBFT, that governs validator voting and block confirmation.
- Turbine: A block propagation protocol that distributes blocks across the validator network by splitting them into smaller data fragments (“shreds”) and transmitting them through a layered tree-based structure.
- Gulf Stream: A transaction forwarding mechanism that routes transactions directly to upcoming block producers and thereby limits the need for a global transaction mempool.
- Sealevel: A parallel transaction execution engine that enables non-conflicting transactions and programs to execute simultaneously across multiple processing threads.
Together, these mechanisms support transaction processing while maintaining a synchronised and verifiable ledger state across participating validator nodes.
2. Address and Cryptographic Standards
Accounts and transactions on the Solana network rely on defined cryptographic primitives and address formats.
- Account Addresses: Accounts are identified by 32-byte addresses. Externally controlled accounts typically use Ed25519 key pairs, while program-derived addresses (PDAs) are deterministically derived off-curve addresses that do not correspond to a private key.
- Transaction Signatures: Transactions are authorised through Ed25519 signatures associated with the account owner’s keypair.
- Hashing: Sequential SHA-256 hashing is used within the Proof-of-History mechanism to generate a verifiable ordering of events.
- Program Derived Addresses (PDAs): Deterministically generated addresses derived through hashing procedures that ensure the resulting address does not correspond to a private key, thereby enabling secure program-controlled accounts.
These cryptographic mechanisms provide the basis for transaction authentication, deterministic account control, and verifiable execution of on-chain instructions.
3. Networking and Data Transmission Standards
Communication between validator nodes and network participants follows defined networking protocols and technical constraints.
- QUIC is used for transaction ingress and TPU-related forwarding paths on Solana validators, alongside other networking channels used across the cluster.
- UDP-based propagation: Utilised for distributing block fragments (“shreds”) across the network through the Turbine protocol.
- Transaction size limits: The maximum transaction size of approximately 1,232 bytes is aligned with the IPv6 minimum transmission unit (MTU) after accounting for network headers, and is intended to enable atomic transmission without fragmentation.
- JSON-RPC interfaces: Standardised APIs used by wallets, applications, and infrastructure providers to submit transactions and query blockchain state.
These standards support interoperability between network nodes, developer infrastructure, and user-facing applications interacting with the Solana ledger.
4. Token and Program Standards (Solana Program Library)
Tokens on Solana are commonly implemented using either the original Token Program or the Token Extension Program (Token-2022), each of which defines standardised token behaviour through on-chain program logic.
Within this framework:
- A token type is represented by a mint account, which defines parameters such as total supply and mint authority.
- Individual token balances are stored in token accounts, which hold balances associated with a specific mint and owner address.
- Interactions with tokens occur through instructions executed by the relevant token program rather than through separate token-specific smart contracts.
These programmatic standards enable consistent token management across the Solana ecosystem. Projects may also integrate metadata functionality, for example through the Metaplex Token Metadata Program or, where applicable, through Token-2022 metadata extensions.
5. Protocol Development and Improvement Standards
Technical changes to the Solana protocol may be proposed and discussed through Solana Improvement Documents (SIMDs). These proposals document suggested modifications to protocol behaviour, economic parameters, or technical limits. Accepted changes may be implemented through updates to validator software and related developer tooling used by network participants.
H.3 Technology used
The crypto-asset that is the subject of this white paper is available on the Solana network.
The following applies to Solana:
1. Solana-Compatible Wallets: The tokens are generally supported by wallets compatible with Solana’s token programs.
2. Decentralised Ledger: The Solana blockchain acts as a decentralised ledger for all token transactions, with the intention of preserving a tamper-resistant record of token transfers and ownership in order to ensure both transparency and security.
3. SPL Token Program: Tokens on Solana are commonly implemented using either the original Token Program or the Token Extension Program (Token-2022), which provide standardised on-chain logic for token creation, issuance, transfer, and account management. Unlike the ERC-20 model on Ethereum, where a project typically deploys its own token contract, Solana tokens generally rely on shared token-program infrastructure, which promotes a high degree of standardisation across the ecosystem.
4. Blockchain Scalability: Solana is designed to support high transaction throughput and comparatively low transaction fees, with the intention of enabling efficient token transfers and related on-chain operations.
Security Protocols for Asset Custody and Transactions:
1. Private Key Management: To safeguard their token holdings, users must securely store their wallet’s private keys and recovery phrases.
2. Cryptographic Integrity: Solana uses Ed25519 digital signatures to authenticate transactions submitted by authorised signers, thereby supporting the integrity and verifiability of token transfers.
H.4 Consensus mechanism
The crypto-asset that is the subject of this white paper is available on the Solana network.
The following applies to Solana:
Solana uses a combination of Proof-of-History (PoH) and Proof-of-Stake (PoS). The core concepts of the mechanism are intended to work as follows:
Core Concepts
1. Proof-of-History (PoH):
PoH is a cryptographic ordering and timing mechanism that provides evidence that data existed in a particular sequence and that time passed between proofs.
Verifiable Delay Function (VDF): PoH relies on a sequential hash-based proof process that Solana describes as VDF-like. This sequence of hashes provides a verifiable order of events, enabling the network to efficiently agree on the sequence of transactions.
2. Proof-of-Stake (PoS):
Validator Selection: Leader slots are assigned through the network’s leader schedule, which is stake-weighted. The more SOL staked, the higher the chance of being selected to validate transactions and produce new blocks.
Delegation: Token holders can delegate their SOL tokens to validators, earning rewards proportional to their stake while contributing to the network's security.
Consensus Process
1. Transaction Validation:
Transactions are broadcasted to the network and collected by validators. Each transaction is validated to ensure it meets the network’s criteria, such as having correct signatures and sufficient funds.
2. PoH Sequence Generation:
A validator generates a sequence of hashes using PoH, each containing a timestamp and the previous hash. This process creates a historical record of transactions, establishing a cryptographic clock for the network.
3. Block Production:
The network uses PoS to select a leader validator based on their stake. The leader is responsible for bundling the validated transactions into a block. The leader validator uses the PoH sequence to order transactions within the block, ensuring that all transactions are processed in the correct order.
4. Consensus and Finalisation:
Other validators vote on the ledger state associated with the block. A block may first become confirmed and later finalised once it reaches the network’s strongest confirmation state.
Security and Economic Incentives
1. Incentives for Validators:
Block Rewards: Validators earn rewards for producing and validating blocks. These rewards are distributed in SOL tokens and are proportional to the validator’s stake and performance.
Transaction Fees: Validators also earn transaction fees from the transactions included in the blocks they produce. These fees provide an additional incentive for validators to process transactions efficiently.
2. Security:
Staking: Staking provides economic alignment, and Solana documentation notes that slashing has been discussed as a future mechanism for intentional malicious behaviour, but is not implemented yet.
Delegated Staking: Token holders can delegate their SOL tokens to validators, intended to enhance network security and decentralisation. Delegators share in the rewards and are incentivised to choose reliable validators.
3. Economic Penalties:
Slashing (planned): Validators can be penalised for malicious behaviour, such as double-signing or producing invalid blocks. This penalty, known as slashing, results in the loss of a portion of the staked tokens, discouraging dishonest actions.
H.5 Incentive mechanisms and applicable fees
The crypto-asset that is the subject of this white paper is available on the Solana network.
The following applies to Solana:
1. Validators:
Validators participate in block production and voting under Solana’s stake-weighted model. They may receive staking-related rewards and a share of transaction-fee income. Under Solana’s fee model, the base fee is split between burn and validator compensation, while any prioritisation fee is paid to the validator.
Transaction Fees: Validators earn a portion of the transaction fees paid by users for the transactions they include in the blocks. This is intended to provide an additional financial incentive for validators to process transactions efficiently and maintain the network's integrity.
2. Delegators:
Delegated Staking: Token holders who do not wish to run a validator node can delegate their SOL tokens to a validator. In return, delegators share the rewards earned by the validators. This is intended to encourage widespread participation in securing the network and to support decentralisation.
3. Economic Security:
Solana staking documentation notes slashing as a possible future mechanism for intentional malicious conduct, but states that slashing is not implemented in the protocol today. Economic alignment instead currently arises primarily from staking participation, validator performance incentives, and the opportunity cost of locking capital in staking positions.
Fees Applicable on the Solana Blockchain
1. Transaction Fees:
Solana transactions require fees in SOL. The fee model consists of a base fee and, where used, an optional prioritisation fee. The base fee compensates signature verification work and is split between burn and validator compensation, while any prioritisation fee is paid to the validator.
2. Rent Fees:
Solana accounts that store on-chain state must satisfy the rent-exemption threshold, which is linked to the amount of data stored. This mechanism is intended to support efficient use of network state and account storage resources.
3. Program Execution Costs:
Deploying and interacting with on-chain programs may involve transaction fees and, where relevant, compute-related prioritisation fees and account-storage requirements. These mechanisms are intended to allocate network resources in proportion to use.
H.6 Use of distributed ledger technology
H.7 DLT functionality description
Not applicable, as the DLT is not operated by the issuer, the offeror, the person seeking admission to trading, or any third party acting on their behalf.
H.8 Audit
H.9 Audit outcome
Part I – Information on risks
I.1 Offer-related risks
1. Regulatory and Compliance
Regulatory frameworks applicable to crypto-asset services in the European Union and in third countries are evolving. Supervisory authorities may introduce, interpret, or enforce rules that affect (i) the eligibility of this crypto-asset for admission to trading, (ii) the conditions under which a crypto-asset service provider may offer trading, custody, or transfer services for it, or (iii) the persons or jurisdictions to which such services may be provided. As a result, the crypto-asset service provider admitting this crypto-asset to trading may be required to suspend, restrict, or terminate trading or withdrawals for regulatory reasons, even if the crypto-asset itself continues to function on its underlying network.
2. Trading venue and connection risk
Trading in the crypto-asset depends on the uninterrupted operation of the trading venues on which it is listed and, where applicable, on its technical connections to external liquidity sources or venues. Interruptions such as system downtime, maintenance, faulty integrations, API changes, or failures at an external venue can temporarily prevent order placement, execution, deposits, or withdrawals, even when the underlying blockchain is functioning. In addition, trading platforms in emerging markets may operate under differing governance, compliance, and oversight standards, which can increase the risk of operational failures or disorderly market conditions.
3. Market formation and liquidity conditions
The price and tradability of the crypto-asset depend on actual trading activity on the venues to which the service provider is connected, whether centralised exchanges (CEXs) or decentralised exchanges (DEXs). Trading volumes may at times be low, order books thin, or liquidity concentrated on a single venue. In such conditions, buy or sell orders may not be executed in full or may be executed only at a less favourable price, resulting in slippage.
Volatility: The market price of the crypto-asset may fluctuate significantly over short periods, including for reasons that are not linked to changes in the underlying project or protocol. Periods of limited liquidity, shifts in overall market sentiment, or trading on only a small number of CEXs or DEXs can amplify these movements and lead to higher slippage when orders are executed. As a result, investors may be unable to sell the crypto-asset at or close to a previously observed price, even where no negative project-specific event has occurred.
4. Counterparty and service provider dependence
The admission of the crypto-asset to trading may rely on several external parties, such as connected centralised or decentralised trading venues, liquidity providers, brokers, custodians, or technical integrators. If any of these counterparties fail to perform, suspend their services, or apply internal restrictions, the trading, deposit, or withdrawal of the crypto-asset on the listing crypto-asset service provider can be interrupted or halted.
Quality of counterparties: Trading venues and service providers in certain jurisdictions may operate under regulatory or supervisory standards that are lower or differently enforced than those applicable in the European Union. In such environments, deficiencies in governance, risk management, or compliance may remain undetected, which increases the probability of abrupt service interruptions, investigations, or forced wind-downs.
Delisting and service suspension: The crypto-asset’s availability may depend on the internal listing decisions of these counterparties. A delisting or suspension on a key connected venue can materially reduce liquidity or make trading temporarily impossible on the admitting service provider, even if the underlying crypto-asset continues to function.
Insolvency of counterparties: If a counterparty involved in holding, routing, or settling the crypto-asset becomes insolvent, enters restructuring, or is otherwise subject to resolution measures, assets held or processed by that counterparty may be frozen, become temporarily unavailable, or be recoverable only in part or not at all, which can result in losses for clients whose positions were maintained through that counterparty. This risk applies in particular where client assets are held on an omnibus basis or where segregation is not fully recognised in the counterparty’s jurisdiction.
5. Operational and information risks
Due to the irrevocability of blockchain transactions, incorrect transaction approvals or the use of wrong networks or addresses will typically make the transferred funds irrecoverable. Because trading may also rely on technical connections to other venues or service providers, downtime or faulty code in these connections can temporarily block trading, deposits, or withdrawals even when the underlying blockchain is functioning. In addition, different groups of market participants may have unequal access to technical, governance, or project-related information, which can lead to information asymmetry and place less informed investors at a disadvantage when making trading decisions.
6. Market access and liquidity concentration risk
If the crypto-asset is only available on a limited number of trading platforms or through a single market-making entity, this may result in reduced liquidity, greater price volatility, or periods of inaccessibility for retail holders.
I.2 Issuer-related risks
1. Insolvency of the issuer
As with any commercial entity, the issuer may face insolvency risks. These may result from insufficient funding, low market interest, mismanagement, or external shocks (e.g. pandemics, armed conflicts). In such a case, ongoing development, support, and governance of the project may cease, potentially affecting the viability and tradability of the crypto-asset.
2. Legal and regulatory risks
The issuer operates in a dynamic and evolving regulatory environment. Failure to comply with applicable laws or regulations in relevant jurisdictions may result in enforcement actions, penalties, or restrictions on the project’s operations. These may negatively impact the crypto-asset’s availability, market acceptance, or legal status.
3. Operational risks
The issuer may fail to implement adequate internal controls, risk management, or governance processes. This can result in operational disruptions, financial losses, delays in updating the white paper, or reputational damage.
4. Governance and decision-making
The issuer’s management body is responsible for key strategic, operational, and disclosure decisions. Ineffective governance, delays in decision-making, or lack of resources may compromise the stability of the project and its compliance with MiCA requirements. High concentration of decision-making authority or changes in ownership/control can amplify these risks.
5. Reputational risks
The issuer’s reputation may be harmed by internal failures, external accusations, or association with illicit activity. Negative publicity can reduce trust in the issuer and impact the perceived legitimacy or value of the crypto-asset.
6. Counterparty dependence
The issuer may depend on third-party providers for certain core functions, such as technology development, marketing, legal advice, or infrastructure. If these partners discontinue their services, change ownership, or underperform, the issuer’s ability to operate the project or maintain investor communication may be impaired. This could disrupt project continuity or undermine market confidence, ultimately affecting the crypto-asset’s value.
I.3 Crypto-assets-related risks
1. Valuation risk
The crypto-asset does not represent a claim, nor is it backed by physical assets or legal entitlements. Its market value is driven solely by supply and demand dynamics and may fluctuate significantly. In the absence of fundamental value anchors, such assets can lose their entire market value within a very short time. Historical market behaviour has shown that some types of crypto-assets have become worthless. Investors should be aware that this crypto-asset may lose all of its value.
2. Market volatility risk
Crypto-asset prices can fluctuate sharply due to changes in market sentiment, macroeconomic conditions, regulatory developments, or technology trends. Such volatility may result in rapid and significant losses. Holders should be prepared for the possibility of losing the full amount invested.
3. Liquidity and price-determination risk
Low trading volumes, fragmented trading across venues, or the absence of active market makers can restrict the ability to buy or sell the crypto-asset. In such situations, it is not guaranteed that an observable market price will exist at all times. Spreads may widen materially, and orders may only be executable under unfavourable conditions, which can make liquidation costly or temporarily impossible.
4. Crypto-asset security risk
Loss or theft of private keys, unauthorised access to wallets, or failures of custodial or exchange service providers can result in the irreversible loss of assets. Because blockchain transactions are final, recovery of funds after a compromise is generally impossible.
5. Fraud and scam risk
The pseudonymous and irreversible nature of blockchain transactions can attract fraudulent schemes. Typical forms include fake or unauthorised crypto-assets imitating established ones, phishing attempts, deceptive airdrops, or social-engineering attacks. Investors should exercise caution and verify the authenticity of counterparties and information sources.
6. Legal and regulatory reclassification risk
Legislative or regulatory changes in the European Union or in the Member State where the crypto-asset is admitted to trading may alter its legal classification, permitted uses, or tradability. In third countries, the crypto-asset may be treated as a financial instrument or security, which can restrict its offering, trading, or custody.
7. Absence of investor protection
The crypto-asset is not covered by investor-compensation or deposit-guarantee schemes. In the event of loss, fraud, or insolvency of a service provider, holders may have no access to recourse mechanisms typically available in regulated financial markets.
8. Counterparty risk
Reliance on third-party exchanges, custodians, or intermediaries exposes holders to operational failures, insolvency, or fraud of these parties. Investors should conduct due diligence on service providers, as their failure may lead to the partial or total loss of held assets.
9. Reputational risk
Negative publicity related to security incidents, misuse of blockchain technology, or associations with illicit activity can damage public confidence and reduce the crypto-asset’s market value.
10. Community and sentiment risk
Because the crypto-asset’s perceived relevance and expected future use depend largely on community engagement and the prevailing sentiment, a loss of public interest, negative coverage or reduced activity of key contributors can materially reduce market demand.
11. Macroeconomic and interest-rate risk
Fluctuations in interest rates, exchange rates, general market conditions, or overall market volatility can influence investor sentiment towards digital assets and affect the crypto-asset’s market value.
12. Taxation risk
Tax treatment varies across jurisdictions. Holders are individually responsible for complying with all applicable tax laws, including the reporting and payment of taxes arising from the acquisition, holding, or disposal of the crypto-asset.
13. Anti-money-laundering and counter-terrorist financing risk
Wallet addresses or transactions connected to the crypto-asset may be linked to sanctioned or illicit activity. Regulatory responses to such findings may include transfer restrictions, reporting obligations, or the freezing of assets on certain venues.
14. Market-abuse risk
Due to limited oversight and transparency, crypto-assets may be vulnerable to market-abuse practices such as spoofing, pump-and-dump schemes, or insider trading. Such activities can distort prices and expose holders to sudden losses.
15. Legal ownership and jurisdictional risk
Depending on the applicable law, holders of the crypto-asset may not have enforceable ownership rights or effective legal remedies in cases of disputes, fraud, or service failure. In certain jurisdictions, access to exchanges or interfaces may be restricted by regulatory measures, even if on-chain transfer remains technically possible.
16. Concentration risk
A large proportion of the total supply may be held by a small number of holders. This can enable market manipulation, governance dominance, or sudden large-scale liquidations that adversely affect market stability, price levels, and investor confidence.
I.4 Project implementation-related risks
As this white paper relates to admission to trading of the crypto-asset, the risk description below reflects general implementation risks typically associated with crypto-asset projects and relevant for the crypto-asset service provider. The party admitting the crypto-asset to trading is not involved in the project’s implementation and does not assume responsibility for its governance, funding, or execution.
Delays, failures, or changes in the implementation of the project as outlined in its public roadmap or technical documentation may negatively impact the perceived credibility or usability of the crypto-asset. This includes risks related to project governance, resource allocation, technical delivery, and team continuity.
Key-person risk: The project may rely on a limited number of individuals for development, maintenance, or strategic direction. The departure, incapacity, or misalignment of these individuals may delay or derail the implementation.
Timeline and milestone risk: Project milestones may not be met as announced. Delays in feature releases, protocol upgrades, or external integrations can undermine market confidence and affect the adoption, use, or value of the crypto-asset.
Delivery risk: Even if implemented on time, certain functionalities or integrations may not perform as intended or may be scaled back during execution, limiting the crypto-asset’s practical utility.
I.5 Technology-related risks
As this white paper relates to admission to trading of the crypto-asset, the following risks concern the underlying distributed ledger technology (DLT), its supporting infrastructure, and related technical dependencies. Failures or vulnerabilities in these systems may affect the availability, integrity, or transferability of the crypto-asset.
1. Blockchain dependency risk
The functionality of the crypto-asset depends on the continuous and stable operation of the blockchain(s) on which it is issued. Network congestion, outages, or protocol errors may temporarily or permanently disrupt on-chain transactions. Extended downtime or degradation in network performance can affect trading, settlement, or the usability of the crypto-asset.
2. Smart contract vulnerability risk
The smart contract that defines the crypto-asset’s parameters or governs its transfers may contain coding errors or security vulnerabilities. Exploitation of such weaknesses can result in unintended token minting, permanent loss of funds, or disruption of token functionality. Even after external audits, undetected vulnerabilities may persist due to the immutable nature of deployed code.
3. Wallet and key-management risk
The custody of crypto-assets relies on secure private key management. Loss, theft, or compromise of private keys results in irreversible loss of access. Custodians, trading venues, or wallet providers may be targeted by cyberattacks. Compatibility issues between wallet software and changes to the blockchain protocol (e.g. network upgrades) can further limit user access or the ability to transfer the crypto-asset.
Outdated or vulnerable wallet software:
Users relying on outdated, unaudited, or unsupported wallet software may face compatibility issues, security vulnerabilities, or failures when interacting with the blockchain. Failure to update wallet software in line with protocol developments can result in transaction errors, loss of access, or exposure to known exploits.
4. Network security risks
Attack risks: Blockchains may be subject to denial-of-service (DoS) attacks, 51% attacks, or other exploits targeting the consensus mechanism. These can delay transactions, compromise finality, or disrupt the accurate recording of transfers.
Centralisation concerns: Despite claims of decentralisation, a relatively small number of validators or a high concentration of stake may increase the risk of collusion, censorship, or coordinated network downtime, which can affect the resilience and operational reliability of the crypto-asset.
5. Bridge and interoperability risk
Where tokens can be bridged or wrapped across multiple blockchains, vulnerabilities in bridge protocols, validator sets, or locking mechanisms may result in loss, duplication, or misrepresentation of assets. Exploits or technical failures in these systems can instantly impact circulating supply, ownership claims, or token fungibility across chains.
6. Forking and protocol-upgrade risk
Network upgrades or disagreements among node operators or validators can result in blockchain “forks”, where the blockchain splits into two or more incompatible versions that continue separately from a shared past. This may lead to duplicate token representations or incompatibilities between exchanges and wallets. Until consensus stabilises, trading or transfers may be disrupted or misaligned. Such situations may be difficult for retail holders to navigate, particularly when trading platforms or wallets display inconsistent token information.
7. Economic-layer and abstraction risk
Mechanisms such as gas relayers, wrapped tokens, or synthetic representations may alter the transaction economics of the underlying token. Changes in transaction costs, token demand, or utility may reduce its usage and weaken both its economic function and perceived value within its ecosystem.
8. Spam and network-efficiency risk
High volumes of low-value (“dust”) or automated transactions may congest the network, slow validation times, inflate ledger size, and raise transaction costs. This can impair performance, reduce throughput, and expose address patterns to analysis, thereby reducing network efficiency and privacy.
9. Front-end and access-interface risk
If users rely on centralised web interfaces or hosted wallets to interact with the blockchain, service outages, malicious compromises, or domain expiries affecting these interfaces may block access to the crypto-asset, even while the blockchain itself remains fully functional. Dependence on single web portals introduces a critical point of failure outside the DLT layer.
10. Decentralisation claim risk
While the technical infrastructure may appear distributed, the actual governance or economic control of the project may lie with a small set of actors. This disconnect between marketing claims and structural reality can lead to regulatory scrutiny, reputational damage, or legal uncertainty – especially if the project is presented as ‘community-governed’ without substantiation.
I.6 Mitigation measures
None.
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
S.1 Name
S.2 Relevant legal entity identifier
S.3 Name of the crypto-asset
S.4 Consensus Mechanism
The crypto-asset that is the subject of this white paper is available on the Solana network.
The following applies to Solana:
Solana uses a combination of Proof-of-History (PoH) and Proof-of-Stake (PoS). The core concepts of the mechanism are intended to work as follows:
Core Concepts
1. Proof-of-History (PoH):
PoH is a cryptographic ordering and timing mechanism that provides evidence that data existed in a particular sequence and that time passed between proofs.
Verifiable Delay Function (VDF): PoH relies on a sequential hash-based proof process that Solana describes as VDF-like. This sequence of hashes provides a verifiable order of events, enabling the network to efficiently agree on the sequence of transactions.
2. Proof-of-Stake (PoS):
Validator Selection: Leader slots are assigned through the network’s leader schedule, which is stake-weighted. The more SOL staked, the higher the chance of being selected to validate transactions and produce new blocks.
Delegation: Token holders can delegate their SOL tokens to validators, earning rewards proportional to their stake while contributing to the network's security.
Consensus Process
1. Transaction Validation:
Transactions are broadcasted to the network and collected by validators. Each transaction is validated to ensure it meets the network’s criteria, such as having correct signatures and sufficient funds.
2. PoH Sequence Generation:
A validator generates a sequence of hashes using PoH, each containing a timestamp and the previous hash. This process creates a historical record of transactions, establishing a cryptographic clock for the network.
3. Block Production:
The network uses PoS to select a leader validator based on their stake. The leader is responsible for bundling the validated transactions into a block. The leader validator uses the PoH sequence to order transactions within the block, ensuring that all transactions are processed in the correct order.
4. Consensus and Finalisation:
Other validators vote on the ledger state associated with the block. A block may first become confirmed and later finalised once it reaches the network’s strongest confirmation state.
Security and Economic Incentives
1. Incentives for Validators:
Block Rewards: Validators earn rewards for producing and validating blocks. These rewards are distributed in SOL tokens and are proportional to the validator’s stake and performance.
Transaction Fees: Validators also earn transaction fees from the transactions included in the blocks they produce. These fees provide an additional incentive for validators to process transactions efficiently.
2. Security:
Staking: Staking provides economic alignment, and Solana documentation notes that slashing has been discussed as a future mechanism for intentional malicious behaviour, but is not implemented yet.
Delegated Staking: Token holders can delegate their SOL tokens to validators, intended to enhance network security and decentralisation. Delegators share in the rewards and are incentivised to choose reliable validators.
3. Economic Penalties:
Slashing (planned): Validators can be penalised for malicious behaviour, such as double-signing or producing invalid blocks. This penalty, known as slashing, results in the loss of a portion of the staked tokens, discouraging dishonest actions.
S.5 Incentive Mechanisms and Applicable Fees
The crypto-asset that is the subject of this white paper is available on the Solana network.
The following applies to Solana:
1. Validators:
Validators participate in block production and voting under Solana’s stake-weighted model. They may receive staking-related rewards and a share of transaction-fee income. Under Solana’s fee model, the base fee is split between burn and validator compensation, while any prioritisation fee is paid to the validator.
Transaction Fees: Validators earn a portion of the transaction fees paid by users for the transactions they include in the blocks. This is intended to provide an additional financial incentive for validators to process transactions efficiently and maintain the network's integrity.
2. Delegators:
Delegated Staking: Token holders who do not wish to run a validator node can delegate their SOL tokens to a validator. In return, delegators share the rewards earned by the validators. This is intended to encourage widespread participation in securing the network and to support decentralisation.
3. Economic Security:
Solana staking documentation notes slashing as a possible future mechanism for intentional malicious conduct, but states that slashing is not implemented in the protocol today. Economic alignment instead currently arises primarily from staking participation, validator performance incentives, and the opportunity cost of locking capital in staking positions.
Fees Applicable on the Solana Blockchain
1. Transaction Fees:
Solana transactions require fees in SOL. The fee model consists of a base fee and, where used, an optional prioritisation fee. The base fee compensates signature verification work and is split between burn and validator compensation, while any prioritisation fee is paid to the validator.
2. Rent Fees:
Solana accounts that store on-chain state must satisfy the rent-exemption threshold, which is linked to the amount of data stored. This mechanism is intended to support efficient use of network state and account storage resources.
3. Program Execution Costs:
Deploying and interacting with on-chain programs may involve transaction fees and, where relevant, compute-related prioritisation fees and account-storage requirements. These mechanisms are intended to allocate network resources in proportion to use.
S.6 Beginning of the period to which the disclosure relates
S.7 End of the period to which the disclosure relates
S.8 Energy consumption
S.9 Energy consumption sources and methodologies
The energy consumption associated with this crypto-asset is aggregated from multiple contributing components, primarily the underlying blockchain network and the execution of token-specific operations. To determine the energy consumption of a token, the energy consumption the Solana network is calculated first. A proportionate share of that energy use is then attributed to the token based on its activity level within the network (e.g. transaction volume, contract execution).
The Functionally Fungible Group Digital Token Identifier (FFG DTI) is used to determine all technically equivalent implementations of the crypto-asset in scope.
Estimates regarding hardware types, node distribution, and the number of network participants are based on informed assumptions, supported by best-effort verification against available empirical data. Unless robust evidence suggests otherwise, participants are assumed to act in an economically rational manner. In line with the precautionary principle, conservative estimates are applied where uncertainty exists – that is, estimates tend towards the higher end of potential environmental impact.
S.10 Renewable energy consumption
S.11 Energy intensity
S.12 Scope 1 DLT GHG emissions – Controlled
S.13 Scope 2 DLT GHG emissions – Purchased
S.14 GHG intensity
S.15 Key energy sources and methodologies
To determine the proportion of renewable energy usage, the locations of the nodes are determined using public information sites, open-source and in-house-developed crawlers. Where no information is available on the geographic distribution of nodes, comparable reference networks are used, taking into account similarities in incentivisation structure and consensus mechanism. This geographic information is then combined with publicly available data from Our World in Data. The resulting intensity is calculated as the marginal energy consumption with respect to one additional transaction.
Ember (2025); Energy Institute, Statistical Review of World Energy (2024), with major processing by Our World in Data. “Share of electricity generated by renewables - Ember and Energy Institute” [dataset]. Underlying sources: Ember, “Yearly Electricity Data Europe”; Ember, “Yearly Electricity Data”; Energy Institute, “Statistical Review of World Energy”. Retrieved from: https://ourworldindata.org/grapher/share-electricity-renewables
S.16 Key GHG sources and methodologies
To determine GHG emissions, the locations of the nodes are determined using public information sites, open-source crawlers, and crawlers developed in-house. Where no information is available on the geographic distribution of nodes, comparable reference networks are used, taking into account similarities in incentivisation structure and consensus mechanism. This geographic information is then combined with publicly available data from Our World in Data. The resulting intensity is calculated as the marginal emission intensity with respect to one additional transaction.
Ember (2025); Energy Institute, Statistical Review of World Energy (2024), with major processing by Our World in Data. “Carbon intensity of electricity generation – Ember and Energy Institute” [dataset]. Underlying sources: Ember, “Yearly Electricity Data Europe”; Ember, “Yearly Electricity Data”; Energy Institute, “Statistical Review of World Energy”. Retrieved from: https://ourworldindata.org/grapher/carbon-intensity-electricity. Licensed under CC BY 4.0.