Three Lines of Defence - yields.digital - LYRA Risk Framework - Q2 2026
Your 3rd Line of Defence
Compliance Manager
Because your regulator does not accept "we believe we were compliant." They accept evidence - structured, timestamped, article-level evidence. MiCA has made this a legal obligation, not a best practice.
What is yields.digital?
yields.digital's LYRA (Layered Yields & Risks Assessment) helps support MiCA compliance for European CASPs and regulated asset managers - with article-level monitoring, structured timestamped outputs, and reporting aligned to competent authority submission requirements. Not a general risk tool adapted for compliance. A system built around the specific obligations that regulators require with the correct logic applied to each article.
2026 Roadmap - in active development, delivering Q2-Q3 2026
Detailed, quantified disclosure of risks, mechanisms, and conflicts of interest for every crypto-asset offered (Art. 19 for asset-referenced tokens)
The Risk Without LYRA
Narrative risk descriptions that are difficult to update, impossible to standardise across offerings, and hard to defend when market conditions change after issuance.
What LYRA Supports
Quantified four-dimension risk scores providing structured, auditable evidence for MiCA white paper risk sections. Updated continuously - not a point-in-time assertion.
Issuers must update white papers when material changes occur. Art. 26 establishes liability for inaccurate or misleading information throughout the life of the offering.
The Risk Without LYRA
Point-in-time disclosures that become stale and create growing liability as conditions change. No system tracks whether the original disclosure remains accurate on any given day.
What LYRA Supports
Continuous monitoring with timestamped records enabling issuers to demonstrate that disclosed risk parameters remain accurate every day after issuance - not just on day one.
Both quarterly average daily transactions exceeding 1,000,000 AND quarterly average daily transaction value exceeding EUR 200,000,000 must be breached concurrently before the obligation to submit a compliance plan is triggered.
The Risk Without LYRA
No dual-AND-threshold monitoring. OR logic produces false alerts. Single-metric monitoring misses genuine concurrent breaches. Either creates direct enforcement exposure.
What LYRA Supports
Parallel monitoring of both thresholds with strict AND logic. Only concurrent breach of both quarterly averages generates a compliance alert, with regulatory-grade timestamp.
Systematic monitoring and management of concentration in assets backing asset-referenced token reserves. (Art. 54 applies equivalent requirements to e-money token reserves.)
The Risk Without LYRA
Manual HHI calculation with inconsistent methodology and no continuous monitoring. Not defensible under regulatory examination. Impossible to scale across multiple reserve assets.
What LYRA Supports
Automated HHI computation at reserve asset level, mapped directly to Art. 38 language, with configurable concentration thresholds and continuous breach alerting.
Documented policies and systems for assessing, monitoring, and managing liquidity risk in reserve portfolios.
The Risk Without LYRA
No documented, systematic liquidity risk management framework. This is a direct, identifiable compliance gap under examination by any competent authority.
What LYRA Supports
Pool TVL monitoring, deployment capacity analysis, LP concentration assessment, and stress scenario outputs structured to align with Art. 40 requirements.
Mandatory since 23 December 2025 (Regulation 2024/2984): crypto-asset white papers notified or submitted to competent authorities must be in machine-readable structured format.
The Risk Without LYRA
Manual formatting, taxonomy misalignment, transcription errors. Time-consuming to prepare and error-prone to validate. Incorrect taxonomy produces rejected filings and resubmission delays.
What LYRA Supports
Structured output pipeline producing iXBRL-ready compliance reports aligned to ESMA MiCA reporting taxonomy. No manual formatting, no transcription, no taxonomy errors.
Art. 23 - The compliance distinction that most monitoring systems get wrong:
Art. 23 applies strict AND logic. Both thresholds must be satisfied concurrently for the obligation to be triggered:
Quarterly average daily transactions > 1,000,000 AND quarterly average daily transaction value > EUR 200,000,000
A system using OR logic generates false alerts - potential unnecessary cessation of issuance with material commercial consequences.
A system monitoring only one metric misses genuine dual-threshold breaches - a silent compliance violation.
LYRA monitors both metrics in parallel. Only concurrent breach of both quarterly averages generates a compliance alert with a regulatory-grade timestamp.