| N | Field | Content |
|---|---|---|
| 00 | Table of contents |
General Information |
| 01 | Date of notification |
2026-05-29 |
| 02 | Statement in accordance with Article 6(3) of Regulation (EU) 2023/1114 |
This crypto-asset white paper has not been approved by any competent authority in any Member State of the European Union. |
| 03 | Compliance statement in accordance with Article 6(6) of Regulation (EU) 2023/1114 |
This crypto-asset white paper complies with Title II of Regulation (EU) 2023/1114 of the European Parliament and of the Council and, to the best of the knowledge of the management body, the information presented in the crypto-asset white paper is fair, clear and not misleading and the crypto-asset white paper makes no omission likely to affect its import. |
| 04 | Statement in accordance with Article 6(5), points (a), (b), (c), of Regulation (EU) 2023/1114 |
The crypto-asset referred to in this crypto-asset white paper may lose its value in part or in full, may not always be transferable and may not be liquid. |
| 05 | Statement in accordance with Article 6(5), point (d), of Regulation (EU) 2023/1114 |
FALSE |
| 06 | Statement in accordance with Article 6(5), points (e) and (f), of Regulation (EU) 2023/1114 |
The crypto-asset referred to in this white paper is not covered by the investor compensation schemes under Directive 97/9/EC of the European Parliament and of the Council or the deposit guarantee schemes under Directive 2014/49/EU of the European Parliament and of the Council. |
| 07 | Warning in accordance with Article 6(7), second subparagraph, of Regulation (EU) 2023/1114 |
Warning |
| 08 | Characteristics of the crypto-asset |
Frankencoin (ZCHF) is a crypto-asset without an identifiable issuer, thereby excluded from the scope of Title II, III or IV of the MiCA Regulation by Recital 22. ZCHF is used within the Frankencoin Protocol. ZCHF operates as an ERC-20 token on Ethereum Mainnet and is implemented through a decentralised collateralised debt position mechanism. Under this structure, users deposit eligible crypto-assets as collateral in order to mint ZCHF, subject to protocol-defined collateralisation requirements. The system is overcollateralised and operates through transparent smart-contract rules governing issuance, repayment, and liquidation. These mechanisms do not constitute a guarantee of value, do not provide holders with a contractual right of redemption at par against an issuer. As a result of the above mechanisms, there are decentralised economic incentives that make it economically attractive to repay debt positions and recover collateral if ZCHF trades below CHF parity, or to mint more ZCHF if it trades above CHF parity. While this could suggest the asset references an official currency in the sense of MiCA Article 3(1)(7), the definition of “electronic money” in article 2(2) of Directive 2009/110/EC, as established in article 4(25) of Directive 2015/2366 and article 2(4)((C) of the MiCA Regulation, defines electronic money as claims against issuers. Therefore, we interpret that ZCHF’s lack of identifiable issuer, absence of claims against any parties and nonexistence of redemption mechanics, makes ZCHF a “crypto-asset other than asset-referenced tokens and e-money tokens”. Irrespective, the question of the asset’s classification is superfluous as the asset is excluded from the application of Titles II, III and IV of MiCA due to the recital 22 provisions for assets without an identifiable issuer |
| 09 |
Not applicable as 05 is false |
|
| 10 | Key information about the offer to the public or admission to trading |
As an asset without an identifiable issuer, ZCHF is excluded by MiCA’s recital 22 from the application of Titles II, III and IV and the admission to trading requirements regulated therein, inclusive of white paper requirements. However, in order to support crypto-asset trading platforms in streamlining their admission to trading processes, and to reduce the operational burden and compliance costs associated to listing processes, MiCA Crypto Alliance OpCo Limited is voluntarily submitting a white paper for ZCHF as a best practice despite the inapplicability of the requirement. In this context, this white paper is specifically targeted for admission to trading to the Kraken trading platform. |
| N | Field | Content | ||||||
|---|---|---|---|---|---|---|---|---|
| A.1 | Name |
MiCA Crypto Alliance Opco Limited |
||||||
| A.2 | Legal form |
N/A as LEI is provided in A.6 |
||||||
| A.3 | Registered address |
N/A as LEI is provided in A.6 |
||||||
| A.4 | Head office |
N/A as LEI is provided in A.6 |
||||||
| A.5 | Registration date |
2025-11-19 |
||||||
| A.6 | Legal entity identifier |
984500CEB5773O38LE40 |
||||||
| A.7 | Another identifier required pursuant to applicable national law |
N/A as LEI is provided in A.6 |
||||||
| A.8 | Contact telephone number |
+44(7441)903166 |
||||||
| A.9 | E-mail address |
submissions@micaalliance.com |
||||||
| A.10 | Response time (Days) |
|
||||||
| A.11 | Parent company |
N/A as LEI is provided in A.6 |
||||||
| A.12 | Members of the management body |
|
||||||
| A.13 | Business activity |
Preparation and submission white papers under the EU Markets in Crypto Assets Regulation. |
||||||
| A.14 | Parent company business activity |
The main object of the company is to own, manage and administer property of any kind whether belonging to the company or not. The secondary object of the company is to hold shares and, or equity in other companies. |
||||||
| A.15 | Newly established |
TRUE |
||||||
| A.16 | Financial condition for the past three years |
Not applicable |
||||||
| A.17 | Financial condition since registration |
The entity was incorporated in November 2025 in Malta and therefore does have a limited financial history. Since incorporation, the entity’s financial condition is developing in line with the scaling of its operational activities in the MiCA-related activity and technology services sector. The entity is generating revenue from MiCA white paper preparation, ESG data disclosures, XBRL reporting services, and related MiCA support for CASPs and blockchain-based projects. Since its establishment, the entity has maintained sufficient financial resources of USD 2,000,000 to support its ongoing operations and development activities. The development of the business has been driven by increasing demand for MiCA compliance services, including white paper drafting, ESG methodology development, and regulatory submission support. In addition, the entity has developed auxiliary tools and initiatives, including a white paper tracking tool aligned with the ESMA registry of notified MiCA white papers. This tool supports market transparency and ecosystem monitoring and has contributed to increased engagement with market participants and stakeholders, thereby indirectly supporting business development activities and client outreach within the MiCA compliance sector. This has resulted in a progressive increase in client engagements, drafting of more than 60 MiCA white papers, and expansion of ESG data analysis activities covering more than 1,200 token datasets. In addition, the entity has expanded its operational ecosystem through partnerships with legal, financial, and blockchain industry participants, supporting the scaling of its service offering and market presence. Given the recent incorporation date, historical financial information is limited. However, the entity’s financial position is currently supported by available capital resources and ongoing service activity, with no material adverse changes identified since establishment. |
| N | Field | Content |
|---|---|---|
| B.1 | Issuer different from offerror or person seeking admission to trading |
TRUE |
| B.2 | Name |
We were not able to identify a legal issuer for ZCHF. ZCHF is created through a decentralised protocol governed by over-collateralisation mechanisms, minting, repayment, and liquidation mechanisms. Substantively, field B.1 should correspond to “TRUE”. However, the MiCA XBRL taxonomy does not support this configuration and requires the completion of issuer-specific fields that are not applicable in this case. Accordingly, field B.1 is set to “FALSE” in the machine-readable version only, while the human-readable version reflects the absence of an identifiable issuer. |
| 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 |
Frankencoin |
||||||||
| D.2 | Crypto-asset name |
Not applicable as DTI is provided in F.13. |
||||||||
| D.3 | Abbreviation |
Not applicable as DTI is provided in F.13. |
||||||||
| D.4 | Crypto-asset project description |
Frankencoin is a decentralised protocol for the creation, use, and management of ZCHF. ZCHF is generated through a collateralised minting mechanism under which users may mint ZCHF against eligible collateral through smart contracts, subject to the applicable protocol rules. The primary use cases for ZCHF are payments, Swiss-franc-denominated transactions, store of wealth use cases and participation in collateralised minting mechanisms within the Frankencoin Protocol. The project operates through transparent smart-contract mechanisms, including collateralised positions, repayment, and liquidation processes. The protocol also includes governance arrangements involving Frankencoin Pool Shares (FPS), including veto-based governance for certain proposals relating to collateral types or other methods of bringing ZCHF into circulation, and saving rate adjustments. ZCHF tokens are created when users deposit eligible crypto-assets as collateral into smart contracts and mint ZCHF against such collateral, subject to predefined collateralisation requirements and applicable protocol parameters. The protocol operates on an over-collateralised basis and incorporates liquidation mechanisms intended to support market-based price stability in relation to the Swiss franc. Eligible collateral assets must satisfy the technical and operational requirements established by the Frankencoin Protocol and the applicable smart-contract parameters, as described in H.3. The initial collateral deposited when opening a position must be at least equal to the specified minimum collateral. A new position must start with at least 5,000 ZCHF worth of collateral. Challenges and auctions are supported in respect of collateralised positions, and the contract includes handling for cases where collateral cannot be returned to a challenger due to blacklist or transfer restrictions. In addition to enabling payments and storage of wealth through ZCHF, the Frankencoin Protocol offers a collateralised ZCHF minting mechanism that may be described as borrowing in exchange for an interest. A part of this interest is routed to ZCHF holders via a native savings mechanism through which holders may deposit tokens into the protocol's Savings module and earn a return denominated in ZCHF. |
||||||||
| D.5 | Details of all natural or legal persons involved in implementation of crypto-asset project |
|
||||||||
| D.6 | Utility Token Classification |
FALSE |
||||||||
| D.7 | Key Features of Goods/Services for Utility Token Projects |
Not applicable |
||||||||
| D.8 | Description of past milestones |
Past milestones Since 2023, Frankencoin has enabled on-chain Swiss-franc-denominated transactions. As at 4 May 2026, the public Frankencoin website states that Frankencoin has been deployed on eight different blockchains. By 2024, the Frankencoin project had published public explanatory materials concerning the Frankencoin Association, FPS, oracle-free design, decentralisation, and Swiss-franc-denominated on-chain use cases through its Substack publication. On 4 September 2025, ZCHF/USDT trading was scheduled to open on MEXC following an initial listing announcement published on 3 September 2025. On 23 September 2025, public social-media materials described an integration involving Frankencoin, Zeal Wallet, Gnosis Pay, and Mt Pelerin, including CHF/ZCHF on- and off-ramp functionality, yield access through Zeal, and card spending through Gnosis Pay. As at 2025 and 2026, the project’s GitHub discussions show continued governance and collateral-related activity, including proposals relating to collateral types, savings-module upgrades, and multichain infrastructure. Public GitHub discussions include a proposal for an upgraded savings module dated 22 May 2025, a multichain infrastructure proposal dated 23 June 2025, and collateral-related proposals dated 2025 and 2026. |
||||||||
| D.8 | Description of future milestones |
Future milestones As of 4 May 2026, public GitHub discussions show ongoing proposals and community activity relating to additional collateral types, liquidity infrastructure, multichain infrastructure, and savings-module upgrades. |
||||||||
| D.9 | Resource allocation |
No central allocation of proceeds from a public offer, issuer-controlled token sale, or centrally managed project budget has been identified for ZCHF. The Frankencoin Protocol allocates resources through smart-contract-based mechanisms, collateralised positions, and the Frankencoin reserve structure rather than through a central issuer allocation. The Frankencoin system includes ZCHF and FPS. FPS provide proportional exposure to the equity reserve pool of the Frankencoin system. The equity reserve pool is funded with ZCHF deposits made in order to obtain FPS in return, ZCHF fees paid to the protocol, and liquidation surpluses arising from challenged positions. FPS represent proportional ownership of the equity reserve pool. FPS holders whose accumulated voting weight reaches at least 2% of the total accumulated votes may veto governance proposals, including new minting module proposals, position proposals, and savings rate changes, as described in H.3. This pool has two purposes. First, a part of the reserve pool funds the savings module described in H.3, as determined by the savings rate. Second, the equity reserve pool is used to cover losses arising from liquidation events in which collateral value falls below the amount of ZCHF borrowed against it. FPS may be redeemed for ZCHF once the applicable 90-day holding period following minting has elapsed. |
||||||||
| D.10 | Planned use of Collected funds or crypto-Assets |
Not applicable |
| N | Field | Content |
|---|---|---|
| E.1 | Public offering or admission to trading | |
| E.2 | Reasons for public offer or admission to trading |
By admitting ZCHF to trading, holders may benefit from access to additional liquidity for buying and selling ZCHF. Admission to trading may support the ability of users, borrowers, liquidity providers, and other ecosystem participants to acquire or dispose of ZCHF through an organised trading venue, subject to market conditions, available order-book depth, applicable fees, and platform-specific access requirements |
| E.3 | Fundraising target | N/A |
| E.4 | Minimum subscription goals | N/A |
| E.5 | Maximum subscription goals | N/A |
| E.6 | Oversubscription acceptance | N/A |
| E.7 | Oversubscription allocation | N/A |
| E.8 | Issue price | N/A |
| E.9 | Official currency or any other crypto-assets determining the issue price | N/A |
| E.10 | Subscription fee | N/A |
| E.11 | Offer price determination method | N/A |
| E.12 | Total number of offered/traded crypto-assets |
The circulating supply of ZCHF follows a dynamic issuance mechanism, as tokens are minted and burned through a decentralised collateralised debt position system. For the purpose of complying with the technical requirements of the MiCA Regulation XBRL taxonomy, a circulating supply of 31101990.464631613 has been reflected as the number of tokens in the machine-readable version of the white paper. This figure emerges from https://api.frankencoin.com/ecosystem/coinmarketcap/totalsupply, as consulted on 11 May 2026 is indicative and may vary over time depending on the minting and burning activity of ZCHF tokens. |
| E.13 | Targeted holders | |
| E.14 | Holder restrictions | N/A |
| E.15 | Reimbursement notice | N/A |
| E.16 | Refund mechanism | N/A |
| E.17 | Refund timeline | N/A |
| E.18 | Offer phases | N/A |
| E.19 | Early purchase discount | N/A |
| E.20 | Time-limited offer | N/A |
| E.21 | Subscription period beginning | N/A |
| E.22 | Subscription period end | N/A |
| E.23 | Safeguarding arrangements for offered funds/crypto-Assets | N/A |
| E.24 | Payment methods for crypto-asset purchase | N/A |
| E.25 | Value transfer methods for reimbursement | N/A |
| E.26 | Right of withdrawal | N/A |
| E.27 | Transfer of purchased crypto-assets | N/A |
| E.28 | Transfer time schedule | N/A |
| E.29 | Purchaser's technical requirements | N/A |
| E.30 | Crypto-asset service provider (CASP) name | N/A |
| E.31 | CASP identifier | N/A |
| E.32 | Placement form | |
| E.33 | Trading platforms name |
Payward Global Solutions Limited (Kraken) |
| E.34 | Trading platforms Market identifier code (MIC) |
PGSL |
| E.35 | Trading platforms access |
Admission to trading of ZCHF is sought on Kraken. Subject to admission to trading, access to the trading platform would be available through Kraken’s web platform, mobile application, and, where supported, Kraken Pro. Users would be required to access the relevant Kraken portal, create or maintain an account, complete any applicable verification requirements, and comply with Kraken’s terms, supported jurisdiction requirements, fees, and applicable legal and regulatory restrictions. |
| E.36 | Involved costs |
The trading platforms where the admission to trading is sought do not involve any costs related to investors’ access. |
| E.37 | Offer expenses |
Not applicable |
| E.38 | Conflicts of interest |
Not applicable |
| E.39 | Applicable law |
Ireland |
| E.40 | Competent court |
Ireland |
| N | Field | Content |
|---|---|---|
| F.1 | Crypto-asset type |
Crypto-asset excluded from Titles II, III and IV of Regulation (EU) 2023/1114 due to the lack of an identifiable issuer, in accordance with the Regulation’s recital 22. |
| F.2 | Crypto-asset functionality |
ZCHF is a decentralised, overcollateralised crypto-asset issued within the Frankencoin protocol. Its primary functionalities are enabling payments and storing value, and decentralised, borrowing-like minting of ZCHF itself against crypto-asset collateral, and subsequent use of ZCHF for payments and value holding. ZCHF may be used for Swiss-franc-denominated payments through compatible applications and services, including payment applications, debit card integrations, IBAN-related integrations, wallets, bridges, and other third-party tools. The availability of such services depends on the relevant third-party provider, supported networks, and applicable legal and technical requirements. ZCHF may be acquired with fiat currency or other crypto-assets where supported by exchanges, decentralised trading venues, wallet providers, or other service providers. Such acquisition methods are external to the core protocol and may be subject to user eligibility, fees, liquidity, sanctions screening, anti-money laundering and counter-terrorist financing controls, and jurisdictional restrictions. ZCHF may be “borrowed” through the Frankencoin protocol by depositing eligible crypto-assets as collateral into collateralised positions. The owner of a position may deposit collateral and mint ZCHF up to the applicable limit defined by the relevant liquidation parameters. The Frankencoin protocol further includes collateralised minting and savings functionality implemented through protocol smart contracts. Users may mint ZCHF against eligible collateral in accordance with applicable protocol parameters, while holders of ZCHF may deposit ZCHF into protocol-supported savings mechanisms. Applicable savings and interest rates are determined through the protocol governance process and may be modified in accordance with the applicable governance procedures. Any yield or return generated through the savings mechanisms is variable, protocol-dependent and not guaranteed. Developers and businesses may integrate Frankencoin functionality into applications and financial services through the available developer resources and APIs, including access to protocol data relating to ZCHF, FPS, minter contracts, approved collateral types, positions, minting activity, transfers, and other ecosystem information. |
| F.3 | Planned application of functionalities |
Not applicable |
| F.4 | Type of crypto-asset white paper | |
| F.5 | The type of submission | |
| F.6 | Crypto-asset characteristics |
ZCHF is generated through an overcollateralisation mechanism whereby users lock eligible crypto-assets as collateral in smart contracts in order to mint new tokens. The protocol enforces collateralisation requirements and may trigger automated liquidation of positions that fall below predefined thresholds. The token is transferable on supported blockchain networks and can be used as a means of exchange or for value transfer between participants. Ownership of ZCHF is represented by control over cryptographic private keys associated with a blockchain address. ZCHF does not confer a claim against an identifiable issuer and does not provide a legally enforceable right of redemption at par value in Swiss francs. Its value is influenced by collateralisation mechanisms, protocol rules, and market conditions. Transactions involving ZCHF are executed and recorded on the underlying distributed ledger and are generally irreversible once confirmed. The functioning of the token relies on smart contracts that govern issuance, transfers, and collateral management. ZCHF is not covered by investor compensation schemes or deposit guarantee schemes. |
| F.7 | Commercial name or trading name |
Not applicable |
| F.8 | Website of the issuer |
Not applicable |
| F.9 | Starting date of offer to the public or admission to trading |
2026-06-27 |
| F.10 | Publication date |
2026-06-26 |
| F.11 | Any other services provided by the issuer |
Not applicable as there is no identifiable issuer. |
| F.12 | Language or languages of the crypto-asset white paper |
English |
| 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 |
1GS8GZGXV |
| F.14 | Functionally fungible group digital token identifier, where available |
2R50HSCVB |
| F.15 | Voluntary data flag |
FALSE |
| F.16 | Personal data flag |
TRUE |
| F.17 | LEI eligibility |
FALSE |
| F.18 | Home Member State | |
| F.19 | Host Member States |
| N | Field | Content |
|---|---|---|
| G.1 | Purchaser rights and obligations |
Not applicable as ZCHF does not confer any contractual, proprietary, or redemption rights against the issuer. ZCHF is issued against overcollateralised positions within the protocol. Positions may be unwound by repaying ZCHF, which results in the release of the underlying collateral. The value of ZCHF may be realised through such mechanisms or through transactions on secondary markets, subject to market conditions and liquidity. Holders are responsible for the secure management of their private keys. Loss or compromise of private keys may result in permanent loss of access to ZCHF. |
| G.2 | Exercise of rights and obligations |
Not applicable as the asset confers no ownership or financial claims and does not impose any legal obligations. |
| G.3 | Conditions for modifications of rights and obligations |
Not applicable as the asset confers no ownership or financial claims and does not impose any legal obligations. |
| G.4 | Future public offers |
Not applicable |
| G.5 | Issuer retained crypto-assets |
|
| G.6 | Utility Token Classification |
FALSE |
| G.7 | Key features of goods/services of utility tokens | N/A |
| G.8 | Utility tokens redemption | N/A |
| G.9 | Non-trading request |
FALSE |
| G.10 | Crypto-assets purchase or sale modalities |
Not applicable |
| G.11 | Crypto-assets transfer restrictions |
This admission to trading does not outline any restrictions on the transferability of the crypto-assets. |
| G.12 | Supply adjustment protocols |
TRUE |
| G.13 | Supply adjustment mechanisms |
The supply of ZCHF is adjusted mostly through an overcollateralised issuance and repayment mechanism within the Frankencoin protocol, and secondarily through swap mechanisms against other Swiss-franc-linked assets. ZCHF tokens are created when users deposit collateral into smart contracts and mint ZCHF against such collateral — subject to predefined collateralisation requirements —, or when other Swiss-franc-referencing digital assets are converted into ZCHF through 1:1 bridge or redemption mechanisms. Collateralisation requirements are defined through the protocol’s position mechanism rather than through a universal predefined list of eligible collateral assets or a minimum collateralisation percentage. As long as the technical criteria for acceptable collateral described in H.3 are met, participants may freely create ‘positions’ specifying the applicable issuance, collateral, liquidation, and other operational parameters (typically — though not necessarily in the case of 1:1 swap positions — including a collateral asset, liquidation price, minting cap, interest rate, and maturity date in the case of overcollateralised positions), which may then be challenged by other participants. A newly proposed position enters a governance veto window (the initialisation period) of at least 3 days, during which qualified FPS holders may permanently deny the position. If not denied, the position becomes active and the owner may mint ZCHF. Separately, any active position (or even a position still in its initialisation period) may be challenged at any time; the auction duration for any such challenge is a configurable parameter set by the position creator, ranging from minutes to up to two weeks depending on collateral liquidity , after which the position owner may deposit collateral into their position to mint ZCHF, or other users may clone the active position — creating their own cloned position inheriting the parent's parameters — to mint ZCHF immediately without a further initialisation period. ZCHF tokens are removed from circulation when users repay their outstanding positions, resulting in the burning of the repaid tokens. Positions may close once outstanding ZCHF has been repaid and collateral withdrawn, upon expiry of the position term, or through liquidation where collateral no longer satisfies the applicable collateralisation requirements. Where the market price of ZCHF deviates from its intended reference value, market participants may be incentivised to mint additional tokens or to repay and burn tokens, depending on prevailing market conditions. Liquidation mechanisms apply through a challenge-and-auction process open to any market participant who believes a position's collateral no longer adequately supports the outstanding ZCHF obligation. A challenger deposits an equivalent amount of the collateral and initiates an auction; if the auction result confirms the position is undercollateralised, the position is settled and the corresponding ZCHF is removed from circulation. This mechanism operates without external price oracles or automatic ratio-based triggers. As of the date of writing this white paper, the web page https://app.frankencoin.com/mint identifies the following active positions within the Frankencoin protocol to support minting of ZCHF against collateral: Boss Info AG, Coinbase Wrapped BTC, Curve DAO Token, Gnosis Token, Switzerland AG C1 Shares SHA, Liquid Staked ETH, Paxos Gold, RealUnit Shares, SPDR S&P 500 ETF (Ondo Tokenized), Wrapped BTC, Wrapped Ether, Wrapped liquid staked Ether 2.0, Tether Gold, and Staked yBOLD. In addition, there are 1:1 swap/redeem positions relating to Allunity Swiss Franc and VNX Franc. In other words, ZCHF may also be redeemed against two other Swiss-franc-referencing tokens without loan-to-value-based collateralisation mechanics. |
| G.14 | Token value protection schemes |
TRUE |
| G.15 | Token value protection schemes description |
The token value protection framework of Frankencoin coincides with the supply adjustment mechanisms described in G.13. As described above, the value of ZCHF is primarily supported by an overcollateralisation framework. ZCHF tokens are primarily issued through collateralised smart-contract positions, although the protocol also supports bridge-based issuance modules. While the protocol does not impose a universal overcollateralisation requirement, overcollateralisation is strongly incentivised as a position creator must put capital at risk to earn income from minting ZCHF against a position, and the capital is more likely to be lost through challenge, liquidation or bad debt if the position is insufficiently collateralised. Where the value of collateral falls below the required thresholds of each individual position, liquidation mechanisms may be applied to the relevant positions in order to maintain sufficient collateral backing. These liquidation mechanisms, together with reserve capital committed to absorb potential losses, position-specific minting limits and risk parameters defined for each position, and certain 1:1 swap or redemption arrangements relating to other Swiss-franc-referencing assets, form part of the value protection framework for ZCHF. |
| G.16 | Compensation schemes |
FALSE |
| G.17 | Compensation schemes description | N/A |
| G.18 | Applicable law |
There is no written legal agreement governing the legal rights or obligations associated with holding the crypto-asset between token-holders and an identifiable issuer. In a context where an identifiable issuer cannot be established, no identifiable issuer can be designated as entering into a contractual relationship with token-holders in relation to the crypto-asset. Accordingly, no single governing law or competent jurisdiction can be predetermined for disputes relating specifically to the crypto-asset itself. The determination of applicable law and jurisdiction would instead depend on the nature of the specific legal relationship in question, including any involvement of identifiable third parties such as crypto-asset service providers, project developers, or the asset interface operators. Such determination would be made in accordance with applicable private international law rules and mandatory legal provisions, including consumer protection rules where relevant. |
| G.19 | Competent court |
There is no written legal agreement governing the legal rights or obligations associated with holding the crypto-asset between token-holders and an identifiable issuer. In a context where an identifiable issuer cannot be established, no identifiable issuer can be designated as entering into a contractual relationship with token-holders in relation to the crypto-asset. Accordingly, no single governing law or competent jurisdiction can be predetermined for disputes relating specifically to the crypto-asset itself. The determination of applicable law and jurisdiction would instead depend on the nature of the specific legal relationship in question, including any involvement of identifiable third parties such as crypto-asset service providers, project developers, or the asset interface operators. Such determination would be made in accordance with applicable private international law rules and mandatory legal provisions, including consumer protection rules where relevant. |
| N | Field | Content |
|---|---|---|
| H.1 | Distributed ledger technology |
Not applicable as DTI is provided in F.13 |
| H.2 | Protocols and technical standards |
Networking The Frankencoin protocol operates on the Ethereum mainnet and interfaces with clients through standard Ethereum JSON-RPC. Users interact with the system directly through compatible wallets and the official web application at https://app.frankencoin.com. Transaction submission, state queries and contract interactions all follow the Ethereum application interface standard. ZCHF is also deployed on Polygon, Arbitrum, Optimism, Base, Avalanche, Gnosis and Sonic through the cross-chain transfer module, with the same contract address 0xD4dD9e2F021BB459D5A5f6c24C12fE09c5D45553 on each of those networks. Serialisation Transactions follow the Ethereum transaction format, including EIP-1559 fee market transactions. Smart contract interactions use ABI-encoded calldata consistent with the Ethereum ABI specification. The ZCHF contract implements ERC-20 (EIP-20) for token transfer and approval. The FPS contract additionally implements vote accumulation logic through a time-weighted holdings mechanism recorded on-chain. Cryptography and key formats Accounts on Ethereum use secp256k1 key pairs with Keccak-256 address derivation. ZCHF ownership is represented by control over a private key associated with an Ethereum address. The token contracts use standard Solidity constructs, and all core deployed contracts are immutable, meaning once deployed, they cannot be altered. Ledger ZCHF is maintained as an ERC-20 token on Ethereum mainnet at contract address 0xB58E61C3098d85632Df34EecfB899A1Ed80921cB. The associated governance token, FPS, is deployed at 0x1bA26788dfDe592fec8bcB0Eaff472a42BE341B2. Both contracts are deployed on the Ethereum mainnet, and their state, including balances, minting permissions, reserve holdings and vote accumulation, forms part of the Ethereum state, committed to the Ethereum blockchain through normal Ethereum block production. Token standards ZCHF implements the ERC-20 standard. FPS implements ERC-20 with additional governance logic: vote weight is calculated by multiplying an address's FPS balance by the duration for which those tokens have been continuously held, rewarding long-term participation and making flash-loan-based governance attacks ineffective. Any address with at least 2 per cent of total accumulated votes may exercise a veto on pending governance proposals in a single transaction. Cross-chain transfer ZCHF can be transferred between Ethereum mainnet and the supported networks through the Chainlink Cross-Chain Interoperability Protocol (CCIP) bridge, audited by ChainSecurity. The CCIP bridge maintains synchronisation of token supply and state between chains. Vote accumulation for governance purposes is anchored exclusively on Ethereum mainnet; FPS holders may synchronise their vote count to other chains using the built-in sync function in order to exercise veto rights on those chains. |
| H.3 | Technology used |
Architecture The Frankencoin system consists of a set of immutable smart contracts on Ethereum mainnet. The ZCHF and FPS token contracts serve as the foundation. ZCHF has a modular minting architecture in which any proposed smart contract that survives the FPS holder veto period may be granted the minter role, enabling them to mint and burn ZCHF without restriction from the token contract itself, subject only to the logic encoded in each module. The approved minting modules in the system are the MintingHub, which governs all collateralised debt positions; the StablecoinBridge, which facilitates 1:1 issuance against other CHF stablecoins; the PositionRoller, which enables flash-loan-based position refinancing, and the Savings module, which distributes interest to ZCHF holders. Collateralised debt positions A position is a debt exposure to a specific collateral asset created and registered by the MintingHub. New position contracts are deployed by the PositionFactory contract, which the MintingHub calls internally when a user opens a new position. Users interact with the MintingHub directly; the PositionFactory operates transparently in the background as the deployment mechanism. Each position belongs to one owner, whose ownership is transferable. The owner deposits collateral and may mint ZCHF up to a limit defined by a liquidation price they specify. When ZCHF is minted from a position, the proceeds are divided into three parts: the usable amount sent to the position owner, a minter reserve withheld within the equity contract and returned upon repayment, and an upfront non-refundable interest fee collected by the reserve pool. Technical collateral requirements Collateral requirements are defined in the smart contract MintingHub.openPosition(). It enforces basic ERC-20 compatibility (including a requirement that failed transfers revert and decimal limits), initial collateral sufficiency, decimal limits, initial collateral sufficiency, a 5,000 ZCHF minimum liquidation value, and a 1,000 ZCHF opening fee. In addition to these technical criteria, broader economic criteria are discussed by the community at https://github.com/Frankencoin-ZCHF/FrankenCoin/discussions/45, including that acceptable collateral should be fungible, free from fundamental transfer restrictions, possess considerable free float, have an externally assessable value, and not be prone to extreme “long tail events”, among other considerations. However, these broader requirements are enforced socially and economically through the initialisation period, veto rights, and challenge-auction mechanism, rather than through hard-coded technical restrictions. Oracle-free liquidation through auctions The system does not depend on external price oracles. Position soundness is instead enforced through a challenge and auction mechanism open to any market participant. A challenger who believes a position's liquidation price is below the market value of the collateral deposits an equivalent amount of the collateral asset and initiates an auction. The auction uses a mechanism that prevents manipulative bidding by the position owner: bids below the liquidation price compete for the challenger's collateral, whilst bids above the liquidation price result in the bidder receiving the position owner's collateral. This design makes price manipulation economically prohibitive. If the highest bid at auction end falls below the liquidation price, the challenge is successful: the position's minter reserve is dissolved, proceeds are distributed to settle the position and reward the challenger at a 2% rate, and any shortfall is absorbed by the equity reserve. Reserve structure The Frankencoin reserve has three components: stablecoins locked in the bridge contracts, minter reserves withheld from each active position, and equity capital held in the FPS contract. The equity capital is exclusively owned by FPS holders. The FPS pricing mechanism is based on the continuous capital corporation model: the market capitalisation of all FPS in circulation is set at three times the equity capital at all times. Anyone may contribute equity capital by minting new FPS at this price, and FPS may be redeemed for a proportional share of the equity capital after a minimum holding period of 90 days. FPS holders absorb residual risk from position liquidations and benefit from minting fees and liquidation surpluses, analogous to the shareholders of a bank. Savings module The Savings module is a governance-approved minting contract that permits ZCHF holders to deposit tokens and earn interest funded from the system's equity pool. Interest is funded from the system's equity pool and distributed at a rate set through the protocol's governance process, which permits FPS holders to propose and enact rate adjustments subject to a seven-day veto window. Deposited ZCHF is fully segregated and attributable to its owner at all times; it is not lent out or otherwise transferred within the system, and unlike minter reserves, it cannot be accessed to cover system losses. A delay of three days applies before interest begins to accrue on a deposit, intended to discourage transactional use. Interest is calculated on the principal amount only; there is no compounding. Interest rate changes are subject to the standard governance veto process with a seven-day enactment window. The Savings module is accessible through the official protocol application at https://app.frankencoin.com/savings. Dependencies All contracts are written in Solidity and deployed on Ethereum mainnet. The system uses no external oracle dependencies. Cross-chain functionality relies on the Chainlink CCIP infrastructure. The official application frontend is maintained at https://app.frankencoin.com. Source code is publicly available at https://github.com/Frankencoin-ZCHF. An emergency governance module, CCIPAdmin (deployed at 0x2527ec458c863073a303CF0a362Bf78aDD5dFEf8 on Ethereum mainnet), enables FPS holders to enact an emergency cut-off of cross-chain bridge flows through swift governance action in the event of a detected bridge exploit or anomalous cross-chain minting activity. This function is not currently exposed in the official frontend and must be invoked directly through a tool such as Etherscan. |
| H.4 | Consensus Mechanism |
ZCHF does not operate an independent consensus mechanism. As an ERC-20 token on Ethereum, it inherits Ethereum's proof-of-stake consensus for all transaction ordering and finality on mainnet. Ethereum validators stake ETH and are assigned block proposal and attestation duties. Ethereum time is organised into 12-second slots and 32-slot epochs. One validator is randomly selected as block proposer per slot; committees of validators attest to the validity of the proposed block. Finality is established once two consecutive checkpoint epochs each receive attestations from at least two-thirds of total staked ETH. Reverting a finalised block would require the slashing of the relevant validator stakes, making such reversion economically prohibitive. On networks other than Ethereum mainnet where ZCHF is deployed, the applicable consensus mechanism of that network governs transaction ordering and finality. (ethereum.org/en/developers/docs/consensus-mechanisms/pos/) The Frankencoin governance process operates above the consensus layer through the veto mechanism described in H.3, and does not itself constitute a consensus mechanism. |
| H.5 | Incentive Mechanisms and Applicable Fees |
Minting fees When a user mints ZCHF against collateral, an upfront non-refundable interest fee is charged and retained by the equity reserve. The interest rate and reserve requirement applicable to each position are defined at the time the position is opened. The fee is calculated at the defined annual rate applied to the minted amount for the remaining duration of the position. This fee structure rewards FPS holders, who bear residual risk, and is designed to sustain the solvency of the equity reserve. Challenger rewards Challengers who successfully initiate an auction that concludes with the highest bid below the position's liquidation price receive a 2% reward on the challenged collateral value denominated in ZCHF. This incentive compensates challengers for the capital at risk during the auction period and is designed to ensure that unsound positions are identified and liquidated promptly. Governance proposal fees Proposing a new minting module or submitting a governance proposal requires payment of a fee of 1,000 ZCHF. This fee is retained by the system regardless of whether the proposal passes or is vetoed, and serves to deter spam proposals. FPS incentives FPS holders receive a share of protocol income from minting fees and liquidation surpluses through automatic adjustment of the FPS price. They also bear residual losses if liquidation proceeds are insufficient to cover outstanding obligations. The minimum holding period of 90 days before FPS can be redeemed from the protocol reduces incentives for short-term speculative participation in governance. Savings rate The savings module distributes interest to depositors from the system's equity pool at a rate set through governance. The savings rate and borrow rate are independent parameters. Proposed rate changes can be enacted after seven days without a veto. Ethereum gas fees All transactions on Ethereum mainnet require ETH for gas. Transaction costs reflect prevailing Ethereum gas prices and are independent of the Frankencoin protocol. On other supported networks, the applicable network's transaction fee model applies. |
| H.6 | Use of distributed ledger technology |
FALSE |
| H.7 | DLT functionality description | N/A |
| H.8 | Audit |
TRUE |
| H.9 | Audit outcome |
BlockBite Security Audit: February 2023
Code4rena Competitive Audit: April 2023
ChainSecurity Audit: Core Contracts, October 2023
ChainSecurity Audit: v2024 Extensions
ChainSecurity Audit: CCIP Bridge
|
| N | Field | Content |
|---|---|---|
| I.1 | Offer-related risks |
CHF/EUR exchange rate risk ZCHF is designed to track the Swiss franc. However, EU holders measure portfolio value in euro, and the EUR/CHF exchange rate is independent of ZCHF's protocol mechanics. A holder acquiring ZCHF on Kraken bears both the risk of ZCHF deviating from CHF parity and the separate risk of CHF depreciating against EUR. These are compounding exposures that are distinct from any risk addressed by the protocol's collateralisation framework. Supply elasticity and external price impact ZCHF has no fixed supply. Minting and repayment activity within the Frankencoin Protocol occurs continuously and independently of trading activity on the admitted platform. Large-scale minting or position repayment events in the protocol may affect circulating supply while a holder is actively trading on Kraken, creating price movements on the exchange that originate outside the exchange's order book and are not visible within it. Venue dependency and delisting risk Access to ZCHF through the admitted trading platform depends on continued listing by Payward Global Solutions Limited (Kraken). Kraken may suspend trading, impose additional eligibility requirements, restrict access by jurisdiction, or delist ZCHF in accordance with its own policies without requiring consent from the offeror or holders. KYC, AML, and access restriction risk Trading ZCHF on Kraken requires account creation, identity verification, and compliance with the platform's eligibility criteria. Users who fail verification, reside in restricted jurisdictions, or are identified as sanctioned persons will be unable to access the admitted trading venue. Regulatory and multi-jurisdiction risk The regulatory treatment of decentralised, overcollateralised crypto-assets such as ZCHF under MiCA continues to develop through supervisory guidance and practice. MiCA is an issuer-centric regime and the definition of e-money tokens, asset-referenced tokens and other crypto-assets is relatively clearer for assets with identifiable issuers, but the recital 22 exemption, and the issuer-centric definition of electronic money, among other gray areas in legal interpretation mean that the consensus classification of ZCHF under MiCA may evolve over time, although in principle the matter should be superfluous due to the recital 22 exclusion from Titles II, III and IV of MiCA. In any event, legal evolution — through interpretation or levels 1 to 3 regulation — across EU member states or third-country jurisdictions may affect the conditions under which ZCHF can be admitted to trading, held, or used. Market abuse risk Crypto-asset markets may be susceptible to front-running, wash trading, spoofing, and other manipulative practices. These risks may be amplified at the time of initial listing or during periods of low liquidity. Market conditions on unregulated decentralised venues may influence prices on the admitted platform. |
| I.2 | Issuer-related risks |
Not applicable as we could not identify an issuer for ZCHF. |
| I.3 | Crypto-assets-related risks |
Collateral value and over-collateralisation risk ZCHF value stability depends on each outstanding position being backed by collateral with a market value exceeding the corresponding ZCHF obligation. A rapid or severe decline in the value of accepted collateral assets — particularly where multiple positions use correlated collateral — could result in under-collateralisation before the auction mechanism completes, resulting in losses absorbed by the equity reserve and a potential reduction in the ZCHF/CHF parity. Auction duration and liquidation speed The system's oracle-free design resolves liquidations through auctions that unfold over a period of hours to days, rather than the near-instantaneous liquidations possible in oracle-based systems. In periods of rapid collateral price decline, the auction mechanism may not resolve quickly enough to prevent under-collateralisation, particularly if multiple positions require simultaneous liquidation. Collateral eligibility and concentration risk Any collateral asset may in principle be proposed and accepted through governance. If the system accumulates material exposure to a single collateral asset or a narrow set of correlated assets, adverse price movements in those assets could affect system solvency disproportionately. The adequacy of the collateral pool depends on governance participants correctly assessing collateral risk at the time of approval. Peg deviation risk There is no hard peg mechanism. Value stability is maintained through economic incentives: over-collateralisation, the arbitrage opportunity created by peg deviations, and the ability of FPS holders to adjust minting costs. Short-term deviations from CHF parity are expected and constitute part of the system's design. Sustained or severe deviations may occur if market conditions, collateral stress or governance failures undermine the incentive structure. Transaction irreversibility and private key risk Transactions on Ethereum are irreversible once confirmed. Loss, theft or compromise of a user's private key results in permanent loss of access to ZCHF, with no mechanism for administrative recovery. Holders are solely responsible for secure key management. Market liquidity risk ZCHF may not always be tradeable at prices close to CHF parity if secondary market liquidity is insufficient. Liquidity on decentralised exchanges depends on the depth of liquidity pools, which may be reduced during periods of market stress. Thin markets may also result in significant price impact for larger transactions. Savings module yield and equity pool dependency The interest paid to ZCHF holders through the Savings module is funded from the system's equity pool, not from an external source or a fixed reserve. The applicable savings rate is set by FPS holder governance and may be adjusted or reduced to zero at any time following the standard seven-day veto window. Additionally, the equity pool from which savings interest is drawn is the same pool that absorbs losses from collateral liquidations. If the equity pool is significantly reduced by liquidation losses, the system's ability to sustain the savings rate may be impaired. Deposited ZCHF in the savings module is fully segregated and cannot be accessed to cover system losses, but the yield on that ZCHF depends on the continued solvency and income of the equity pool. |
| I.4 | Project implementation-related risks |
Governance proposal and veto failure risk The governance system relies on FPS holders reviewing and where necessary vetoing proposed new minting modules. If a harmful or exploitable minting contract is proposed and passes without being vetoed — whether through insufficient attention, collusive or apathetic governance, or a failure to identify risks in complex code — it would gain the ability to mint and burn ZCHF without restriction within the system. The 1,000 ZCHF proposal fee reduces but does not eliminate this risk. Extension module risk The modular architecture permits new minting contracts to be added over time. Each new module introduces additional smart contract surface area and potential economic interactions with existing modules. The v2024 audit identified that the new liquidation mechanism introduced in that release could interfere with the existing one. Future extensions may similarly introduce unforeseen interactions. Immutability and upgrade risk All core contracts are immutable. This eliminates the risk of malicious or accidental upgrades to the token contract but also means that identified deficiencies in core contract logic cannot be corrected after deployment. New functionality must be introduced through separately deployed minting modules and governance approval, which may limit the speed and scope of remediation in the event of a material protocol issue. Ecosystem and interface dependency User interactions with the system depend on the availability and accuracy of the official application at https://app.frankencoin.com, supporting wallet infrastructure, RPC node availability and third-party services such as on-ramps and exchanges. Outages, inaccurate data, or interface changes may impair practical access to the system even where the underlying contracts continue to operate correctly. Adoption and community risk The long-term solvency and utility of the system depend on continued participation by collateral depositors, FPS holders and ZCHF users. Reduced adoption could reduce equity reserves, weaken governance engagement and reduce secondary market liquidity, each of which independently increases system risk. |
| I.5 | Technology-related risks |
Smart contract defects The Frankencoin system consists of immutable Solidity contracts. Undiscovered defects in core contract logic — including the ZCHF token, the MintingHub, the Equity contract or any approved minting module — could result in loss of funds, incorrect accounting or system manipulation. Multiple audits have been conducted, but no audit process guarantees the absence of all vulnerabilities. Oracle-free design limitations The system's auction-based price discovery mechanism requires that potential challengers own or can acquire sufficient quantities of a given collateral asset to initiate a challenge. If a minter acquires a dominant share of a collateral asset's circulating supply, they may be able to prevent effective challenges, allowing unsound positions to persist. This is a known design constraint relevant to the collateral eligibility assessment process. Cross-chain bridge risk The CCIP bridge enabling ZCHF transfers between Ethereum mainnet and supported chains introduces additional technical risk. The ChainSecurity audit identified caveats regarding out-of-order execution and partial data transfer in cross-chain message handling. A bridge failure, including a failure of the underlying CCIP infrastructure operated by Chainlink, could result in loss of funds or state synchronisation failures. The ChainSecurity audit further noted the absence of a recovery mechanism in the event of bridge failure. Ethereum Layer 1 dependency The Frankencoin system's primary settlement layer is Ethereum. System operation is subject to all risks associated with Ethereum mainnet, including Ethereum client defects, consensus failures, network congestion, high gas prices, and risks associated with Ethereum's proof-of-stake validator set. Severe Ethereum network events could delay or impair transaction processing, position management and liquidation activities. FPS vote accumulation and governance attack The vote accumulation mechanism weights votes by FPS holdings multiplied by holding duration, rendering flash-loan-based governance attacks ineffective. However, a patient actor accumulating a sufficient FPS position over time could acquire veto power to block legitimate proposals indefinitely. The kamikaze function built into the FPS contract allows an altruistic participant to sacrifice their own votes to cancel an equivalent number of votes held by a target address, providing a defence mechanism but not a complete guarantee. Quantum computing risk The Frankencoin Protocol, as an ERC-20 system on Ethereum, relies on secp256k1 elliptic curve cryptography for address ownership and transaction authorisation. A sufficiently capable quantum computer running Shor’s algorithm could potentially derive private keys from exposed public keys, allowing attackers to compromise Ethereum addresses holding ZCHF, FPS, or protocol positions. Because the core Frankencoin contracts are immutable and non-upgradeable, any migration to post-quantum cryptography would depend entirely on Ethereum’s own protocol-level response rather than contract-level upgrades by Frankencoin itself. |
| I.6 | Mitigation measures |
Offer-related risks
Crypto-asset-related risks
Project implementation-related risks
Technology-related risks
|
| 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 |
MiCA Crypto Alliance Opco Limited |
| S.2 | Relevant legal entity identifier |
984500CEB5773O38LE40 |
| S.3 | Name of the crypto-asset |
ZCHF |
| S.4 | Consensus Mechanism |
ZCHF does not operate as an independent consensus mechanism. As an ERC-20 token on Ethereum, it inherits Ethereum's proof-of-stake consensus for all transaction ordering and finality on mainnet. Ethereum validators stake ETH and are assigned block proposal and attestation duties. Ethereum time is organised into 12-second slots and 32-slot epochs. One validator is randomly selected as block proposer per slot; committees of validators attest to the validity of the proposed block. Finality is established once two consecutive checkpoint epochs each receive attestations from at least two-thirds of total staked ETH. Reverting a finalised block would require the slashing of the relevant validator stakes, making such reversion economically prohibitive. On networks other than Ethereum mainnet where ZCHF is deployed, the applicable consensus mechanism of that network governs transaction ordering and finality. (ethereum.org/en/developers/docs/consensus-mechanisms/pos/) The Frankencoin governance process operates above the consensus layer through the veto mechanism described in E.3, and does not itself constitute a consensus mechanism. |
| S.5 | Incentive Mechanisms and Applicable Fees |
See H.5 |
| S.6 | Beginning of the period to which the disclosed information relates |
2026-01-01 |
| S.7 | End of period to which disclosed information relates |
2026-04-29 |
| Mandatory key indicator | ||
| S.8 | Energy consumption |
|
| Sources and methodologies | ||
| S.9 | Energy consumption sources and methodologies |
Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5). |
| 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 |
Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5). |
| S.16 | Key GHG sources and methodologies |
Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5). |
| 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 |
Land use: 144.74726 m² |
| 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 |
Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5). |
| S.34 | Other GHG sources and methodologies |
Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5). |
| S.35 | Waste sources and methodologies |
Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5). Estimates on individual node weight, hazardous components and depreciation rate are used. |
| S.36 | Natural resources sources and methodologies |
Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5). Usage of natural resources is approximated through land use metrics. Land use, water use and water recycling are calculated based on energy mix-specific estimates of purchased electricity land intensity, purchased electricity water intensity, and water recycling rates. Full methodology available at: www.micacryptoalliance.com/methodologies |