MiCA Environmental Disclosures: What a CASP Must Actually Document

Decentralised News · Editorial by Heath Muchena · Evidence reviewed 11 November 2026. Original DN analysis and local instrument; field testing is claimed only where expressly reported.

A sustainability page can contain plenty of numbers while leaving its reader unable to identify what they describe. Is the energy figure for the service provider’s own offices, the underlying network or an allocation to one asset? Which period does it cover? Was it measured, estimated or copied from another document? The operational challenge is to maintain that chain of meaning.

For a CASP, begin by identifying the exact legal entity and the services it provides. A group brand is an inadequate substitute if several entities serve different markets. Then connect each relevant asset to the consensus mechanism and the evidence used in its disclosure. DN’s record is designed around that handoff between legal scope, technical data and the published page.

The current rule, in a bounded statement

MiCA Article 66(5) requires CASPs to publish prominent website information about the principal climate and other environmental impacts of the consensus mechanisms underlying the crypto-assets for which they provide services. It permits information to be obtained from white papers. Source: ESMA’s Article 66 text.

Delegated Regulation 2025/422 entered into force on 20 April 2025. Under Article 5, Table 2 is mandatory for in-scope CASPs. Table 3 becomes mandatory when both the specified service condition and annual S.8 energy above 500,000 kWh are met. Table 4 indicators are optional. Methods, sources and estimates have associated disclosure requirements; offsets do not reduce the calculated indicators. Source: Regulation 2025/422; official dates.

The specified services are operating a trading platform, exchanging crypto-assets for funds, or exchanging them for other crypto-assets: Article 3(1)(16), points (b), (c) and (d). A service description should be checked against those definitions, rather than inferred from a company calling itself an exchange. Source: ESMA’s Article 3 text.

Claim versus evidence: from a badge to a traceable disclosure

These are DN’s operational questions, not an additional regulatory template. They help a team preserve the evidence behind its chosen disclosure. A complete worksheet remains distinct from a conclusion that the disclosure satisfies every applicable obligation.

Make the entity and asset inventory explicit

Assign a record to a legal entity, a service scope and a reporting unit. Use the internal identifier that the legal and compliance teams already recognize. Do not ask an analyst to reconstruct the entity from a logo, domain name or global marketing page. A change in the customer-facing brand may leave the underlying legal relationship unchanged; a change in entity may require a new assessment even when the brand stays the same.

Next, list the assets the review actually covers. Keep the source of that inventory and the date it was generated. A spreadsheet that omits newly offered assets can remain internally tidy while drifting away from the service’s actual scope. The review should therefore have an explicit trigger for additions, removals and changes in how an asset is offered.

Separate identifiers that look similar. A ticker is a label, not a complete description of a network, token representation or consensus mechanism. The evidence file should allow the technical reviewer to identify the exact object without relying on familiarity with a trading screen. Where the relationship is uncertain, record the uncertainty before importing another asset’s figures.

Build a source trail that survives copying

A useful disclosure record contains the original source, the field extracted, the reference period and any transformation applied before publication. Copying a value into a content-management system should not sever that trail. Store the original unit as well as the displayed unit, especially when converting between kilowatt-hours and megawatt-hours.

Keep measurement and estimation labels attached to the relevant value. If a dataset blends both, ask which components are observed and which are modeled. A single label at the bottom of a page may be difficult to interpret when different rows have different evidence. DN’s worksheet records the method reference rather than guessing how a provider derived the figure.

ESMA explicitly cautions that white papers in its register have not been reviewed or approved by a competent authority. The presence of a document in that register therefore does not turn its environmental figures into verified findings. Preserve the author’s identity, source and assumptions when using it as evidence. Source: ESMA MiCA implementation and register page.

Use an evidence alias in the shared worksheet, such as “network-method-v3” or “scope-review-2026Q4.” Retain detailed working papers in the organization’s normal controlled system. The local DN tool neither retrieves those documents nor assesses their content.

Use the DN MiCA Sustainability Disclosure Record

The record has seven areas: scope, asset identity, reporting period, table mapping, methods, publication and review. Each area is recorded as a referenced document, an explicit issue or an unknown. A reference requires an alias. Seven references indicate seven documented pointers, not seven passed legal tests.

