Markets in Crypto Assets (MiCA)

The Markets in Crypto Assets (MiCA) is a comprehensive regulatory framework proposed by the European Union (EU) to govern the issuance and provision of services related to crypto assets. MiCA is part of the European Commission’s Digital Finance Strategy and due to take effect beginning in June 2024.

Here are the MiCA regulations in English. (Here are the regulations in each of the official languages of the EU.)  The regulations cover crypto asset issuers, crypto asset offerors, e-money tokens, and asset-referenced tokens. Any company offering crypto assets within the block of 27 nations that make up the European Union will be subject to these regulations.

The regulations require that a "whitepaper" be published by any company offering crypto assets to the public within the European Union.  The whitepaper is somewhat like a "management discussion and analysis" and does include financial information.

Inline XBRL (iXBRL) format will be used for MiCA whitepapers. The European Securities and Markets Authority (ESMA) has made available a Proof of Concept (PoC) to allow market participants to familiarize themselves with Inline XBRL. This PoC includes a draft XBRL taxonomy.

I created an implementation of the MiCA proof of concept.

An estimate of the number of crypto asset offerors and issuers that might be impacted is approximately 20,000. Wikipedia says there are about 20,000 crypto currencies as of 2023. This Forbes list has 11,503. The Motley Fool says there are about 23,000. Investing.com uses the number 10,125. This Forbes article puts the number at 22,932; it also describes the different types.

Auditchain Labs says that they are the first company to publish the required white paper.  Here is an example of a crypto asset white paper for Pacioli.ai.  That Pacioli.ai whitepaper was published using Auditchain Luca.

Here is information about that Pacioli.ai whitepaper:


What I am personally trying to achieve with MiCA is to take advantage of all the GOOD THINGS that the SEC and ESMA have done in terms of XBRL-based digital reporting and leverage those good ideas and to avoid the NOT SO GOOD THINGS. The SEC and ESMA have boldly led the way in XBRL-based digital financial reporting in a very big way. While their follow through in terms of making adjustments to fix glitches leaves something to be desired; the SEC's and ESMA's pioneering efforts are greatly valued.

Additional Information:


Comments

Post a Comment

Popular posts from this blog

Relational Knowledge Graph System (RKGS)

Image
Relational Knowledge Graph System (RKGS) is an interesting idea that combines the relational paradigm and the knowledge graph paradigm.  This documentation, Why RKGS , explains the idea. This gets even more interesting with the notion of "relational AI".  RelationalAI is described as follows by the company of the same name, Relational.ai : “RelationalAI is a cloud-based relational knowledge graph management system, with state of the art probabilistic processing and declarative reasoning at scale to make developing Data Applications a superpower for your business.” This notion of knowledge graphs represented in relational databases fits into my belief that knowledge graphs have two aspects: the expression SYNTAX and the logic of what is expressed or SEMANTICS. While the LOGIC of a knowledge graph is always the same regardless of technical syntax used to express that logic; there are many, many different technical syntaxes that can be used to represent a knowledge graph. There
Read more

Graph Hairball

Image
Knowledge graph system logic, the "things" and "relations between things" that  graph theory calls "vertices" (a.k.a. nodes, points, entities, things) and "edges" (a.k.a.  links, lines, relations, associations), looks like a big graph hairball as some people call it an example of which you can see here: Why?  This common view of a graph is because there has to be some "general view" of the information provided by the graph.  This is just like a general view of the information within a relational database is a table ; a set of ROWS and COLUMNS for exactly one table at a time. So what is interesting is that with a graph database the default view is everything in the graph of knowledge.  Whereas the default view of everything in a relational database is one table at a time. Further, it does not really matter whether the information that populates your knowledge graph comes from, say, CSV files, Excel, JSON, XBRL, RDF, PROLOG or whateve
Read more

PLATINUM Business Use Cases, Test Cases, Conformance Suite

Image
A brick wall is made of exactly two things: bricks, mortar. But a brick wall created by a master craftsman, or mason, and a brick wall created by a “weekend warrior” with no knowledge of masonry will be very different. Master craftsmen are created and that process takes time and effort. This blog post is a first prototype that brings several things together into one useful resource for business professionals.  It pulls together the human readable information of the Showcase of Reports   and the machine readable information of the Conformance Suite of XBRL-based Financial Reports Prepared using the Seattle Method .  Then, I want to incorporate the information found in these PLATINUM XBRL-based Financial Report Examples . The three resources can be useful and used independently; but they are even more useful when used together.  Business professionals really could not care a less about the technical details of getting some result that they want.  But technical professionals need to under
Read more