| [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 $TRIA token is intended to function as a utility and governance crypto-asset. Its primary purpose is to enable access to, and interaction with, specific features and services of the TRIA application. The token is not designed to represent money, legal tender, electronic money, or a claim on any reference asset. It is also not intended to function as a general-purpose means of payment outside the TRIA ecosystem. Subject to the technical design of the protocol and applicable terms, holders of $TRIA tokens may be entitled to the following functional rights within the TRIA ecosystem: - Access and Usage Rights: $TRIA tokens may be used to pay for protocol-related services, including but not limited to BestPath routing fees, SDK access, and subscription-based services. - Fee Reduction Rights: Users who stake $TRIA tokens may become eligible for reduced platform fees, subject to the applicable staking conditions. - Governance Participation: Holders of $TRIA tokens may participate in governance processes related to the development, configuration, and evolution of the TRIA protocol, including voting on certain proposals, parameters, or feature prioritization. The exercise of these rights is subject to the technical rules of the protocol, smart-contract logic, and any applicable eligibility requirements. The acquisition or holding of $TRIA tokens does not confer any ownership interest, equity stake, profit-sharing right, dividend entitlement, or claim against the issuer or any affiliated entity. Token holders are not entitled to repayment, redemption, or guaranteed returns. Token holders are responsible for complying with applicable laws and regulations in their respective jurisdictions, including tax and reporting obligations. The value of $TRIA tokens may fluctuate and is not guaranteed. The characteristics, utilities, and functional rights associated with the $TRIA token may evolve over time as the TRIA protocol develops. Changes may occur through governance decisions, protocol upgrades, or technical modifications, provided such changes are implemented in accordance with the protocol's governance framework and applicable legal requirements. No assurance is given that all current or planned functionalities will be maintained indefinitely, and token holders should consider the possibility of modifications when acquiring or using $TRIA tokens. |
|||
| 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 | Suite 5 Oleander Building, Port Purcell Tortola |
|||
| Country | enumeration | ||||
| Sub-division | text | ||||
| A.4 Head office | |||||
| Head office | text | Suite 5 Oleander Building, Port Purcell Tortola |
|||
| Country | enumeration | ||||
| Sub-division | text | ||||
| A.5 Registration date | date | ||||
| A.6 Legal entity identifier | LEI | ||||
| A.7 Another identifier required pursuant to applicable national law | text | ||||
| A.8 Contact telephone number | text | ||||
| A.9 E-mail address | text | ||||
| A.10 Response time (days) | integer | ||||
| A.11 Parent company | text | |
|||
| A.12 Members of the management body | |||||
| Member #1 | id | 1 | |||
| Identity | text | ||||
| Business address | text | |
|||
| Function | text | ||||
| A.13 Business activity | textBlock | ||||
| A.14 Parent company business activity | textBlock | ||||
| A.15 Newly established | boolean | ||||
| A.16 Financial condition for the past three years | textBlock | ||||
| A.17 Financial condition since registration | textBlock | The offeror has not engaged in lending, borrowing, or any form of external financing, nor has it issued debt instruments or entered into credit arrangements. Its operations to date have been funded exclusively through internal resources made available at the time of establishment. As of the latest reporting period, the offeror's available budget amounts to approximately USD 300,000. These resources are allocated to operational expenses related to software development, security audits, regulatory and compliance needs, partnership coordination, and administrative functions necessary for the maintenance of the $TRIA token framework. |
|||
| Part B - Information about issuer, if different from offeror or person seeking admission to trading | |||||
| B.1 Issuer different from offerror or person seeking admission to trading | boolean | ||||
| B.2 Name | N/A | . | |||
| B.3 Legal form | N/A | . | |||
| B.4 Registered address | |||||
| Registered addess | N/A | . | |||
| Country | N/A | . | |||
| Sub-division | N/A | . | |||
| B.5 Head office | |||||
| Head office | N/A | . | |||
| Country | N/A | . | |||
| Sub-division | N/A | . | |||
| B.6 Registration date | N/A | . | |||
| B.7 Legal entity identifier | N/A | . | |||
| B.8 Another identifier required pursuant to applicable national law | N/A | . | |||
| B.9 Parent company | N/A | . | |||
| B.10 Members of the management body | |||||
| Member #1 | N/A | . | |||
| Identity | N/A | . | |||
| Business address | N/A | . | |||
| Function | N/A | . | |||
| B.11 Business activity | N/A | . | |||
| B.12 Parent company business activity | N/A | . | |||
| Part C - Information about the operator of the trading platform in cases where it draws up the crypto-asset white paper and information about other persons drawing the crypto-asset white paper pursuant to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | |||||
| C.1 Name | N/A | . | |||
| C.2 Legal form | N/A | . | |||
| C.3 Registered address | |||||
| Registered address | N/A | . | |||
| Country | N/A | . | |||
| Sub-division | N/A | . | |||
| C.4 Head office | |||||
| Head office | N/A | . | |||
| Country | N/A | . | |||
| Sub-division | N/A | . | |||
| C.5 Registration date | N/A | . | |||
| C.6 Legal entity identifier | N/A | . | |||
| C.7 Another identifier required pursuant to applicable national law | N/A | . | |||
| C.8 Parent company | N/A | . | |||
| C.9 Reason for crypto-asset white paper preparation | N/A | . | |||
| C.10 Members of the management body | |||||
| Member #1 | N/A | . | |||
| Identity | N/A | . | |||
| Business address | N/A | . | |||
| Function | N/A | . | |||
| C.11 Operator business activity | N/A | . | |||
| C.12 Parent company business activity | N/A | . | |||
| C.13 Other persons drawing up the crypto-asset white paper according to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | N/A | . | |||
| C.14 Reason for drawing the white paper by persons referred to in Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | N/A | . | |||
| Part D - Information about other token project | |||||
| D.1 Crypto-asset project name | text | ||||
| D.2 Crypto-asset name | text | ||||
| D.3 Abbreviation | text | ||||
| D.4 Crypto-asset project description | textBlock | The TRIA application supports interoperability across multiple blockchains and virtual machines, allowing users to interact with a wide range of crypto-assets without being limited to a single network. The platform is designed to support the spending of a large number of tokens, execution of DeFi transactions, and cross-border remittances with near-real-time settlement. The $TRIA token underpins the operation of the ecosystem by enabling access to protocol services, staking mechanisms, liquidity support, and governance participation. The project's objective is to provide a unified technical framework that connects multiple blockchains and financial functionalities within a single application, while maintaining a non-custodial and interoperable design. |
|||
| 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 | New Castle County Delaware, 19808 |
|||
| 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 | Past Milestones To date, the TRIA project has completed several foundational milestones relevant to the role and planned use of the $TRIA token, including: - Completion of pre-seed and strategic funding rounds, raising approximately USD 12 million, followed by an additional USD 2 million fundraise through Legion, supporting early-stage development and infrastructure build-out. - Design and development of the core non-custodial architecture of the TRIA application. - Development of cross-chain interoperability mechanisms enabling interaction across multiple blockchains and virtual machines. - Initial implementation of the BestPath routing framework and core protocol components. - Design of the $TRIA token's utility framework, including payments, fee reductions, and governance participation. - These milestones have established the technical and operational foundation necessary for the deployment and functional use of the $TRIA token within the ecosystem. |
|||
| Description of future milestones | textBlock | - Progressive enablement of $TRIA token use for protocol-related payments, including BestPath fees, SDK access, and subscription services within the TRIA application. - Implementation and refinement of staking mechanisms for users and network participants, including eligibility for reduced platform fees and participation in protocol operations. - Gradual rollout of governance functionality allowing $TRIA token holders to participate in decision-making processes related to protocol configuration, feature prioritization, and strategic parameters. - Ecosystem Expansion: Integration of additional blockchains, virtual machines, and third-party services, increasing the scope of the TRIA ecosystem in which $TRIA tokens may be utilized. |
|||
| D.9 Resource allocation | text | ||||
| 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 | |
|||
| 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 | |
|||
| E.39 Applicable law | textBlock | ||||
| E.40 Competent court | textBlock | ||||
| Part F - Information about other tokens | |||||
| F.1 Crypto-asset type | text | The value of the crypto-asset is entirely determined by market forces – specifically, the dynamics of supply and demand – and is not supported by any stabilization mechanism. It is neither pegged to a fiat currency nor backed by external assets, which differentiates it from EMTs and ARTs. Moreover, the crypto-asset does not qualify as a financial instrument, deposit, insurance policy, pension product, or any other regulated financial product under EU law. It does not confer any financial entitlements contractual claims on its holders, thereby placing it outside the regulatory scope governing traditional financial instruments. |
|||
| F.2 Other token functionality | textBlock | The $TRIA token further enables participation in governance processes related to the TRIA protocol. Token holders may be entitled to submit proposals or vote on certain matters concerning protocol configuration, feature development, fee parameters, or other strategic aspects of the ecosystem, in accordance with the applicable governance framework. The functionality of the $TRIA token is limited to its use within the TRIA ecosystem as described above. The token is not intended to represent money, electronic money, or a claim on any reference asset, nor is it designed to function as a general-purpose means of payment outside the TRIA application. The specific functionalities of the $TRIA token may evolve over time as the TRIA protocol develops, subject to governance decisions, technical upgrades, and applicable legal or regulatory requirements. |
|||
| F.3 Planned application of functionalities | textBlock | ||||
| A description of the characteristics of the other token, including the data necessary for classification of the crypto-asset white paper in the register referred to in Article 109 of Regulation (EU) 2023/1114, as specified in accordance with paragraph 8 of that Article | |||||
| F.4 Type of crypto-asset white paper | enumeration | ||||
| F.5 Type of submission | enumeration | ||||
| F.6 Other token characteristics | textBlock | ||||
| F.7 Commercial name or trading name | text | ||||
| F.8 Website of the issuer | text | ||||
| F.9 Starting date of offer to the public or admission to trading | date | ||||
| F.10 Publication date | date | ||||
| F.11 Any other services provided by the issuer | textBlock | ||||
| F.12 Language or languages of white paper | text | ||||
| F.13 Digital token identifier code used to uniquely identify the crypto-asset or each of the several crypto assets to which the white paper relates, where available | text | ||||
| F.14 Functionally fungible group digital token identifier, where available | text | ||||
| F.15 Voluntary data flag | boolean | ||||
| F.16 Personal data flag | boolean | ||||
| F.17 LEI eligibility | boolean | ||||
| F.18 Home member state | enumeration | ||||
| F.19 Host member states #1 | enumerationSet | ||||
| F.19 Host member states #2 | enumerationSet | ||||
| F.19 Host member states #3 | enumerationSet | ||||
| F.19 Host member states #4 | enumerationSet | ||||
| F.19 Host member states #5 | enumerationSet | ||||
| F.19 Host member states #6 | enumerationSet | ||||
| F.19 Host member states #7 | enumerationSet | ||||
| F.19 Host member states #8 | enumerationSet | ||||
| F.19 Host member states #9 | enumerationSet | ||||
| F.19 Host member states #10 | enumerationSet | ||||
| F.19 Host member states #11 | enumerationSet | ||||
| F.19 Host member states #12 | enumerationSet | ||||
| F.19 Host member states #13 | enumerationSet | ||||
| F.19 Host member states #14 | enumerationSet | ||||
| F.19 Host member states #15 | enumerationSet | ||||
| F.19 Host member states #16 | enumerationSet | ||||
| F.19 Host member states #17 | enumerationSet | ||||
| F.19 Host member states #18 | enumerationSet | ||||
| F.19 Host member states #19 | enumerationSet | ||||
| F.19 Host member states #20 | enumerationSet | ||||
| F.19 Host member states #21 | enumerationSet | ||||
| F.19 Host member states #22 | enumerationSet | ||||
| F.19 Host member states #23 | enumerationSet | ||||
| F.19 Host member states #24 | enumerationSet | ||||
| F.19 Host member states #25 | enumerationSet | ||||
| F.19 Host member states #26 | enumerationSet | ||||
| F.19 Host member states #27 | enumerationSet | ||||
| F.19 Host member states #28 | enumerationSet | ||||
| F.19 Host member states #29 | enumerationSet | ||||
| F.19 Host member states #30 | enumerationSet | ||||
| Part G - Information on rights and obligations attached to other tokens | |||||
| G.1 Purchaser rights and obligations | textBlock | TRIA holders retain full control and ownership of their tokens, which are freely transferable on the Ethereum network in accordance with the ERC-20 token standard. Ownership of TRIA does not confer any rights of equity, profit-sharing, debt, or repayment in Tria Labs Limited nor in any affiliated entity. |
|||
| 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 underlying technology | |||||
| H.1 Distributed ledger technology (DTL) | text | ||||
| H.2 Protocols and technical standards | text | Smart contracts within the TRIA ecosystem are developed using industry-standard programming languages and frameworks appropriate to the supported blockchains. Cross-chain functionality and interoperability are achieved through protocol-level integrations and routing mechanisms designed to facilitate interaction between different blockchain networks. Where applicable, the TRIA application integrates with external payment and infrastructure providers using standardized APIs and technical interfaces, in accordance with applicable technical and compliance requirements. |
|||
| H.3 Technology used | textBlock | The TRIA application is designed to operate in a non-custodial manner, meaning that users retain control over their private keys and digital assets. Certain processes, such as transaction routing, analytics, and service coordination, may rely on off-chain systems, while asset custody and settlement occur on-chain. |
|||
| H.4 Consensus mechanism | text | ||||
| H.5 Incentive mechanisms and applicable fees | text | ||||
| H.6 Use of distributed ledger technology | boolean | ||||
| H.7 DLT functionality description | textBlock | ||||
| Other token audit details | |||||
| H.8 Audit | boolean | ||||
| H.9 Audit outcome | textBlock | ||||
| Part I - Information on risks | |||||
| I.1 Offer-related risks | textBlock | ||||
| I.2 Issuer-related risks | textBlock | ||||
| I.3 Other tokens-related risks | textBlock | ||||
| I.4 Project implementation-related risks | textBlock | ||||
| I.5 Technology-related risks | textBlock | ||||
| I.6 Mitigation measures | textBlock | a) A dedicated team of experts evaluates risk exposures, asset allocations, and protocol parameters to ensure prudent management. b) Transparent Governance: All major protocol and token-related decisions are made through community governance, supported by public documentation and auditable voting records. c) Entity Stewardship: Entities surrounding the TRIA protocol provide strategic guidance and ensures the project's adherence to sustainability and compliance standards. Technical Security. a) Independent Smart Contract Audits: All smart contracts are subjected to multiple third-party security audits prior to deployment and after major upgrades. b) Bug Bounty Programs: Continuous bounty initiatives incentivize community reporting of vulnerabilities. c) Use of trusted industry service providerr for key management and 3rd party infrastructures. Operational Resilience. a) Infrastructure Diversification: Multiple RPC providers, storage networks, and validator partners are employed to reduce reliance on any single provider. b) Incident Response Procedures: A structured monitoring and response framework enables rapid detection, containment, and resolution of potential security or operational incidents. c) Periodic Stress Testing: Protocol systems undergo regular performance and load testing to evaluate resilience under adverse conditions. Regulatory and Compliance Measures. a) Regulatory Monitoring: The issuer and foundation actively monitor evolving EU and international regulations, including MiCAR developments, to ensure continuous compliance. b) Legal Reviews: Ongoing external legal assessments help ensure that token operations remain consistent with applicable laws and regulatory classifications. Market and Financial Controls. a) Treasury Management Policies: Treasury operations follow internal governance controls to ensure transparent use of funds and responsible liquidity management. b) Diversification of Assets: The treasury maintains a balanced composition of TRIA and stablecoins to maintain liquidity. Community and Transparency. a) Clear Documentation: documentation and informative materials are publicly accessible, enabling independent review. b) Continuous Communication: Regular updates through governance forums, community calls, and transparency reports ensure ongoing stakeholder engagement. |
|||
| 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 | ||||
| S.5 Incentive mechanisms and applicable fees | text | ||||
| S.6 Beginning of period to which disclosed information relates | date | ||||
| S.7 End of period to which disclosed information relates | date | ||||
| Mandatory key indicator | |||||
| S.8 Energy consumption | energy (kWh) | ||||
| Sources and methodologies | |||||
| S.9 Energy consumption sources and methodologies | textBlock | |
|||
| 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 | https://ethereum.org/energy-consumption/. |
|||
| S.16 Key GHG sources and methodologies | textBlock | https://ethereum.org/energy-consumption/. |
|||
| 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 | ||||