Significant ART/EMT Thresholds and EBA Supervision: Instrumenting the Trigger Metrics

Under MiCA, becoming “significant” is not a badge. It is a change of supervisor and a step-up in duties, and the trigger is a set of numbers you already generate every day. The mistake is treating those numbers as a reporting output rather than an operational alarm.

Most writing about MiCA significance describes the criteria as if they were a static classification a lawyer confirms once. In practice they are moving metrics attached to a live product. An asset-referenced token (ART) or e-money token (EMT) that is growing is walking towards a line, and the day it crosses that line the European Banking Authority takes over its supervision from the national competent authority, with heavier prudential and governance obligations attached. If the first time your board hears about it is in a letter from the EBA, you have already lost the ability to plan the transition. This is a data problem before it is a legal one.

What actually trips the wire

Article 43(1) of MiCA sets out seven criteria for classifying an ART as significant. An issuer is caught when it meets at least three of them. Three are hard numeric thresholds you can instrument directly:

• Holders. The number of holders is larger than 10 million.
• Size. The value of the token issued, its market capitalisation, or the size of the issuer’s reserve of assets is higher than EUR 5 billion.
• Transactions. The average number of transactions per day is higher than 2.5 million and their average aggregate value per day is higher than EUR 500 million. Both limbs have to be met for this one criterion to count.

The other four are qualitative or structural: designation as a gatekeeper under the Digital Markets Act; the significance of the issuer’s activities internationally, including use for payments and remittances; interconnectedness with the financial system; and whether the same issuer runs at least one further ART or EMT and provides at least one crypto-asset service. For e-money tokens, Article 56 applies the same set of criteria. The upshot is the same for both instruments: three of seven, and you change regime.

The point that gets missed is that you probably control several of the qualitative criteria structurally and permanently. If you already issue two tokens and run a custody or exchange service, the multi-service criterion is a standing yes. That leaves the numeric thresholds doing the real work of deciding when you tip over. Which is exactly why they belong on a dashboard, not in a quarterly return.

The data is already leaving the building

You are not being asked to invent this telemetry. Article 22 already requires issuers of ARTs above EUR 100 million in issued value to report, every quarter, the number of holders, the value of the token issued and the size of the reserve, and the average number and average aggregate value of transactions per day. Those are, almost exactly, the significance metrics. The regulation has told you which numbers matter by making you report them.

So the raw feeds exist. The failure is one of latency and framing. A number computed once a quarter for a supervisory filing tells you where you were, sometimes months ago. A significance threshold crossed in week three of a quarter is a fact about your firm long before it appears in a return. Treat the Article 22 metrics as a batch obligation and you will find out you are significant after the market does. Compute the same metrics daily, against the significance lines rather than the reporting threshold, and you convert a compliance artefact into an early-warning system. The same discipline of treating a regulatory disclosure as a data object rather than a document applies directly here.

Instrument the metrics, not the deadline

The queries below compute the three numeric criteria on a rolling daily basis and flag not just breaches but proximity — because the value of this is in the approach, not the crossing. Alert at, say, 80 per cent of each line and you buy the months of lead time you need to raise own funds, appoint the additional functions, and brief the board before the supervisor changes.

-- MiCA Article 43(1) significance metrics, computed daily.
-- Thresholds: holders > 10m; size > EUR 5bn;
-- transactions > 2.5m/day AND aggregate value > EUR 500m/day.
-- Warn at 80% of any line so the transition can be planned.

WITH daily_tx AS (
    SELECT
        tx_date,
        COUNT(*)              AS tx_count,
        SUM(value_eur)        AS tx_value_eur
    FROM token_transactions
    WHERE token_id = :token_id
      AND tx_date >= CURRENT_DATE - INTERVAL '90 days'
    GROUP BY tx_date
),
rolling AS (
    SELECT
        AVG(tx_count)     AS avg_tx_per_day,     -- limb 1 of the tx criterion
        AVG(tx_value_eur) AS avg_tx_value_per_day -- limb 2; BOTH must breach
    FROM daily_tx
),
point_in_time AS (
    SELECT
        (SELECT COUNT(*) FROM token_holders
           WHERE token_id = :token_id AND balance > 0) AS holder_count,
        (SELECT reserve_value_eur FROM reserve_snapshot
           WHERE token_id = :token_id
           ORDER BY as_of DESC LIMIT 1)                 AS reserve_eur
)
SELECT
    p.holder_count,
    p.reserve_eur,
    r.avg_tx_per_day,
    r.avg_tx_value_per_day,
    -- criterion flags (1 = met)
    (p.holder_count > 10000000)::int                       AS crit_holders,
    (p.reserve_eur  > 5000000000)::int                     AS crit_size,
    (r.avg_tx_per_day > 2500000
        AND r.avg_tx_value_per_day > 500000000)::int       AS crit_transactions,
    -- proximity warnings at 80% (structural criteria counted separately)
    (p.holder_count >= 0.8 * 10000000)::int                AS warn_holders,
    (p.reserve_eur  >= 0.8 * 5000000000)::int              AS warn_size,
    (r.avg_tx_per_day >= 0.8 * 2500000
        OR r.avg_tx_value_per_day >= 0.8 * 500000000)::int AS warn_transactions
FROM point_in_time p CROSS JOIN rolling r;

The output of that query is one row a day. The number that matters is the count of numeric criteria met, added to whatever standing qualitative criteria apply to your firm. When the running total reaches three, you are significant on the metrics whether or not the classification decision has yet been taken. Set the alert to fire well before that, and route it to a named owner — not a shared inbox. The same instinct that makes teams instrument delivery metrics rather than guess at them applies to a regulatory boundary: measured continuously, it stops being a surprise.

What crossing the line actually costs

Instrumentation only earns its keep because the consequences are material. Once an ART is significant, supervision passes to the EBA and the own funds requirement rises from 2 per cent to 3 per cent of the average reserve of assets. There are additional obligations on remuneration policy, on liquidity management, and on interoperability, and equivalent duties attach to significant EMTs. These are not documentation exercises you can complete in a fortnight. Raising own funds and standing up new governance functions takes a planning horizon measured in quarters, which is precisely the horizon a daily metric buys you and a quarterly return does not.

This connects directly to the operational spine of an issuer — the reserve management, redemption and reporting machinery that has to scale with the token. The significance thresholds are the moment that machinery is asked to carry more weight under a different supervisor. Knowing the moment is coming is the whole game.

The instruments and figures here should be checked against the current consolidated text and the EBA’s delegated acts on significance before you build to them; the criteria in Article 43 are settled, but the surrounding technical standards continue to move. Verify, then instrument. A regulator who watches your metrics in near real time is a fact of the regime. The only question is whether you are watching the same numbers first.