| [Table 2] Template for white papers for crypto-assets other than asset-referenced tokens or e-money tokens | |||||
| Template for white papers for crypto-assets other than asset-referenced tokens or e-money tokens [abstract] | |||||
| General information | |||||
| 00 Table of content | boolean true | ||||
| 01 Date of notification | date | ||||
| 02 Statement in accordance with Article 6(3) of Regulation (EU) 2023/1114 | boolean true | ||||
| 03 Compliance statement in accordance with Article 6(6) of Regulation (EU) 2023/1114 | boolean true | ||||
| 04 Statement in accordance with Article 6(5), points (a), (b), (c), of Regulation (EU) 2023/1114 | boolean true | ||||
| 05 Statement in accordance with Article 6(5), point (d), of Regulation (EU) 2023/1114 | boolean true | ||||
| 06 Statement in accordance with Article 6(5), points (e) and (f), of Regulation (EU) 2023/1114 | boolean true | ||||
| SUMMARY | |||||
| 07 Warning in accordance with Article 6(7), second subparagraph, of Regulation (EU) 2023/1114 | boolean true | This summary should be read as an introduction to the crypto-asset white paper. The prospective holder should base any decision to purchase this crypto-asset on the content of the crypto-asset white paper as a whole and not on the summary alone. The offer to the public of this crypto-asset does not constitute an offer or solicitation to purchase financial instruments and any such offer or solicitation can be made only by means of a prospectus or other offer documents pursuant to the applicable national law. This crypto-asset white paper does not constitute a prospectus as referred to in Regulation (EU) 2017/1129 of the European Parliament and of the Council or any other offer document pursuant to Union or national law. |
|||
| 08 Characteristics of the crypto-asset | textBlock | The tokens provide functional utility within the dappOS ecosystem, which has processed over 12 million transactions for more than 5 million users (as of Q4 2025), specifically: subscription payments for premium AI services (such as the Bubble Engine); payment of transaction fees for intent executions within the ecosystem (with discounts compared to payments in other mainstream tokens); staking as collateral by service providers and validators (including Super Nodes and Execution Validators) within the Intent Execution Network; and participation in ecosystem incentive programs. Token holders currently have no governance rights (governance functionality is planned as a future feature; see F.3), no claims to dividends or profit distributions, and no ownership rights in Dapp OS Technology Pte. Ltd. The tokens are not redeemable for fiat currency or any other assets from the issuer. Transferability may be restricted during active staking periods subject to network protocol rules. |
|||
| 09 Further information about utility tokens | textBlock | ||||
| 10 Key information about the offer to the public or admission to trading | textBlock | ||||
| Part A - Information about offeror or person seeking admission to trading | |||||
| A.1 Name | text | ||||
| A.2 Legal form | text | ||||
| A.3 Registered address | |||||
| Registered addess | text | ||||
| Country | enumeration | ||||
| Sub-division | text | ||||
| A.4 Head office | |||||
| Head office | text | ||||
| Country | enumeration | ||||
| Sub-division | text | ||||
| A.5 Registration date | date | ||||
| A.6 Legal entity identifier | LEI | ||||
| A.7 Another identifier required pursuant to applicable national law | text | ||||
| A.8 Contact telephone number | text | ||||
| A.9 E-mail address | text | ||||
| A.10 Response time (days) | integer | ||||
| A.11 Parent company | text | ||||
| A.12 Members of the management body | |||||
| Member #1 | id | 1 | |||
| Identity | text | ||||
| Business address | text | ||||
| Function | text | ||||
| Member #2 | id | 2 | |||
| Identity | text | ||||
| Business address | text | ||||
| Function | text | ||||
| Member #3 | id | 3 | |||
| Identity | text | ||||
| Business address | text | ||||
| Function | text | ||||
| A.13 Business activity | textBlock | ||||
| A.14 Parent company business activity | textBlock | ||||
| A.15 Newly established | boolean | ||||
| A.16 Financial condition for the past three years | textBlock | DappOS raised USD 15.3 million in a Series A financing round in 2024. A seed financing round was completed in 2023. As of Q4 2025, the Intent Execution Network has processed over 5 million users and 12 million transactions. |
|||
| A.17 Financial condition since registration | textBlock | ||||
| Part B - Information about issuer, if different from offeror or person seeking admission to trading | |||||
| B.1 Issuer different from offerror or person seeking admission to trading | boolean | ||||
| B.2 Name | text | ||||
| B.3 Legal form | text | ||||
| B.4 Registered address | |||||
| Registered addess | text | ||||
| Country | enumeration | ||||
| Sub-division | text | ||||
| B.5 Head office | |||||
| Head office | text | ||||
| Country | enumeration | ||||
| Sub-division | text | ||||
| B.6 Registration date | date | ||||
| B.7 Legal entity identifier | LEI | ||||
| B.8 Another identifier required pursuant to applicable national law | text | ||||
| B.9 Parent company | text | ||||
| B.10 Members of the management body | |||||
| Member #1 | id | 1 | |||
| Identity | text | ||||
| Business address | text | ||||
| Function | text | ||||
| Member #2 | id | 2 | |||
| Identity | text | ||||
| Business address | text | ||||
| Function | text | ||||
| Member #3 | id | 3 | |||
| Identity | text | ||||
| Business address | text | ||||
| Function | text | ||||
| B.11 Business activity | textBlock | ||||
| B.12 Parent company business activity | textBlock | Part C – Information about the operator of the trading platform in cases where it draws up the crypto-asset white paper and information about other persons drawing the crypto-asset white paper pursuant to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 |
|||
| Part C - Information about the operator of the trading platform in cases where it draws up the crypto-asset white paper and information about other persons drawing the crypto-asset white paper pursuant to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | |||||
| C.1 Name | N/A | . | |||
| C.2 Legal form | N/A | . | |||
| C.3 Registered address | |||||
| Registered address | N/A | . | |||
| Country | N/A | . | |||
| Sub-division | N/A | . | |||
| C.4 Head office | |||||
| Head office | N/A | . | |||
| Country | N/A | . | |||
| Sub-division | N/A | . | |||
| C.5 Registration date | N/A | . | |||
| C.6 Legal entity identifier | N/A | . | |||
| C.7 Another identifier required pursuant to applicable national law | N/A | . | |||
| C.8 Parent company | N/A | . | |||
| C.9 Reason for crypto-asset white paper preparation | N/A | . | |||
| C.10 Members of the management body | |||||
| Member #1 | N/A | . | |||
| Identity | N/A | . | |||
| Business address | N/A | . | |||
| Function | N/A | . | |||
| C.11 Operator business activity | N/A | . | |||
| C.12 Parent company business activity | N/A | . | |||
| C.13 Other persons drawing up the crypto-asset white paper according to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | N/A | . | |||
| C.14 Reason for drawing the white paper by persons referred to in Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | N/A | . | |||
| Part D - Information about other token project | |||||
| D.1 Crypto-asset project name | text | ||||
| D.2 Crypto-asset name | text | ||||
| D.3 Abbreviation | text | ||||
| D.4 Crypto-asset project description | textBlock | ||||
| D.5 Details of all natural or legal persons involved in implementation of crypto-asset project | |||||
| Person #1 | id | 1 | |||
| Type of person | enumeration | ||||
| Name of person | text | ||||
| Business address of person | text | ||||
| Domicile of company | enumeration | ||||
| Person #2 | id | 2 | |||
| Type of person | enumeration | ||||
| Name of person | text | ||||
| Business address of person | text | ||||
| Domicile of company | enumeration | ||||
| Person #3 | id | 3 | |||
| Type of person | enumeration | ||||
| Name of person | text | ||||
| Business address of person | text | ||||
| Domicile of company | enumeration | ||||
| Person #4 | id | 4 | |||
| Type of person | enumeration | ||||
| Name of person | text | ||||
| Business address of person | text | ||||
| Domicile of company | enumeration | ||||
| Person #5 | id | 5 | |||
| Type of person | enumeration | ||||
| Name of person | text | ||||
| Business address of person | text | ||||
| Domicile of company | enumeration | ||||
| D.6 Utility token classification | boolean | ||||
| D.7 Key features of goods or services for utility token projects | text | ||||
| D.8 Plans for the token | |||||
| Description of past milestones | textBlock | ||||
| Description of future milestones | textBlock | ||||
| D.9 Resource allocation | text | Current expenditure breakdown: 62.5% research and development, 30% marketing, 7.5% other operational activities. |
|||
| D.10 Planned use of collected funds or other tokens | text | ||||
| Part E - Information about offer to public of other tokens or their admission to trading | |||||
| E.1 Public offering or admission to trading | enumeration | ||||
| E.2 Reasons for public offer or admission to trading | textBlock | In addition, this crypto-asset white paper is intended to serve as a single reference document drawn up in accordance with the applicable MiCA templates. To reduce the risk of market confusion caused by multiple different white papers for the same crypto-asset prepared by different parties, this crypto-asset white paper is intended to be reusable by other entities admitting the crypto-asset to trading, subject to the written consent mechanism foreseen in Article 5(4) of Regulation (EU) 2023/1114. |
|||
| E.3 Fundraising target | |||||
| Target expressed in currency | monetary | EUR | |||
| Target expressed in units | decimal | ||||
| Target expressed in digital token identifier | text | ||||
| E.4 Minimum subscription goals | |||||
| Goals expressed in currency | monetary | EUR | |||
| Goals expressed in units | decimal | ||||
| Goals expressed in digital token identifier | text | ||||
| E.5 Maximum subscription goals | |||||
| Goasl expressed in currency | monetary | EUR | |||
| Goals expressed in units | decimal | ||||
| Goals expressed in digital token identifier | text | ||||
| E.6 Oversubscription acceptance | boolean | ||||
| E.7 Oversubscription allocation | text | ||||
| Issue price details | |||||
| E.8 Issue price | decimal | ||||
| E.9 Official currency determining issue price | enumeration | ||||
| E.9 Any other tokens determining issue price | text | ||||
| E.10 Subscription fee | |||||
| Fee expressed in currency | monetary | EUR | |||
| Fee expressed in units | decimal | ||||
| Fee expressed in digital token identifier | text | ||||
| E.11 Offer price determination method | text | ||||
| E.12 Total number of offered or traded other tokens | integer | ||||
| E.13 Targeted holders | enumeration | ||||
| E.14 Holder restrictions | text | ||||
| E.15 Reimbursement notice | boolean true | ||||
| E.16 Refund mechanism | textBlock | ||||
| E.17 Refund timeline | text | ||||
| E.18 Offer phases | textBlock | ||||
| E.19 Early purchase discount | textBlock | ||||
| E.20 Time-limited offer | boolean | ||||
| E.21 Subscription period beginning | date | ||||
| E.22 Subscription period end | date | ||||
| E.23 Safeguarding arrangements for offered funds or other tokens | textBlock | ||||
| E.24 Payment methods for other token purchase | textBlock | ||||
| E.25 Value transfer methods for reimbursement | textBlock | ||||
| E.26 Right of withdrawal | textBlock | ||||
| E.27 Transfer of purchased other tokens | textBlock | ||||
| E.28 Transfer time schedule | text | ||||
| E.29 Purchaser's technical requirements | textBlock | ||||
| Other token services provider characteristics | |||||
| E.30 Other token service provider (CASP) name | text | ||||
| E.31 CASP identifier | LEI | ||||
| E.32 Placement form | enumeration | ||||
| Trading platforms characteristics | |||||
| E.33 Trading platforms name | text | ||||
| E.34 Trading platforms market identifier code (MIC) | text | ||||
| E.35 Trading platforms access | text | ||||
| E.36 Involved costs | textBlock | ||||
| E.37 Offer expenses | textBlock | ||||
| E.38 Conflicts of interest | textBlock | MiCA-compliant crypto-asset service providers are required to have arrangements in place to identify, prevent, manage and disclose conflicts of interest. Prospective holders should also review the conflicts of interest policy of the trading platform used for trading. |
|||
| E.39 Applicable law | textBlock | ||||
| E.40 Competent court | textBlock | ||||
| Part F - Information about other tokens | |||||
| F.1 Crypto-asset type | text | The asset does not aim to maintain a stable value by referencing an official currency, a basket of assets, or any other underlying rights. Instead, its valuation is entirely market-driven, based on supply and demand dynamics, and not supported by a stabilization mechanism. It is neither pegged to any fiat currency nor backed by any external assets, distinguishing it clearly from EMTs and ARTs. Furthermore, the crypto-asset is not categorised as a financial instrument, deposit, insurance product, pension product, or any other regulated financial product under EU law. It does not grant financial rights or any contractual claims to its holders, ensuring that it remains outside the scope of regulatory frameworks applicable to traditional financial instruments. |
|||
| F.2 Other token functionality | textBlock | ||||
| F.3 Planned application of functionalities | textBlock | The token-specific functionalities described in F.2, including subscription payments in $DOS, transaction fee payments in $DOS (with associated discounts), staking of $DOS as collateral by service providers and validators, and $DOS-denominated ecosystem incentive programs, are expected to go live in connection with the Token Generation Event, targeted for Q3 2026. The protocol architecture supports the potential introduction of governance functionality. No decision to activate governance has been made. There is no assurance that all functionalities will be activated as described or within the indicated timeframe. 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 |
|||
| A description of the characteristics of the other token, including the data necessary for classification of the crypto-asset white paper in the register referred to in Article 109 of Regulation (EU) 2023/1114, as specified in accordance with paragraph 8 of that Article | |||||
| F.4 Type of crypto-asset white paper | enumeration | ||||
| F.5 Type of submission | enumeration | ||||
| F.6 Other token characteristics | textBlock | ||||
| F.7 Commercial name or trading name | text | ||||
| F.8 Website of the issuer | text | ||||
| F.9 Starting date of offer to the public or admission to trading | date | ||||
| F.10 Publication date | date | ||||
| F.11 Any other services provided by the issuer | textBlock | ||||
| F.12 Language or languages of white paper | text | ||||
| F.13 Digital token identifier code used to uniquely identify the crypto-asset or each of the several crypto assets to which the white paper relates, where available | text | ||||
| F.14 Functionally fungible group digital token identifier, where available | text | ||||
| F.15 Voluntary data flag | boolean | ||||
| F.16 Personal data flag | boolean | ||||
| F.17 LEI eligibility | boolean | ||||
| F.18 Home member state | enumeration | ||||
| F.19 Host member states #1 | enumerationSet | ||||
| F.19 Host member states #2 | enumerationSet | ||||
| F.19 Host member states #3 | enumerationSet | ||||
| F.19 Host member states #4 | enumerationSet | ||||
| F.19 Host member states #5 | enumerationSet | ||||
| F.19 Host member states #6 | enumerationSet | ||||
| F.19 Host member states #7 | enumerationSet | ||||
| F.19 Host member states #8 | enumerationSet | ||||
| F.19 Host member states #9 | enumerationSet | ||||
| F.19 Host member states #10 | enumerationSet | ||||
| F.19 Host member states #11 | enumerationSet | ||||
| F.19 Host member states #12 | enumerationSet | ||||
| F.19 Host member states #13 | enumerationSet | ||||
| F.19 Host member states #14 | enumerationSet | ||||
| F.19 Host member states #15 | enumerationSet | ||||
| F.19 Host member states #16 | enumerationSet | ||||
| F.19 Host member states #17 | enumerationSet | ||||
| F.19 Host member states #18 | enumerationSet | ||||
| F.19 Host member states #19 | enumerationSet | ||||
| F.19 Host member states #20 | enumerationSet | ||||
| F.19 Host member states #21 | enumerationSet | ||||
| F.19 Host member states #22 | enumerationSet | ||||
| F.19 Host member states #23 | enumerationSet | ||||
| F.19 Host member states #24 | enumerationSet | ||||
| Part G - Information on rights and obligations attached to other tokens | |||||
| G.1 Purchaser rights and obligations | textBlock | ||||
| G.2 Exercise of rights and obligations | textBlock | ||||
| G.3 Conditions for modifications of rights and obligations | textBlock | ||||
| G.4 Future public offers | textBlock | ||||
| G.5 Issuer retained other token | integer | ||||
| G.6 Utility token classification | boolean | ||||
| G.7 Key features of goods or services utility tokens | text | ||||
| G.8 Utility tokens redemption | text | ||||
| G.9 Non-trading request | boolean | ||||
| G.10 Other tokens purchase or sale modalities | text | ||||
| G.11 Other tokens transfer restrictions | text | ||||
| G.12 Supply adjustment protocols | boolean | ||||
| G.13 Supply adjustment mechanisms | text | ||||
| Other token schemes details | |||||
| G.14 Token value protection schemes | boolean | ||||
| G.15 Token value protection schemes description | textBlock | ||||
| G.16 Compensation schemes | boolean | ||||
| G.17 Compensation schemes description | textBlock | ||||
| G.18 Applicable law | textBlock | ||||
| G.19 Competent court | textBlock | Part H – information on the underlying technology |
|||
| Part H – Information on underlying technology | |||||
| H.1 Distributed ledger technology (DTL) | text | ||||
| H.2 Protocols and technical standards | text | The Ethereum mainnet token contract includes a pause mechanism, allowing the issuer to temporarily suspend token transfers. The contract does not support upgradeability or blacklisting, and there are no role-based mint or burn permissions beyond the initial minting. Bridging to BNB Chain is facilitated through LayerZero, a third-party interoperability protocol. Contracts associated with bridged representations on BNB Chain, deployed by the bridge provider, may include additional functionalities such as pausability and upgradeability. These contracts are not under the issuer's direct control. |
|||
| H.3 Technology used | textBlock | The token is natively issued on the Ethereum mainnet. A bridged representation exists on BNB Chain, facilitated through LayerZero. The bridge operates via a lock-and-mint mechanism whereby tokens are locked on Ethereum and corresponding representations are minted on BNB Chain. The bridge infrastructure is operated by a third party and is not under the direct control of the issuer. Users must securely manage their private keys and recovery phrases. Loss of these credentials results in permanent and irreversible loss of access to the associated tokens. |
|||
| H.4 Consensus mechanism | text | The following applies to Ethereum: Ethereum uses a Proof-of-Stake (PoS) consensus mechanism, introduced with The Merge in September 2022. Validators must stake at least 32 ETH to participate in block production. For each block, a validator is randomly chosen to propose the next block; once proposed, other validators verify its integrity. The network operates on a slot and epoch system, where a new block is proposed every 12 seconds and finalization occurs after two epochs (approximately 12.8 minutes) using Casper-FFG. The Beacon Chain coordinates validators, while the fork-choice rule (LMD-GHOST) ensures the chain follows the heaviest accumulated validator votes. Validators earn rewards for proposing and verifying blocks, but face slashing for malicious behaviour or inactivity. PoS aims to improve energy efficiency, security, and scalability, with future upgrades like Proto-Danksharding enhancing transaction efficiency. The following applies to BNB Smart Chain: BNB Smart Chain uses a hybrid consensus mechanism called Proof of Staked Authority (PoSA), which combines elements of Delegated Proof of Stake (DPoS) and Proof of Authority (PoA). This method ensures fast block times and low fees while maintaining a level of decentralization and security. Validators are responsible for producing new blocks, validating transactions, and maintaining network security. To become a validator, an entity must run a validator node and stake a significant amount of BNB. On a daily basis, the 45 validators with the highest stake and delegation are selected as active validators. Every epoch (240 blocks, approximately 20 minutes), 21 consensus validators are picked from the active set to take turns producing blocks. Token holders who do not wish to run a validator node can delegate their BNB to validators, earning a share of rewards and improving their chosen validator's selection chances. Inactive validators remain in a pool, ensuring a sufficient number of nodes are ready to take on validation tasks. BNB Smart Chain achieves block times of around 0.75 seconds. Validators are required to stake BNB as collateral, which can be slashed for malicious behaviour. Delegators earn rewards proportional to their stake, and transaction fees are paid in BNB. |
|||
| H.5 Incentive mechanisms and applicable fees | text | The dappOS ecosystem employs the following incentive mechanisms and fee structures at the protocol level: Service providers and validators within the Intent Execution Network (including Super Nodes and Execution Validators) are required to stake $DOS tokens as collateral. This staking secures the network by creating economic accountability for the correct execution of user intents through the Optimistic Minimum Staking (OMS) mechanism. Validators who fail to perform or act dishonestly are subject to slashing penalties, resulting in partial or total loss of staked collateral. Users pay fees for intent executions within the dappOS ecosystem. Payments in $DOS tokens are subject to discounted fee rates compared to payments in other mainstream tokens. Fee parameters may be adjusted by the core development team. Access to premium AI services (such as the Bubble Engine) requires subscription payments in $DOS tokens. $DOS tokens are distributed as rewards to participants who contribute to the ecosystem, subject to applicable conditions and eligibility criteria as determined by the protocol rules. Underlying network fees: In addition to the protocol-level fees described above, all on-chain transactions involving $DOS tokens are subject to network transaction fees ("gas fees") on the respective underlying blockchain. On Ethereum, transaction fees are paid in ETH under the EIP-1559 fee model (base fee plus optional priority fee). On BNB Smart Chain, transaction fees are paid in BNB. These network-level fees are independent of the dappOS protocol and may vary depending on network congestion. |
|||
| H.6 Use of distributed ledger technology | boolean | ||||
| H.7 DLT functionality description | textBlock | ||||
| Other token audit details | |||||
| H.8 Audit | boolean | ||||
| H.9 Audit outcome | textBlock | Part I – Information on risks |
|||
| Part I - Information on risks | |||||
| I.1 Offer-related risks | textBlock | This white paper has been prepared with utmost caution; however, uncertainties in the regulatory requirements and future changes in regulatory frameworks could potentially impact the token's legal status and its tradability. There is also a high probability that other laws will come into force, changing the rules for the trading of the token. Therefore, such developments shall be monitored and acted upon accordingly. 2. Operational and technical Blockchain Dependency: The token is entirely dependent on the blockchains the crypto-asset is issued upon. Any issues, such as downtime, congestion, or security vulnerabilities within the blockchain, could adversely affect the token's functionality. Smart Contract Risks: Smart contracts governing the token may contain hidden vulnerabilities or bugs that could disrupt the token offering or distribution processes. Connection Dependency: As the trading of the token also involves other trading venues, technical risks such as downtime of the connection or faulty code are also possible. Human errors: Due to the irrevocability of blockchain transactions, approving wrong transactions or using incorrect networks or addresses will most likely result in funds not being accessible anymore. Custodial risk: When admitting the token to trading, the risk of losing clients' assets due to hacks or other malicious acts is given. This is due to the fact the token is held in custodial wallets for the customers. Multi-network and interoperability risk: The token is deployed on more than one network (Ethereum mainnet and BNB Chain). The bridge mechanics applicable to tokens transferred between networks are described in H.3 above. Bridges have historically been sensitive to malfunctions and exploits. If bridging is used, it may pose an additional source of risk for token holders, including operational control over mint/burn/release functions and potential smart contract vulnerabilities in bridge contracts. The total number of tokens across all networks and any spillover effects must be taken into account. Protocol-utility dependency: Separately from network gas fees on the underlying blockchains (paid in ETH or BNB respectively), the token relies on protocol-level functionalities within the dappOS ecosystem, including subscription payments, transaction fee payments, staking and collateral mechanisms, and ecosystem incentive programs. Any malfunction, change, or discontinuation of such functionalities could adversely affect the token's perceived utility and market value. 3. Market and liquidity Volatility: The token will most likely be subject to high volatility and market speculation. Price fluctuations could be significant, posing a risk of substantial losses to holders. Liquidity Risk: Liquidity is contingent upon trading activity levels on decentralized exchanges (DEXs) and potentially on centralized exchanges (CEXs), should they be involved. Low trading volumes may restrict the buying and selling capabilities of the tokens. 4. Counterparty As the admission to trading involves the connection to other trading venues, counterparty risks arise. These include, but are not limited to, the following risks: General Trading Platform Risk: The risk of trading platforms not operating to the highest standards is given. Examples like FTX show that especially in nascent industries, compliance and oversight-frameworks might not be fully established and/or enforced. Listing or Delisting Risks: The listing or delisting of the token is subject to the trading partners internal processes. Delisting of the token at the connected trading partners could harm or completely halt the ability to trade the token. 5. Liquidity Liquidity of the token can vary, especially when trading activity is limited. This could result in high slippage when trading a token. 6. Failure of one or more counterparties Another risk stems from the internal operational processes of the counterparties used. As there is no specific oversight other than the typical due diligence check, it cannot be guaranteed that all counterparties adhere to the best market standards. Bankruptcy Risk: Counterparties could go bankrupt, possibly resulting in a total loss for the clients' assets held at that counterparty. Concentration and market integrity risk: Especially in early-stage markets, trading can be influenced by concentration of holdings, limited free float, market-making behaviour, or coordinated trading activity. This can amplify volatility, widen spreads, and increase the risk of market abuse. |
|||
| I.2 Issuer-related risks | textBlock | As with every other commercial endeavor, the risk of insolvency of the issuer is given. This could be caused by but is not limited to lack of interest from the public, lack of funding, incapacitation of key developers and project members, force majeure (including pandemics and wars) or lack of commercial success or prospects. 2. Counterparty In order to operate, the issuer has most likely engaged in different business relationships with one or more third parties on which it strongly depends on. Loss or changes in the leadership or key partners of the issuer and/or the respective counterparties can lead to disruptions, loss of trust, or project failure. This could result in a total loss of economic value for the crypto-asset holders. 3. Legal and regulatory compliance Cryptocurrencies and blockchain-based technologies are subject to evolving regulatory landscapes worldwide. Regulations vary across jurisdictions and may be subject to significant changes. Non-compliance can result in investigations, enforcement actions, penalties, fines, sanctions, or the prohibition of the trading of the crypto-asset impacting its viability and market acceptance. This could also result in the issuer to be subject to private litigation. The beforementioned would most likely also lead to changes with respect to trading of the crypto-asset that may negatively impact the value, legality, or functionality of the crypto-asset. 4. Operational Failure to develop or maintain effective internal control, or any difficulties encountered in the implementation of such controls, or their improvement could harm the issuer's business, causing disruptions, financial losses, or reputational damage. 5. Industry The issuer is and will be subject to all of the risks and uncertainties associated with a crypto-asset project in a highly competitive and nascent sector. History has shown that many projects in the crypto-asset sector resulted in financial losses for the investors. The token's intended utility is linked to the adoption of the dappOS ecosystem. Any failure to achieve sufficient ecosystem adoption, or material changes to the protocol design, fee schedules, or incentive structures, can reduce demand for the token and adversely affect its perceived value. 6. Reputational The issuer faces the risk of negative publicity, whether due to, without limitation, operational failures, security breaches, or association with illicit activities, which can damage the issuer reputation and, by extension, the value and acceptance of the crypto-asset. 7. Competition There are numerous other crypto-asset projects in the same realm, which could have an effect on the crypto-asset in question. 8. Unanticipated risk In addition to the risks included in this section, there might be other risks that cannot be foreseen. Additional risks may also materialize as unanticipated variations or combinations of the risks discussed. As of the date of this white paper, no decentralised governance framework has been deployed. Key decisions regarding the protocol, economic parameters, and technical architecture are taken by the core development team. This concentration of decision-making authority may result in changes that adversely affect token holders. |
|||
| I.3 Other tokens-related risks | textBlock | The token provides functional utility within the dappOS ecosystem but does not grant legally enforceable financial rights or contractual obligations. Its price is determined by supply and demand. Historically, most crypto-assets have lost value dramatically and were not a beneficial investment. Investing therefore poses a high risk, and a total loss of funds can occur. 2. Market volatility Crypto-asset prices are highly susceptible to dramatic fluctuations driven by market sentiment, regulatory changes, technological developments, and macroeconomic conditions. These fluctuations can cause significant losses within short periods. This is especially true for crypto-assets without intrinsic value, and holders should be prepared to lose the entire amount invested. 3. Liquidity challenges Limited liquidity can make it difficult to execute large trades without materially affecting the market price. This can lead to substantial losses, particularly during rapid market movements, when selling may be challenging or possible only at unfavourable prices. 4. Asset security Crypto-assets face security threats including theft from exchanges or wallets, loss of private keys, and failures of custodial services. Because transactions are generally irreversible, a security breach or mismanagement can result in the permanent loss of assets. 5. Scams The irreversibility of blockchain transactions and the pseudonymous nature of blockchain ecosystems attract fraud. Investors should proceed with caution. Typical scams include, but are not limited to, fake crypto-assets using the same name, phishing on social networks or by email, fake giveaways or airdrops, and identity theft. 6. Blockchain dependency Issues with the underlying blockchains, such as downtime, congestion, or security vulnerabilities, could disrupt the transfer, trading, or functionality of the crypto-asset. 7. Smart contract vulnerabilities The smart contracts used to issue the crypto-asset may contain bugs, coding errors, or vulnerabilities that could be exploited by malicious actors, potentially leading to asset loss, unauthorised data access, or unintended operational consequences. 8. Privacy concerns All transactions on the blockchain are permanently recorded and publicly accessible. Although addresses are pseudonymous, the transparent and immutable nature of blockchain permits forensic analysis that can, over time, link addresses to real-world identities, compromising user privacy. 9. Regulatory uncertainty The regulatory environment for crypto-assets is evolving and may directly affect their usage, valuation, and legal status. New requirements relating to consumer protection, taxation, or anti-money laundering may arise. Although the crypto-asset does not create contractual obligations, a regulator may nevertheless qualify it as a security or other financial instrument under its applicable law, with drastic consequences, including potential loss of the invested capital. This could also expose the issuer, its affiliates, directors, and officers to fines or penalties, or make the crypto-asset illegal to use, buy, or sell in certain jurisdictions. Regulators could also act against the issuer or the trading platforms if they view the token as an unregistered securities offering. Any such outcome could negatively affect the value or functionality of the crypto-asset and could cause a complete loss of the invested funds. 10. Counterparty risk Entering into agreements with, or storing crypto-assets on, exchanges introduces counterparty risk, including the failure of the other party to perform. Losses may result from insolvency, regulatory non-compliance, or fraud, underlining the need for careful due diligence. 11. Reputational concerns Crypto-assets are subject to reputational risks arising from associations with illegal activity, security breaches, and technological failures. Such incidents can undermine trust, reduce investor confidence and market value, and hinder adoption. 12. Technological innovation New technologies could render the DLT or ecosystem design less competitive or break fundamental components (for example, quantum computing could break the cryptographic algorithms securing the network), affecting adoption and value. Participants should understand the speculative and volatile nature of the crypto-asset and be prepared to bear losses up to a complete loss of value. 13. Community and narrative As the crypto-asset has no intrinsic value, its market value depends heavily on its community and the popularity of its narrative. Declining interest or negative sentiment could significantly affect the token's value. 14. Interest rate change Changes in interest and exchange rates, and increased volatility, have historically raised credit and market risks and may affect the value of the crypto-asset. Investors should be aware that general market movements may affect sentiment and therefore the token's price. 15. Taxation The tax treatment of trading the crypto-asset depends on the holder's jurisdiction. It is the holder's sole responsibility to comply with all applicable tax laws, including the reporting and payment of income tax, wealth tax, or similar taxes arising from the appreciation or depreciation of the crypto-asset. 16. Anti-money laundering / counter-terrorism financing It cannot be ruled out that wallet addresses interacting with the crypto-asset have been or will be used for money laundering or terrorist financing, or are associated with a person known to have committed such offences. 17. Market abuse Crypto-assets can be prone to market abuse, as the underlying infrastructure may be used for front-running, spoofing, pump-and-dump schemes, and fraud across systems, platforms, or locations. This is especially true for crypto-assets with low market capitalisation and few trading venues, and could lead to a total loss of the invested funds. 18. Timeline and milestones Critical project milestones could be delayed by technical, operational, or market challenges. The token is available on Ethereum mainnet and BNB Chain; the total number of tokens across networks, the bridge mechanics, and potential spillover effects between deployments must be taken into account, as they may adversely affect investors. The token's utility within the dappOS ecosystem (subscription fees, transaction fees with $DOS discounts, staking and collateral with slashing penalties, and ecosystem incentives) depends on the protocol design. Changes to that design, its parameters, eligibility rules, fee schedules, reward mechanics, slashing conditions, or access conditions can adversely affect token demand, usability, and value, and may be implemented unilaterally by the core development team, as no decentralised governance framework has been deployed as of the drafting date. If governance functionality is introduced in the future, the structure, voting mechanics, and decision-making authority of such a body may create additional risks, and governance decisions could adversely affect the value or usability of the crypto-asset. |
|||
| I.4 Project implementation-related risks | textBlock | ||||
| I.5 Technology-related risks | textBlock | 1. Blockchain dependency risks Network Downtime: Potential outages or congestion on the involved networks could interrupt on-chain token transfers, trading, and other functions. Scalability Challenges: Unexpected demand or technical issues might compromise network performance. 2. Smart contract risks Vulnerabilities: The smart contract(s) governing The token could contain bugs, coding errors, or vulnerabilities that may be exploited, affecting token transfers and other token-related functions. 3. Wallet and storage risks Private Key Management: Token holders must securely manage their private keys and recovery phrases to prevent permanent loss of access to their tokens, which includes Trading-Venues, who are a prominent target for dedicated hacks. Compatibility Issues: The token requires compatible wallets and supporting infrastructure for storage and transfer. Any incompatibility or technical issues could impact token accessibility. 4. Network security risks Attack Risks: The networks may face threats such as denial-of-service (DoS) attacks or exploits targeting network components, which could compromise network integrity. Centralization Concerns: Depending on the underlying network, concentration effects (e.g., validator concentration or stake concentration) may pose centralization risks, potentially affecting network resilience. 5. Evolving technology risks: technological obsolescence The fast pace of innovation in blockchain technology may make the used token standard and supporting infrastructure appear less competitive or become outdated, potentially impacting the usability or adoption of the token. |
|||
| I.6 Mitigation measures | textBlock | Part J – Information on the sustainability indicators in relation to adverse impact on the climate and other environment-related adverse impacts |
|||
| Part J - Information on the sustainability indicators in relation to adverse impact on the climate and other environment-related adverse impacts | |||||
| J.1 Adverse impacts on climate and other environment-related adverse impacts | textBlock | ||||
| Mandatory information on principal adverse impacts on the climate and other environment-related adverse impacts of the consensus mechanism | |||||
| General information about adverse impacts | |||||
| S.1 Name | text | ||||
| S.2 Relevant legal entity identifier | text | ||||
| S.3 Name of the crypto-asset | text | ||||
| S.4 Consensus mechanism | text | The following applies to Ethereum: Ethereum uses a Proof-of-Stake (PoS) consensus mechanism, introduced with The Merge in September 2022. Validators must stake at least 32 ETH to participate in block production. For each block, a validator is randomly chosen to propose the next block; once proposed, other validators verify its integrity. The network operates on a slot and epoch system, where a new block is proposed every 12 seconds and finalization occurs after two epochs (approximately 12.8 minutes) using Casper-FFG. The Beacon Chain coordinates validators, while the fork-choice rule (LMD-GHOST) ensures the chain follows the heaviest accumulated validator votes. Validators earn rewards for proposing and verifying blocks, but face slashing for malicious behaviour or inactivity. PoS aims to improve energy efficiency, security, and scalability, with future upgrades like Proto-Danksharding enhancing transaction efficiency. The following applies to BNB Smart Chain: BNB Smart Chain uses a hybrid consensus mechanism called Proof of Staked Authority (PoSA), which combines elements of Delegated Proof of Stake (DPoS) and Proof of Authority (PoA). This method ensures fast block times and low fees while maintaining a level of decentralization and security. Validators are responsible for producing new blocks, validating transactions, and maintaining network security. To become a validator, an entity must run a validator node and stake a significant amount of BNB. On a daily basis, the 45 validators with the highest stake and delegation are selected as active validators. Every epoch (240 blocks, approximately 20 minutes), 21 consensus validators are picked from the active set to take turns producing blocks. Token holders who do not wish to run a validator node can delegate their BNB to validators, earning a share of rewards and improving their chosen validator's selection chances. Inactive validators remain in a pool, ensuring a sufficient number of nodes are ready to take on validation tasks. BNB Smart Chain achieves block times of around 0.75 seconds. Validators are required to stake BNB as collateral, which can be slashed for malicious behaviour. Delegators earn rewards proportional to their stake, and transaction fees are paid in BNB. |
|||
| S.5 Incentive mechanisms and applicable fees | text | The following applies to Ethereum: Ethereum's PoS system secures transactions through validator incentives and economic penalties. Validators stake at least 32 ETH and earn rewards for proposing blocks, attesting to valid ones, and participating in sync committees. Rewards are paid in newly issued ETH and transaction fees. Under EIP-1559, transaction fees consist of a base fee, which is burned to reduce supply, and an optional priority fee (tip) paid to validators. Validators face slashing if they act maliciously and incur penalties for inactivity. This system aims to increase security by aligning incentives while making the fee structure more predictable and deflationary during high network activity. The following applies to BNB Smart Chain: BNB Smart Chain uses the Proof of Staked Authority (PoSA) consensus mechanism to ensure network security and incentivize participation from validators and delegators. Validators must stake a significant amount of BNB to participate in the consensus process. They earn rewards in the form of transaction fees when they produce blocks. On a daily basis, active validators are selected based on the amount of BNB staked and delegated to them. Token holders can delegate their BNB to validators, increasing the validator's total stake and improving their selection chances. Delegators earn a portion of the rewards that validators receive. Validators can be penalized for malicious behaviour or failure to perform their duties, including slashing of a portion of their staked tokens. Transaction fees on BNB Smart Chain are paid in BNB and are designed to remain low compared to other blockchain networks. On the underlying network (Ethereum), transaction ordering and finality are provided by Ethereum's Proof-of-Stake consensus (Gasper: LMD-GHOST fork choice + Casper FFG finality). Validators participate by staking ETH and performing block proposal/attestation duties; the execution of token transfers occurs on the EVM execution layer and is secured by the PoS consensus layer. |
|||
| S.6 Beginning of period to which disclosed information relates | date | ||||
| S.7 End of period to which disclosed information relates | date | ||||
| Mandatory key indicator | |||||
| S.8 Energy consumption | energy (kWh) | ||||
| Sources and methodologies | |||||
| S.9 Energy consumption sources and methodologies | textBlock | The following applies to BNB Chain: For the calculation of energy consumption, the so-called 'bottom-up' approach is being used. The nodes are considered to be the central factor for the energy consumption of the network. These assumptions are made on the basis of empirical findings through the use of public information sites, open-source crawlers and crawlers developed in-house. The main determinants for estimating the hardware used within the network are the requirements for operating the client software. The energy consumption of the hardware devices was measured in certified test laboratories. When calculating the energy consumption, the Functionally Fungible Group Digital Token Identifier (FFG DTI) is used to determine all implementations of the asset in scope. The mappings are updated regularly, based on data of the Digital Token Identifier Foundation. The information regarding the hardware used and the number of participants in the network is based on assumptions that are verified with best effort using empirical data. In general, participants are assumed to be largely economically rational. As a precautionary principle, assumptions are made on the conservative side when in doubt, i.e. making higher estimates for the adverse impacts. Source: FFG 8N2VXJKB1, reporting period 2024-06-30 to 2025-06-30. Where the reporting template requires a single numerical value, the values reported in S.6 to S.14 relate to the Ethereum mainnet, on which the token is natively issued, and to the reporting period of the Ethereum source stated above. The corresponding energy consumption of the BNB Smart Chain, for the reporting period of the BNB source stated above, is 90,228.00000 kWh/a. |
|||
| Supplementary information on principal adverse impacts on climate and other environment-related adverse impacts of consensus mechanism | |||||
| Supplementary key indicators | |||||
| S.10 Renewable energy consumption | percent | ||||
| S.11 Energy intensity | energy (kWh) | ||||
| S.12 Scope 1 DLT GHG emissions - controlled | GHG emissions (tCO2e) | ||||
| S.13 Scope 2 DLT GHG emissions - purchased | GHG emissions (tCO2e) | ||||
| S.14 GHG intensity | GHG emissions (tCO2e) | ||||
| Sources and methodologies | |||||
| S.15 Key energy sources and methodologies | textBlock | The following applies to BNB Chain: To determine the proportion of renewable energy usage, the locations of the nodes are to be determined using public information sites, open-source crawlers and crawlers developed in-house. If no information is available on the geographic distribution of the nodes, reference networks are used which are comparable in terms of their incentivization structure and consensus mechanism. This geo-information is merged with public information from Our World in Data, see citation. The intensity is calculated as the marginal energy cost with respect to one more 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]. Ember, "Yearly Electricity Data Europe"; Ember, "Yearly Electricity Data"; Energy Institute, "Statistical Review of World Energy" [original data]. Retrieved from https://ourworldindata.org/grapher/share-electricity-renewables. Source: FFG 8N2VXJKB1, reporting period 2024-06-30 to 2025-06-30. |
|||
| S.16 Key GHG sources and methodologies | textBlock | The following applies to BNB Chain: To determine the GHG emissions, the locations of the nodes are to be determined using public information sites, open-source crawlers and crawlers developed in-house. If no information is available on the geographic distribution of the nodes, reference networks are used which are comparable in terms of their incentivization structure and consensus mechanism. This geo-information is merged with public information from Our World in Data, see citation. The intensity is calculated as the marginal emission with respect to one more 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]. Ember, "Yearly Electricity Data Europe"; Ember, "Yearly Electricity Data"; Energy Institute, "Statistical Review of World Energy" [original data]. Retrieved from https://ourworldindata.org/grapher/carbon-intensity-electricity. Licenced under CC BY 4.0. Scope 1 emissions are reported as zero, as Proof-of-Staked-Authority validation does not involve direct combustion or controlled emission sources. Source: FFG 8N2VXJKB1, reporting period 2024-06-30 to 2025-06-30. |
|||
| Optional information on principal adverse impacts on the climate and on other environment-related adverse impacts of the consensus mechanism | |||||
| Optional indicators | |||||
| S. 17 Energy mix | percent | ||||
| S.18 Energy use reduction | |||||
| Energy use reduction target (absolute value) | energy (kWh) | ||||
| Energy use reduction target (percentage) | percent | ||||
| S.19 Carbon intensity (kgCO2e/kWh) | decimal | ||||
| S.20 Scope 3 DLT GHG emissions - value chain | GHG emissions (tCO2e) | ||||
| S.21 GHG emissions reduction targets or commitments | textBlock | ||||
| S.22 Generation of waste electrical and electronic equipment (WEEE) | mass (tonnes) | ||||
| S.23 Non-recycled WEEE ratio | percent | ||||
| S.24 Generation of hazardous waste | mass (tonnes) | ||||
| S.25 Generation of waste (all types) | mass (tonnes) | ||||
| S.26 Non-recycled waste ratio (all types) | percent | ||||
| S.27 Waste intensity (all types) | mass (tonnes) | ||||
| S.28 Waste reduction targets or commitments (all types) | textBlock | ||||
| S.29 Impact of use of equipment on natural resources | textBlock | ||||
| S.30 Natural resources use reduction targets or commitments | textBlock | ||||
| S.31 Water use | volume (m3) | ||||
| S.32 Non recycled water ratio | percent | ||||
| Sources and methodologies | |||||
| S.33 Other energy sources and methodologies | textBlock | ||||
| S.34 Other GHG sources and methodologies | textBlock | ||||
| S.35 Waste sources and methodologies | textBlock | ||||
| S.36 Natural resources sources and methodologies | textBlock | ||||