Check MiCA Reserve Disclosure

rca-02-mica-reserve-stress is a Monte Carlo redemption stress under Article 36: 1,000 paths over 90 days, a fan chart and a breach probability. That asks whether the reserve survives a run, which is a forward-looking simulation. This node asks whether a published disclosure matches the terms you declared, and answers it deterministically. Its simulation is not imported here and its kernel is untouched. art-105-mica-token-service-scoper scopes which services apply, and tools/332-mica-casp-authorization-checker checks authorisation. Neither of those reads a reserve disclosure.

The eligible asset classes, the concentration limits, the minimum segregated percentage, the acceptable custodian types and the publication cadence are all inputs on this page. They stay inputs on purpose. A bundled reporting template is a standing duty to chase someone else's revisions, and the day it stops being chased it goes quietly false while still looking authoritative. Because the rules travel with the run and are pinned in the receipt alongside rules_version, a later rule change makes an old receipt dated rather than wrong. Where a named person attests the check, use art-503-build-dual-control-certification: this page evaluates no threshold of its own and builds no second certification.

The rules are yours and are merely asserted. The amount in circulation, the component amounts, the custodian types, the segregation markers and the publication dates are taken as given from the disclosure you are checking; this page does not verify that the published document says what you transcribed from it, nor that the reserve exists, nor what anything is worth. It performs no lookups of any kind (zero-egress, no network calls after load) and ships no eligible-asset table and no issuer library. Every verdict is measured against your declared rules, so a finding can equally originate from a rule this run had wrong. This is not a determination that the issuer complies with MiCA or anything else, not legal advice, and not a submission to any authority.

Verified 1 August 2026 against the consolidated text of Regulation (EU) 2023/1114 on EUR-Lex. Article 30(1) requires the issuer to disclose, in a publicly and easily accessible place on its website, the amount of asset-referenced tokens in circulation and the value and composition of the reserve of assets referred to in Article 36, updated at least monthly. Article 36(2) and 36(3) require the reserve to be legally and operationally segregated from the issuer's estate and from other reserves. Article 37(3) has the reserve assets held in custody by a crypto-asset service provider, a credit institution or an investment firm, and Article 37(1)(d) and (e) require concentration of custodians and of reserve assets to be avoided. Article 54(a) requires at least 30 percent of funds received for e-money tokens to be deposited in separate accounts in credit institutions. Two things often repeated elsewhere are not encoded here because they do not hold: the Regulation applies from 30 December 2024 under Article 149(2), with Titles III and IV, which contain Article 30, applying from 30 June 2024, so "in full from 1 July 2026" is a misreading of the Article 143(3) transitional window for service providers; and there is no weekly publication cadence for significant tokens in the text, only the weekly maturities input to a liquidity technical standard in Article 36(4)(b), which is a different subject. That is exactly why the cadence on this page is a number you type.