The optional scope illustration takes three inputs: whether the relevant CASP scope has been assessed, whether a specified service is provided, and annual energy for S.8. It preserves uncertainty about the legal scope and the data. It does not use the business’s office electricity bill, customer turnover or trading volume as substitutes for the required energy field.

Constructed boundary check: with confirmed scope and a specified service, entered energy of 500,000 kWh does not cross the “above” condition; 500,001 kWh does. If the service or energy input is unknown, the tool retains that uncertainty unless another entered condition already rules out the conjunction. These are logical examples, not findings about a named CASP.

The output says what the entered conditions imply for this limited illustration. It never says “compliant,” “approved” or “exempt from MiCA.” Other fields and obligations remain outside the calculation. The export is also not the prescribed disclosure format; it is a working record that helps the responsible team assemble and review its actual publication.

Design the review around changes that matter

A practical internal workflow gives each change a destination. A new asset prompts an inventory check. A revised network methodology prompts a data review. A new service or entity prompts a scope review. A corrected source figure prompts a publication review. Assigning those triggers is DN’s operational recommendation, not a claim that this article specifies every statutory update deadline.

Retain the previous published version when making a correction. The reader should be able to distinguish a new reporting period from a repaired error. A changed value may reflect new observations, a revised estimation method, a unit correction or a different boundary. Those explanations have different implications for comparison over time.

For automated publishing, require the evidence record to change with the visible page. An automated job that refreshes a number while leaving its old source date can create a misleading combination. A useful control is to stop the refresh when the source’s unit, period or field definition changes unexpectedly, then route the difference to a reviewer.

DN’s existing MiCA licensing explanation addresses service-scope questions. This article handles the environmental disclosure record after that scope is identified. The related energy-boundary discussion helps explain why a denominator and a reporting unit must remain explicit; its task-level model is not a replacement for a network disclosure.

What a useful review meeting should produce

Bring the current page, its asset inventory and the source trail into the same review. Ask the legal reviewer to confirm the scope statement, the technical reviewer to confirm the data mapping, and the publishing owner to confirm that the page reflects the reviewed version. Record disagreements as unresolved items with a next action.

A missing input may lead to further research, an appropriately supported estimate or a corrected scope assessment. The choice requires the actual facts and the applicable rules. The worksheet does not select an estimate simply because a blank looks unattractive. It gives the team a concise list of what has not yet been resolved.

When presenting the result to management, distinguish evidence availability from substantive findings. “Six areas have references and one has an unresolved method issue” is a useful status statement. “We are 86% compliant” would claim a relationship the tool has not established. The latter would also conceal the possibility that the one missing issue is decisive.

Methodology and limitations

This article reviews current primary legal materials within the stated EU CASP scope. It does not survey US, UK or other jurisdictions, and it does not assume that every crypto business is a CASP. Issuer and white-paper obligations can require separate analysis. No named entity’s service permissions, assets or disclosure quality were investigated.

DN’s original method counts seven documentation areas and applies one transparent conditional illustration. Legal applicability, evidence quality and publication adequacy remain outside the calculation. The JSON has a stable schema, self-reported evidence label, null approval and separate record-creation time. No creation timestamp is presented as a regulatory or evidentiary verification date.

Frequently Asked Questions

Is this a new 2027 requirement?

The cited legal instruments already have their own published dates. A future planning label should not replace those dates or create obligations in another jurisdiction.

Does a below-threshold entry mean no disclosure is required?

No. The instrument illustrates a limited supplementary-condition question. It does not remove the rest of the disclosure review or decide that an entity is outside scope.

Does a white paper in ESMA’s register have regulatory approval?

ESMA says the listed white papers have not been reviewed or approved by a competent authority. Treat registration and substantive verification as separate questions.

Can I publish the downloaded JSON as my official disclosure?

The export is a DN working record. Use the actual applicable format and obtain the necessary review for the publication you intend to make.

Corrections and change log

Send corrections with the legal provision, official source, version date and affected passage to press@decentralised.news. 11 November 2026, version 1.0: replaced the proposed generic future ESG premise with a bounded EU CASP evidence record. No legal approval, market compliance ranking or blanket US mandate is asserted.