Every time you change your token, you are making a regulatory decision.
Every time you change your token, you are making a regulatory decision. Most founders don't know that. This is one of the most common MiCA token classification mistakes I see in practice.
Most founders don’t think about that.
They do the legal work once, usually at launch. They get a classification opinion, or they take a view themselves (sometimes right, sometimes not), and they move on.
Take this scenario for instance, the token is a utility token. MiCA applies. Whitepaper drafted. Box ticked.
It is what happens next that changes things… the product evolves.
A staking mechanism goes in. Users can lock tokens and earn rewards. Then a governance layer, holders can vote on protocol decisions. Then a redemption feature, tokens can be exchanged for credits, services, or real-world value.
Each of those decisions felt like a product decision or a tokenomics call. A way to increase engagement or retention. Which makes sense, this is what they should be thinking about… but… each of them could also change the regulatory picture.
This is where the trouble starts – the token they are actually running looks nothing like the token they originally classified.
MiCA looks at what your token does, not what you call it
MiCA classifies tokens based on what they do, not what they are called, and not what they did when you launched.
A token that grants access to a service is a utility token. Peg it to a real-world asset and you’re no longer looking at a whitepaper. You’re looking at full authorisation. A project adds staking rewards to a utility token. Holders lock tokens and earn a return. The moment a token generates returns for holders, it stops looking like a utility token and starts looking like an investment instrument. Potentially a MiFID question which is an even harder place to be.
The categories are not fixed in stone, they move with the product. Change the product and risk changing the classification under MiCA, or any other regulatory regime as a matter of fact.
Founders are making a call, a product call and assuming the legal/ regulatory picture has not changed.
Where MiCA Token Classification Catches Founders Out
The projects I see get caught here are not the ones that ignored MiCA at the start. They are the ones that did the work but kept building without reassessing or looping legal back in.
Token classification is only one example. The same pattern plays out across licensing, cross-border structuring, and commercial agreements. The product moves. The legal review does not.
A project adds staking rewards to a utility token. If the issuer is paying a return to holders, a regulator may start asking whether this is still a utility token at all, or whether it has taken on characteristics of an investment instrument or something else. Most founders do not ask that question before they ship the feature.
A project that originally served non-EU users expands. Same token, same structure, same legal opinion from eighteen months ago. Now it has material EU users. MiCA applies based on where your users are, not where your entity is. The regulatory position changed the moment the user base did.
In each case, the founder thinks they are inside the same regulatory position they started in. They are not.
Questions worth asking before you ship
Token classification is not a one-time exercise. It is something that needs to travel with the product.
That does not mean involving legal at every sprint. It means building a simple check into your product process: when we add a feature that changes what the token does or how it is used, we ask the classification question again. And when we expand into new markets, we ask the scope question again.
Specifically:
- Does this change what the token grants access to?
- Does this introduce a redemption or exchange mechanism?
- Does this create a return, reward, or yield for holders?
- Are we expanding who we are offering this to, including into EU markets?
If the answer to any of those is yes, it is worth a conversation before the feature ships or the market opens, not after.
Getting it right is not about slowing down
Good legal work at this stage is not a blocker. It is a sequencing question.
The founders who get into difficulty are not usually the ones who move too fast. They are the ones who made product decisions in isolation from their regulatory position, and found out later that the two had diverged.
Token classification is one of the clearest examples of that divergence. It is also one of the easiest to manage, if you treat it as an ongoing question rather than a closed one.
If you are not sure whether your token still sits where you classified it, that is usually a sign it is worth checking.
More from DLT Law
If you found this useful, these may also be relevant:
If you are thinking about listing your token on EU exchanges, MiCA has specific requirements for that too. Read more here.
If your project touches payments, you many need additional licensing which most founders miss. Read more here.
For more on how DLT Law works with crypto and Web3 founders across MiCA, licensing, and cross-border structuring, visit dltlaw.io.
