What we had to work out ourselves.
We build products that fall under European crypto rules, so we read the regulation before we ship. These are the notes, written properly rather than as a sales funnel.
Three practical entry points
The library currently covers CASP authorisation under MiCAR, crypto custody, and stablecoin regulation. Each guide starts with a decision a product team must make, separates software from regulated services, and points readers towards the terms and official registers that matter. Use the article summaries below to choose the relevant path.
The CASP guide focuses on service scope and authorisation. The custody guide explains key control and provider access. The stablecoin guide distinguishes asset-referenced tokens, e-money tokens, issuers, and service providers. These notes are educational references, not legal advice. Where a decision determines whether a company may operate, verify the current primary sources and take the specific service model to qualified counsel.
CASP authorisation under MiCAR
The question most teams actually have is not how to get authorised. It is whether they need to be.
Custody models, and what each one triggers
Institutions usually pick a custody provider first and discover the regulatory consequence second. It works better the other way round.
Stablecoin regulation under MiCAR: ART, EMT and CASP
MiCAR uses defined legal categories instead of treating every stablecoin alike. The practical answer depends on the token's reference, the actor's role and the service actually provided.