| N | Field | Content |
|---|---|---|
| 00 | Table of contents |
Part A: Information about the offeror or the person seeking admission to trading Part B: Information about the issuer, if different from the offeror or person seeking admission to trading Part C: Information about the operator of the trading platform in cases where it draws up the crypto-asset white paper and information about other persons drawing the crypto-asset white paper pursuant to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 Part D: Information about the crypto-asset project Part E: Information about the offer to the public of crypto-assets or their admission to trading Part F: Information about the crypto-assets Part G: Information on the rights and obligations attached to the crypto-assets Part H: Information on the underlying technology Part I: Information on the risks Part J: Information on the sustainability indicators in relation to adverse impact on the climate and other environment-related adverse impacts |
| 01 | Date of notification |
|
| 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 |
|
| 07 | Warning in accordance with Article 6(7), second subparagraph, of Regulation (EU) 2023/1114 |
This summary should be read as an introduction to the crypto-asset white paper. The prospective holder should base any decision to purchase this crypto-asset on the content of the crypto-asset white paper as a whole and not on the summary alone. The offer to the public of this crypto-asset does not constitute an offer or solicitation to purchase financial instruments and any such offer or solicitation can be made only by means of a prospectus or other documents pursuant to the applicable national law. This crypto-asset white paper does not constitute a prospectus as referred to in Regulation (EU) 2017/1129 of the European Parliament and of the Council or any other offer document pursuant to Union or national law. |
| 08 | Characteristics of the crypto-asset |
|
| 09 | Further information about utility tokens |
|
| 10 | Key information about the offer to the public or admission to trading |
|
| N | Field | Content | ||||||
|---|---|---|---|---|---|---|---|---|
| A.1 | Name |
|
||||||
| A.2 | Legal form |
|
||||||
| A.3 | Registered address |
|
||||||
| A.3 | Country | |||||||
| A.3 | Sub-division |
|
||||||
| A.4 | Head office |
|
||||||
| A.4 | Country | |||||||
| A.4 | Sub-division |
|
||||||
| 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 |
Yellow Network's strategy is to provide a complete Web3 toolkit that unifies liquidity, simplifies dApp development, and improves the user experience. The base technology is a three-layer architecture: EVM smart contracts provide on-chain custody and dispute enforcement (Layer 1); the Yellow Clearnet, a distributed peer-to-peer ledger, enables off-chain clearing and settlement across multiple blockchains using threshold cryptographic signatures (Layer 2); and the Application Layer supports dApps, the App Store, and developer tools (Layer 3). This architecture creates a global, unified pool of liquidity while enabling transactions at scale. Built on top of this is the Yellow SDK, which provides developers with the tools to build dApps with the speed and user experience of traditional Web2 platforms. Yellow Network aims to accelerate the adoption of Web3 by providing the infrastructure for a more efficient and accessible financial ecosystem. Products/services YELLOW ECOSYSTEM Yellow Network is a comprehensive Web3 ecosystem providing the core infrastructure and developer tools to power a new generation of high-performance decentralised finance applications. YELLOW NETWORK The Layer-3 protocol described above underpins all network operations, providing the clearing and settlement infrastructure for the ecosystem. YELLOW.COM Yellow.com is a separate entity from Layer3 Fintech Ltd., with no shared management. It currently serves as a media outlet. YELLOW SDK Yellow SDK is a comprehensive Software Development Kit that serves as the primary toolkit for developers to build advanced, user-friendly, and efficient dApps on the Yellow Network. YELLOW TOKEN YELLOW is the native utility token that provides access to the goods and services supplied by Layer3 Fintech Ltd. within the Yellow Network, enabling users to access network services, build decentralised applications, and post collateral as a mandatory security deposit for node operation. NEODAX NeoDAX is an open-source crypto brokerage solution that provides turnkey liquidity and can handle hundreds of thousands of transactions per second. Markets served The primary market for Yellow Network is professional traders and brokers. The Yellow ecosystem appeals to a wider audience aiming to address common issues in traditional and Web3 finance and to provide new experiences spanning finance and entertainment. |
||||||
| 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 |
|
| N | Field | Content |
|---|---|---|
| B.1 | Issuer different from offerror or person seeking admission to trading |
|
| B.2 | Name | N/A |
| B.3 | Legal form | N/A |
| B.4 | Registered address | N/A |
| B.5 | Head office | N/A |
| B.6 | Registration date | N/A |
| B.7 | Legal entity identifier | N/A |
| B.8 | Another identifier required pursuant to applicable national law | N/A |
| B.9 | Parent company | N/A |
| B.10 | Members of the management body | N/A |
| B.11 | Business activity | N/A |
| B.12 | Parent company business activity | N/A |
| N | Field | Content |
|---|---|---|
| C.1 | Name | N/A |
| C.2 | Legal form | N/A |
| C.3 | Registered address | N/A |
| C.4 | Head office | N/A |
| C.5 | Registration date | N/A |
| C.6 | Legal entity identifier | N/A |
| C.7 | Another identifier required pursuant to applicable national law | N/A |
| C.8 | Parent company | N/A |
| C.9 | Reason for crypto-asset white paper Preparation | N/A |
| C.10 | Members of the management body | N/A |
| C.11 | Operator business activity | N/A |
| C.12 | Parent company business activity | N/A |
| C.13 | Other persons drawing up the crypto-asset white paper according to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | N/A |
| C.14 | Reason for drawing the white paper by persons referred to in Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | N/A |
| N | Field | Content | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| D.1 | Crypto-asset project name |
|
||||||||||||||||||||
| D.2 | Crypto-asset name |
|
||||||||||||||||||||
| D.3 | Abbreviation |
|
||||||||||||||||||||
| D.4 | Crypto-asset project description |
|
||||||||||||||||||||
| D.5 | Details of all natural or legal persons involved in implementation of crypto-asset project |
Yellow is an open-source software framework developed through multi-entity collaboration across several independent organisations and jurisdictions. The core state channel technology builds on academic research from statechannels.org and the Nitrolite framework, developed in collaboration with Consensys and other open-source contributors. Principal development entities include Clearsync Ltd. (UK) and other independent contributors across multiple jurisdictions, with approximately 60 core developers contributing across the open-source codebase. The project’s ecosystem extends further through participation in Ethereum Foundation and ETHGlobal hackathons, with over 500 independent developer-built projects now building on the protocol using its open-source SDK — spanning developer tooling, analytics dashboards, decentralised finance integrations, and trading applications.
Layer3 Fintech Ltd. integrates, maintains, and supplies the resulting goods and services — including the protocol software, SDK, developer tools, AppRegistry, smart account infrastructure, and associated platform services — that constitute the goods and services accessible through YELLOW. Node operators use the issuer’s open-source clearnode software to deliver network services on their own hardware — analogous to service providers running SaaS software supplied by a licensor. Layer3 Fintech Ltd. retains responsibility for the ongoing integration, maintenance, and availability of the protocol, SDK, and application-layer tools that YELLOW provides access to.
|
||||||||||||||||||||
| D.6 | Utility Token Classification |
|
||||||||||||||||||||
| D.7 | Key Features of Goods/Services for Utility Token Projects |
|
||||||||||||||||||||
| D.8 | Description of past milestones |
The Yellow Network's decentralised infrastructure has been developed through open-source collaboration across multiple independent entities (see section D.5), delivering client applications, decentralised protocols, and smart contracts that power the technology framework used by businesses and developers building applications on the network. Layer3 Fintech Ltd. coordinates the integration and supply of the resulting goods and services. 2024: - State Channel and Account Abstraction R and D - Launch of the Yellow Smart Account - Launch of the Yellow Wallet - Establishment of the Clearing Network Legal Framework - Launch of the Yellow.com User Portal - Finalisation of the Core Protocol Architecture. 2025: - Production Release of the Yellow SDK - Network Expansion to 6 New EVM Chains - Official Launch of the Yellow Builder Program - Launch of 100+ Third-Party Applications on the Yellow Network Outlook. |
||||||||||||||||||||
| D.8 | Description of future milestones |
2026: - Public Release of the NeoDAX Brokerage Software — Q2 2026 - Finalisation of the Clearing Network Architecture - Public Release of the Yellow Clearing Network — Q3 2026 - Initiation of non-EVM Chain Support (Closed Beta) — Q4 2026. The following goods and services are fully operational at the time of this white paper: State Channels, Smart Account Abstraction, Yellow Wallet, Yellow.com Portal, Core Protocol, Yellow SDK v1.0, Yellow Builder Program, Yellow App Store, Yellow App Registry, and Yellow Node Registry. The Application Layer (AppLayer) and the Ledger Layer (DLT Clearnet) are accessible to node operators on testnet and are expected to reach mainnet within six months of filing. Future milestones include integrations with other major blockchain networks and transition of protocol parameter administration from a centralised key to distributed multi-signature execution by active node operators. |
||||||||||||||||||||
| D.9 | Resource allocation |
Financial Resources — The company has attracted private round seed funding in prior years and recently completed a public placement for $1M. These resources are primarily allocated to operational expenses and team salaries related to Yellow's development. Human Resources — Yellow has a dedicated core team of 33 full-time staff within Layer3 Fintech Ltd., supplemented by approximately 60 core developers contributing across the open-source codebase through independent entities including Clearsync Ltd. (UK) and other contributors across multiple jurisdictions, as well as a network of advisors. The advisors include Chris Larsen, co-founder of Ripple Labs, providing strategic guidance. Technical Resources — The project builds on open-source state channel research from statechannels.org and the Nitrolite framework developed in collaboration with Consensys and other contributors. Core developers across the contributing entities maintain and extend the open-source codebase, with Layer3 Fintech Ltd. integrating contributions into the supplied goods and services. Operational Partnerships — Exchange partnerships with Kraken, Coinbase, Bithumb, and yellow.pro have been initiated to support token launch and liquidity provision. The YELLOW token was listed on 8 March 2026 on a non-EU regulated exchange. Admission to additional exchanges is subject to final listing agreements. |
||||||||||||||||||||
| D.10 | Planned use of Collected funds or crypto-Assets |
|
| N | Field | Content |
|---|---|---|
| E.1 | Public offering or admission to trading | |
| E.2 | Reasons for public offer or admission to trading |
Admission to Trading for Ecosystem Accessibility Admission to trading ensures that YELLOW tokens remain accessible to network participants — including node operators, developers, brokers, and service providers — who require the token to access goods and services supplied by Layer3 Fintech Ltd. The YELLOW token was admitted to secondary market trading on 8 March 2026 on a non-EU regulated exchange, with additional EU-regulated trading platforms being pursued. Prior Token Distribution The public offer distributed YELLOW tokens to participants who need them to operate nodes, access developer tools, register applications, and use network services. Proceeds from the distribution supported the continued development and delivery of Yellow ecosystem services. |
| E.3 | Target expressed in currency | N/A — Primary sales are closed. The most recent public sale was completed on 25 August 2025. |
| E.3 | Target expressed in units | N/A |
| E.3 | Target expressed in digital token identifier | N/A |
| E.4 | Minimum subscription goals | N/A |
| E.5 | Maximum subscription goals | N/A |
| E.6 | Oversubscription acceptance |
|
| E.7 | Oversubscription allocation | N/A |
| E.8 | Issue price |
|
| E.9 | Official currency or any other crypto-assets determining the issue price | |
| E.9 | Official currency or any other crypto-assets determining the issue price |
|
| E.10 | Fee expressed in currency | N/A |
| E.10 | Fee expressed in units | N/A |
| E.10 | Fee expressed in digital token identifier | N/A |
| 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 |
Right of Withdrawal — in accordance with Article 13 of Regulation (EU) 2023/1114, all purchasers had the right to withdraw from their purchase within 14 calendar days of the subscription date. Purchasers exercising this right were reimbursed in the same currency or crypto-asset used for payment, less any transaction costs charged by third-party payment providers. Cancellation of the Offer — if the public offer had been cancelled prior to completion, all purchasers would have been reimbursed in full in the same currency or crypto-asset used for payment. Reimbursement requests were processed by Layer3 Fintech Ltd. or the third-party platforms facilitating the offer. As the offer is now closed and the token has been admitted to trading, these refund mechanisms are no longer applicable. |
| 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 |
Segregated Holding of Assets — All fiat funds and crypto-assets received during the token offer were held in dedicated accounts or wallets separate from Layer3 Fintech Ltd.'s operational funds. Third-Party Custody — Launchpads and exchanges facilitating the public offer held purchaser funds or crypto-assets in accordance with their regulated safeguarding arrangements until the allocation of YELLOW tokens was confirmed. Reimbursement Mechanism — Purchasers who exercised their 14-day right of withdrawal under Article 13 MiCA had their funds or crypto-assets returned in the same form in which they were received (subject only to network or payment provider transaction costs). Security and Oversight — Layer3 Fintech Ltd. monitored and verified that all safeguarding arrangements were maintained in compliance with EU standards throughout the offer period. |
| E.24 | Payment methods for crypto-asset purchase |
Fiat Payments — payments in official currencies (such as EUR or USD) were accepted through regulated third-party payment providers through launchpads and exchanges participating in the offer. Crypto-Asset Payments — Crypto-assets such as USDT, USDC and ETH were used to acquire YELLOW tokens. These transactions were processed via licensed third-party crypto-asset service providers (CASPs) acting as on-ramps/off-ramps, with conversion carried out at prevailing market rates at the time of purchase. Layer3 Fintech Ltd. did not directly hold or custody purchaser funds. All public offer payments were facilitated through external regulated partners to ensure compliance with applicable financial and anti-money laundering requirements. The public offer is now closed; YELLOW is available on secondary markets. |
| 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 | N/A |
| 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 |
The full token allocation is as follows. Each allocation is functional and tied to the delivery or consumption of Yellow ecosystem services — no allocation is designed to generate financial returns for its recipient:
|
| E.39 | Applicable law |
|
| E.40 | Competent court |
|
| N | Field | Content |
|---|---|---|
| F.1 | Crypto-asset type |
YELLOW is not an electronic money token (Art. 3(1)(7)). YELLOW does not purport to maintain a stable value by referencing the value of any single official currency. Its market price is determined solely by supply and demand and is not pegged, algorithmically stabilised, or backed by reserves denominated in an official currency. YELLOW is not an asset-referenced token (Art. 3(1)(6)). YELLOW does not purport to maintain a stable value by referencing another value or right or a combination thereof, including one or more official currencies. There is no reserve of assets backing YELLOW, no stabilisation mechanism, and no redemption right at par or at a reference value. YELLOW is not a financial instrument (Art. 2(4)(a), Directive 2014/65/EU MiFID II). YELLOW does not confer rights equivalent to any category of financial instrument: - Not a transferable security: YELLOW does not represent ownership in or a debt obligation of the issuer. It confers no rights to dividends, profit-sharing, liquidation proceeds, or voting rights in corporate matters. Its characteristics are not comparable to shares, bonds, or depositary receipts. - Not a money market instrument: YELLOW is not a short-term debt instrument and does not bear interest or represent a claim payable at maturity. - Not a unit in a collective investment undertaking: YELLOW does not represent a pooled investment. Holders do not share in the profits or losses of a common enterprise. The mandatory collateral lock-up mechanism for node operators is a service prerequisite that increases slashing exposure, not an investment return. Protocol parameter governance is restricted to active node operators running infrastructure and is non-transferable, non-delegable, and terminates immediately when operations cease — it is an operational administration function, not a right attached to token ownership. - Not a derivative: YELLOW's value is not derived from an underlying asset, index, or reference rate. There is no settlement obligation, option, or future contract embedded in the token. The assessment takes into account the ESMA Guidelines on the conditions and criteria for the qualification of crypto-assets as financial instruments under Article 2(5) of Regulation (EU) 2023/1114. YELLOW is not a deposit (Art. 2(4)(b)). YELLOW is not repayable at par and does not represent funds received by a credit institution. There is no obligation on the issuer to return a nominal amount to the holder. YELLOW is not funds (Art. 2(4)(c)). YELLOW does not constitute funds within the meaning of Directive (EU) 2015/2366 (PSD2). It is not banknotes, coins, scriptural money, or electronic money. YELLOW is not a securitisation position, insurance product, pension product, or social security scheme (Art. 2(4)(d)-(j)). YELLOW does not fall within any of these excluded categories. |
| F.2 | Crypto-asset functionality |
Other functionalities are planned that focus on expanding the role of YELLOW within the Yellow ecosystem by requiring YELLOW as a mandatory functional security deposit across additional protocol components. As Yellow continues to scale, YELLOW will be increasingly utilised to secure a broader range of components and services supplied by Layer3 Fintech Ltd., including the Yellow Clearnet (Ledger Layer), NeoDAX, Yellow App Store, and the Application Layer and its extensions. YELLOW will also be required as the protocol expands the scope of goods and services supplied by Layer3 Fintech Ltd., requiring node operators to post YELLOW collateral to back additional service guarantees across a broader range of protocol operations — including Clearnet settlement validation and Application Layer extensions such as NeoDAX and other applications built on the Yellow Network. As the network matures, protocol parameter administration will transition from centralised administration to distributed multi-signature execution by active node operators, replacing a single-point-of-failure administrator key with collective operational oversight — a protocol security mechanism, not a right conferred by token ownership. |
| F.3 | Planned application of functionalities |
- State Channels — operational since 2024 - “Smart” Account Abstraction — operational since 2024 - Yellow Wallet — operational since 2024 - Yellow.com User Portal — operational since 2024 - Core Protocol — operational since 2024 - Yellow SDK v1.0 — production release 2025 - Yellow Builder Program — launched 2025 - Yellow App Store — operational - Yellow App Registry — operational - Yellow Node Registry — operational The following functionalities are accessible to node operators on testnet and are expected to reach mainnet within six months of filing: - Yellow Ledger Layer (DLT Clearnet) — in testnet since 2025 - Yellow Application Layer (AppLayer) — in testnet since 2025 The following functionalities are planned for delivery by December 2026, within the 12-month period commencing from the date of publication of the original crypto-asset white paper (February 2026), in accordance with Article 4(6) of Regulation (EU) 2023/1114: - Yellow Network Clearing Public Release — Q3 2026 - Yellow Network support of non-EVM blockchains — Q4 2026 - Public Release of NeoDAX Brokerage Open Source Software — Q2 2026 |
| F.4 | Type of crypto-asset white paper | |
| F.5 | The type of submission | |
| F.6 | Crypto-asset characteristics |
YELLOW is only intended to provide access to the goods and services supplied by Layer3 Fintech Ltd. within the Yellow Network — a clearing and settlement network of interconnected nodes operating across several blockchains. YELLOW is consumed when accessing protocol services and is required as a mandatory functional security deposit for node operation under the protocol's Value-at-Risk model (see section H.5 for the full collateral, fee, and slashing mechanism). The supply is fixed at 10 billion YELLOW, with neither inflationary nor deflationary mechanisms. YELLOW does not entitle holders to any governance privileges, dividends, or repayment obligations, and its acquisition does not involve any guaranteed financial return. Holding YELLOW alone does not grant participation in protocol parameter governance, which is restricted to active node operators running network infrastructure (see section H.5). YELLOW is not a financial instrument within the meaning of Directive 2014/65/EU (MiFID II), as it does not confer ownership rights, profit participation, or claims analogous to transferable securities, money market instruments, or derivatives. |
| 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, where available |
|
| F.14 | Functionally fungible group digital token identifier, where available |
|
| F.15 | Voluntary data flag |
|
| F.16 | Personal data flag |
|
| F.17 | LEI eligibility |
|
| F.18 | Home Member State | |
| F.19 | Host Member States |
| N | Field | Content |
|---|---|---|
| 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 | N/A |
| 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 |
|
| N | Field | Content |
|---|---|---|
| H.1 | Distributed ledger technology |
Layer 1 — Base blockchain (EVM settlement) YELLOW is implemented as an ERC-20 token on Ethereum, ensuring compatibility with existing wallets, smart contract systems, and decentralised applications. Smart contracts deployed on each supported EVM chain (Ethereum, Base, Arbitrum, Linea, BNB, and Polygon) provide on-chain asset custody, the NodeRegistry for node operator registration and collateral management, the AppRegistry for application registration, and collateral slashing enforcement. Layer 2 — Ledger Layer (Yellow Clearnet) A distributed peer-to-peer ledger that operates off-chain above the base blockchain. Independent node operators form a decentralised network where each user account is guarded by a group of nodes assigned by the protocol. These nodes collectively manage the account's state using threshold cryptographic signatures — no single node can unilaterally move funds; a supermajority of the group must agree before any balance change is recorded. The protocol scales security proportionally: as the value held in an account grows, it automatically assigns more nodes to guard it, ensuring the total collateral at risk always exceeds the value being protected. A separate set of nodes independently verifies every state change and can produce on-chain fraud proofs if the primary group acts dishonestly. The Ledger Layer provides Virtual State Channels — channels that are created and managed entirely off-chain without requiring an on-chain transaction to initialise — enabling off-chain balance management, cross-chain clearing and settlement, and unified multi-chain balances through clearnode infrastructure. Layer 3 — Application Layer (AppLayer) Applications built on top of the Ledger Layer. Application-level state updates are agreed off-chain by channel participants through quorum consensus. Misconduct is enforced through collateral slashing on the base blockchain. The Application Layer supports the Yellow App Store, SDK-built applications, and specialised services such as dispute adjudication through independent arbitration forums. This three-layer structure aligns with the MiCA definition of Distributed Ledger Technology (Regulation (EU) 2023/1114) — a system in which records are stored in a distributed manner, where validation and updating are performed by multiple parties using cryptographic and consensus-based mechanisms, without reliance on a central authority. The Yellow Network maps to this definition in the following ways:
|
| H.2 | Protocols and technical standards |
Layer 1 — On-chain standards
|
| H.3 | Technology used |
Layer 1 — EVM smart contracts — Custody contracts deployed on each supported chain (Ethereum, Base, Arbitrum, Linea, BNB, and Polygon) provide on-chain asset custody and settlement finality. The NodeRegistry manages node operator registration and collateral. The AppRegistry manages application registration and service quality deposits. Collateral slashing is enforced on-chain when fraud is detected by the Ledger Layer. Layer 2 — Clearnode infrastructure (Yellow Clearnet) — Clearnodes are decentralised nodes operated by independent node operators using the issuer's open-source software. Each clearnode participates in the distributed ledger by joining node groups that collectively guard user accounts, maintaining asset pools across multiple blockchain networks, providing chain abstraction, routing off-chain transactions through Virtual State Channels, and exposing unified cross-chain balances to connected clients. Layer 3 — Application Layer and developer tools — The Yellow SDK provides the AppLayer RPC API and AppLayerClient library, enabling developers to integrate applications with the Yellow Network without managing low-level Virtual State Channel operations, cryptographic signing, or multi-chain settlement directly. The Yellow Smart Account and Yellow Wallet provide end-user interfaces for interacting with the network, managing assets across chains, and accessing application-layer services. |
| H.4 | Consensus Mechanism |
Layer 1 — Ethereum Proof-of-Stake YELLOW is an ERC-20 token deployed on the Ethereum blockchain and therefore inherits Ethereum's Proof-of-Stake (PoS) consensus mechanism. Validators stake ETH to participate in block proposal and attestation, ensuring that attacks are economically irrational, transactions are finalised through consensus checkpoints, and every on-chain YELLOW transfer is validated by a globally decentralised set of nodes. The creation, ownership, and on-chain transfer of YELLOW are secured by Ethereum's PoS consensus. Layer 2 — Ledger Layer threshold-signature consensus Within the Ledger Layer, each user account is guarded by a group of nodes that reach consensus through threshold cryptographic signatures. A supermajority of the group must co-sign every state update before it is accepted — no single node, or even a minority of nodes, can unilaterally alter an account's balance. A separate set of nodes independently verifies every state change; if the primary group produces a fraudulent update, the verifiers generate an on-chain dispute certificate that overrides it and triggers automatic collateral slashing. This consensus mechanism operates entirely off-chain for speed but relies on the Layer 1 smart contracts for final enforcement. Layer 3 — Application Layer channel consensus At the Application Layer, state updates within Virtual State Channels are agreed off-chain by the participating parties through quorum co-signing. Channels are created and managed entirely off-chain. The base blockchain is used only for asset custody and collateral slashing enforcement when fraud is detected by the Ledger Layer. This layered model provides scalability and near-instant transaction speed while retaining on-chain enforceability. Yellow does not replace blockchain consensus; it extends it — combining the finality of Ethereum's PoS, the security of threshold-signature consensus at the Ledger Layer, and the performance of off-chain channel consensus at the Application Layer. |
| H.5 | Incentive Mechanisms and Applicable Fees |
Fee structure and protocol fee accounting All network services — including trading, clearing, and protocol-level operations — require the consumption of YELLOW as a service access fee. The primary and incentivised method of payment is direct expenditure of YELLOW by the user, which receives a discounted fee rate. For users who do not yet hold YELLOW, an optional convenience mechanism allows payment in other supported assets (such as ETH or USDT); independent third-party liquidity providers convert the payment into YELLOW before the service fee is consumed by the protocol. This optional conversion is operated by third-party liquidity providers, not by the issuer, and does not constitute a currency exchange service, payment function, or value-stabilisation mechanism. Protocol fees from clearing and trading operations are locked into the collateral of the node operators that processed them, as described below. Fees from Yellow App Store subscriptions and premium application-layer features are directed to the Foundation Treasury to fund continued research, development, and delivery of the goods and services accessible through YELLOW. Node collateral and network security Posting YELLOW as collateral is a functional security requirement of the protocol. Yellow Network implements a Value-at-Risk security model: the protocol dynamically ensures that the total collateral posted by nodes responsible for any given account always exceeds the value of assets held in that account. This makes fraud economically irrational — an attacker who corrupts the nodes guarding an account would lose more collateral than they could steal. Node collateral serves three essential protocol functions: 1. Sybil resistance — a minimum collateral threshold per node prevents an attacker from cheaply flooding the network with malicious nodes to surround and compromise target accounts. 2. Fraud deterrence — if a node participates in producing a fraudulent transaction, its collateral is slashed automatically through on-chain fraud proofs. The collateral is the enforcement mechanism that makes the protocol's dispute resolution credible. 3. Dynamic security scaling — as the value held in any account grows, the protocol automatically assigns more nodes to guard it, requiring proportionally more collateral at risk. This ensures the cost of corruption always exceeds the value being protected. Nodes and applications post YELLOW as a mandatory security deposit to activate operational roles (e.g., clearnode operation, routing participation, app deployment). As a mandatory network security mechanism, protocol fees from processed transactions are locked into the collateral of the nodes that processed them, increasing those operators' slashing exposure proportionally — this does not constitute income, yield, or reward. Auto-compounded fees strengthen the security deposit, not the operator's financial returns. There is no fee distribution to passive token holders. Node operators who engage in misconduct or underperformance are subject to automatic collateral slashing. Node operator governance as a security mechanism The Yellow Network protocol depends on on-chain smart contracts that enforce collateral rules, process withdrawals, and verify cryptographic signatures. These contracts contain configurable operational parameters that must be updated as the network evolves — for example, security thresholds, network configuration, and fee parameters. Without governance, these contracts require a centralised administrator key — a single point of failure that, if compromised, could undermine the security model for every user on the network. Node operator governance replaces this centralised key with distributed multi-signature execution by the operators who run network infrastructure. Parameter changes require collective agreement from multiple independent operators rather than a single key holder. Governance participation is accessible only to active node operators — not to passive token holders. Eligibility requires running a clearnode with registered nodes, maintaining collateral above the protocol minimum, and actively processing transactions on the network. Governance participation is non-transferable, non-delegable, and terminates immediately upon cessation of node operations — it is a condition of the service-provider role, not a right attached to the YELLOW token. The token serves as mandatory collateral for node registration; governance eligibility derives exclusively from active infrastructure operation, not from token ownership or the quantity of tokens held. Governance scope is strictly limited to protocol-level service parameters: security thresholds, fee parameters, supported blockchain integrations, confirmation requirements, and protocol upgrade activation. Governance does not extend to token supply decisions, treasury allocation, or issuer corporate matters, which remain the responsibility of Layer3 Foundation and Layer3 Fintech Ltd. Please refer further to the information provided in section H.1 above. |
| H.6 | Use of distributed ledger technology |
|
| H.7 | DLT functionality description |
|
| H.8 | Audit |
|
| H.9 | Audit outcome |
Hacken (2024) — Hacken, an independent cybersecurity firm, performed a security assessment targeting the Ethereum smart contracts for the Yellow Network. The audit evaluated findings using Likelihood, Impact, Exploitability, and Complexity metrics. It concluded that the implementation was robust, with no critical issues found, affirming that Yellow’s engineering team had effectively protected against common attack vectors. The full report is publicly accessible here: https://hacken.io/audits/openware-yellow-network/sca-yellow-network-vault-sept-2024/ GuardianAudits (ongoing) — GuardianAudits is auditing the decentralised ledger (Yellow Clearnet). Audit reports are published here: https://github.com/GuardianAudits/Audits/tree/main/Yellow%20Network/ |
| N | Field | Content |
|---|---|---|
| I.1 | Offer-related risks |
Liquidity conditions: YELLOW may experience low trading volumes or wide bid-ask spreads, particularly during early distribution or campaign-driven activity. Funds Loss: The public YELLOW token sale may carry risks such as transaction errors, allocation mistakes, or offer cancellation, exposing participants to potential loss of funds or incorrect token allocation. Large transactions and scheduled unlocks: Pre-allocated YELLOW tranches are released according to a pre-defined, rule-based schedule. Scheduled releases from reserve allocations may affect market pricing as additional tokens enter circulation. Regulatory exposure and multi-jurisdiction complexity: As YELLOW will be traded in different countries and on various platforms, it may fall under multiple, evolving legal and regulatory regimes. Changes in these rules could affect where and how the asset can be traded. |
| I.2 | Issuer-related risks |
Governance Practices: Concentration of decision-making authority within a small group, or lack of transparency in governance processes, may create risks of mismanagement or reduced accountability. Limited disclosure of treasury movements or protocol updates could also affect credibility. Partnership Dependencies: Layer3 Fintech Ltd. works closely with brokers, validators, and technical partners. If key partners leave, fail to perform, or face issues, network operations could slow down. Heavy dependence on a few major partners increases the impact of any disruption. Regulatory Risks: As Yellow network operates globally, this requires adaptation to changing crypto regulations. New rules or stricter compliance demands could add costs or limit activity in some regions. Non-compliance or unclear token classification may also create legal or reputational risks. |
| I.3 | Crypto-assets-related risks |
Liquidity Risks: Limited market liquidity may make it difficult to buy or sell YELLOW tokens without causing large price changes. Low trading volumes or exchange availability could reduce the token’s usability in collateral and settlement functions. Market Manipulation Risks: Since token distribution and trading activity may be uneven, large holders could influence price movements. This creates potential exposure to market distortions if coordinated trading or concentrated ownership occurs. Irreversibility Risks: Transactions on the Yellow Network, like on most blockchains, are irreversible. Mistaken or unauthorised transfers cannot be undone, and funds lost in such cases cannot be recovered. Private Key Management Risks: Users must securely manage their private keys to access and transfer tokens. Loss, theft, or exposure of private keys results in permanent loss of assets, as there is no central authority to restore access. Custodial Risks: If users rely on third-party services or custodians for holding their tokens, they face the risk of loss due to technical failures, breaches, or poor management by those custodians. Privacy Risks: Although the Yellow Network supports transparency in transactions, all activity is recorded on-chain. This public visibility can potentially expose wallet addresses or transaction patterns, affecting user privacy. Treasury Risks: The Foundation Treasury is funded by fees from Yellow App Store subscriptions and premium application-layer features, and is used to fund continued research, development, and delivery of the goods and services accessible through YELLOW. Protocol fees from clearing and trading operations are separate and are locked into node operators’ collateral. If network activity declines, premium feature revenue may be insufficient to cover development costs. Market drops affecting reserve assets could also reduce available funds, creating short-term liquidity pressure. |
| I.4 | Project implementation-related risks |
Operational Interruptions and Downtime: Outages or degraded performance of brokers, nodes, or sequencers could temporarily halt transaction processing or reduce efficiency. Prolonged downtime would affect settlements and user experience. Governance and Control Risk: Weak governance safeguards could enable parameter manipulation or insufficient operator participation, affecting fair decision-making. Poorly designed procedures could also delay or block necessary protocol upgrades. Interdependency Across Systems: Modules within Yellow’s ecosystem, such as trading, clearing, and settlement, are interlinked. A malfunction in one area could cascade into others due to shared infrastructure and liquidity routing. Dependency on Third Parties: The project relies on external providers for infrastructure, such as security audits. Delays, miscommunication, or policy changes from these parties could slow progress or introduce vulnerabilities. Operator Concentration: If only a small group of node operators or brokers supports key functions, the network faces concentration risk. Collusion or downtime among these operators could disrupt service. Force-Majeure and Network Events: External events such as blockchain congestion, node outages, or global infrastructure failures could interrupt access or delay transaction processing. |
| I.5 | Technology-related risks |
Protocol logic defects in fraud detection and slashing: Logic errors in the Ledger Layer’s threshold-signature consensus or independent verification mechanism may result in undetected fraud or incorrect collateral slashing. Cryptographic risks: Compromise of signature algorithms or future quantum computing advances could endanger signature validity. Infrastructure and service dependencies: Dependencies on clearnodes, RPC gateways, explorers, and indexers could create single points of failure or data inconsistency. |
| I.6 | Mitigation measures |
Funds Loss: Purchasers benefit from a 14-day withdrawal right, allowing them to recover their funds and full reimbursement is guaranteed if the offer is cancelled. All funds are securely held in safeguarded accounts or managed by regulated third-party custodians until token allocation is complete. Layer3 Fintech Ltd. actively monitors these arrangements to ensure compliance, security, and proper handling of participant assets. Issuer-Related Risks — Operational Integrity: To strengthen operational integrity, Yellow requires node operators to deposit collateral, and incorporates automated smart-contract dispute resolution mechanisms. The Yellow Clearnet (Ledger Layer) provides a distributed peer-to-peer ledger with threshold-signature consensus and independent fraud verification, enabling secure and decentralised transaction settlement between brokers and exchanges. Governance Practices: Yellow is transitioning protocol parameter administration from the Layer3 Foundation administrator key to distributed multi-signature execution by active node operators. This replaces a single point of failure with collective operational oversight, restricted to protocol parameters and limited to participants running network infrastructure. Treasury risks: The Foundation Treasury is funded by premium feature and App Store subscription fees and is managed by Layer3 Foundation, with allocation decisions made by the Foundation's management — not by token-holder or protocol governance. Treasury management follows documented policies covering diversification, operational continuity, and quarterly reporting. Crypto-asset-Related Risks — Privacy and Custody: Yellow emphasises self-custody for users, ensuring that token holders maintain direct control over their assets, reducing dependency on third-party custodians and lowering the risk of loss from external breaches or mismanagement. Project-Implementation-Related Risks — Dependency on Third Parties: Yellow network works with a broad range of specialised partners rather than relying on a single provider in any field. For example, HackenAI and Zokyo provide security audits, while Cobo and Fireblocks handle custody and treasury management. Other fields, such as blockchain infrastructure, developer tools, and trading integrations, are also supported by multiple partners. Technology-Related Risks — Smart-contract and protocol logic defects: Yellow commissioned independent audits by Hacken in 2024 covering logic correctness, exploitability, and arithmetic safety. No critical vulnerabilities were found. |
| N | Field | Content |
|---|---|---|
| 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 |
|
| S.2 | Relevant legal entity identifier |
|
| S.3 | Name of the crypto-asset |
|
| S.4 | Consensus Mechanism |
Layer 1 (Base blockchain) — YELLOW is an ERC-20 token on Ethereum, so its ownership and transfers are secured by Ethereum's Proof-of-Stake (PoS) consensus. Validators stake ETH to produce and attest blocks, providing global security, settlement finality, and ledger integrity. Layer 2 (Ledger Layer) — Within the Yellow Clearnet, each user account is guarded by a group of nodes that reach consensus through threshold cryptographic signatures. A supermajority must co-sign every state update. A separate set of nodes independently verifies state changes and can trigger on-chain fraud proofs. Layer 3 (Application Layer) — Application-level state updates within Virtual State Channels are agreed off-chain by participants through quorum co-signing. Collateral slashing is enforced on-chain when fraud is detected by the Ledger Layer. Network fees are denominated in YELLOW (see section H.5 for the fee structure and incentive mechanism). |
| S.5 | Incentive Mechanisms and Applicable Fees |
|
| S.6 | Beginning of the period to which the disclosed information relates |
|
| S.7 | End of period to which disclosed information relates |
|
| Mandatory key indicator | ||
| S.8 | Energy consumption |
|
| Sources and methodologies | ||
| S.9 | Energy consumption sources and methodologies |
|
| Supplementary information on principal adverse impacts on climate and other environment-related adverse impacts of the consensus mechanism | ||
| Supplementary key indicators | ||
| 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 |
|
| Sources and methodologies | ||
| S.15 | Key energy sources and methodologies |
|
| S.16 | Key GHG sources and methodologies |
|
| 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 | |
| S.18 | Energy use reduction | N/A |
| S.19 | Carbon intensity |
|
| S.20 | Scope 3 DLT GHG emissions – Value chain | N/A |
| S.21 | GHG emissions reduction targets or commitments | N/A |
| S.22 | Generation of waste electrical and electronic equipment (WEEE) |
|
| S.23 | Non-recycled WEEE ratio |
|
| S.24 | Generation of hazardous waste |
|
| S.25 | Generation of waste (all types) |
|
| S.26 | Non-recycled waste ratio (all types) |
|
| S.27 | Waste intensity (all types) |
|
| S.28 | Waste reduction targets or commitments (all types) | N/A |
| S.29 | Impact of the use of equipment on natural resources |
|
| S.30 | Natural resources use reduction targets or commitments | N/A |
| S.31 | Water use |
|
| S.32 | Non recycled water ratio |
|
| Sources and and methodologies | ||
| S.33 | Other energy sources and methodologies |
|
| S.34 | Other GHG sources and methodologies |
|
| S.35 | Waste sources and methodologies |
|
| S.36 | Natural resources sources and methodologies |
|