Tokenised rights and digital objects: the decisions this practice answers
A token is a wrapper. What matters is what sits behind it: a claim, a right, a debt, a share of something real. This hub does not answer any single question about tokenised assets. It sorts the question you actually have into the page built to answer it, and tells you where the boundary of each page sits.
The decision map
Most enquiries in this area fall into one of a small number of buckets. The table below matches the practical question to the page that carries the detail.
| Your question | Where it is answered |
|---|---|
| A token claims to carry a licence. What does that mean for us? | Situation page on token-backed licence claims |
| How is a token issued, offered and traded end to end? | Token issuance and trading overview |
| What can be established about a specific asset from official Lithuanian sources? | Asset factual report, Lithuania |
| What can be established about a specific debtor from official Lithuanian sources? | Debtor factual report, Lithuania |
If your question is not in this table, it is likely one level below — inside one of the pages linked from this hub, not on this hub itself.
Where to start
Two entry points cover most of what reaches this practice. The first is issuance and trading mechanics: Token issuance and trading overview explained walks through how a token comes into existence, who is involved, and what obligations attach at each step. The second is verification: Factual reports on official sources overview explains how we check what a register actually shows, separate from what a counterparty claims it shows.
Start with issuance if the token does not exist yet or you are evaluating a structure. Start with reports if a token, a counterparty, or a claim already exists and you need to know what is verifiable before you rely on it.
What changes in practice
Two pieces of EU law set the current frame for crypto-assets and tokenised claims. Regulation (EU) 2023/1114 (MiCA) sets out authorisation, disclosure and conduct rules for crypto-asset issuers and service providers. Regulation (EU) 2023/1113 (TFR) sets information requirements for transfers of funds and crypto-assets, including the data that must travel with a transfer between providers.
Together, these two instruments mean a token is rarely a purely technical object anymore. Depending on what it represents and who moves it, the issuer, the platform, or the counterparty may sit inside a licensing perimeter, a disclosure duty, or a transfer-information requirement. Which of these applies is a page-specific question, not a hub-level one.
What to do first
- Write down, in plain language, what the token is supposed to represent. Not what it is called — what it is claimed to carry.
- Identify who issued it and where that issuer is established or registered.
- Check whether a transfer has already happened, or whether you are still at the decision stage.
- Collect any document that describes the claim: a whitepaper, a smart contract reference, a terms page, a register extract.
- Route the question using the table above before contacting us. It shortens the first call.
Sources and limit
This hub does not verify anything itself. Verification sits in the reports layer, built from official registers rather than from what a counterparty or a platform states about itself. For a specific asset in Lithuania, the relevant starting point is Asset in Lithuania, which sets out exactly what can and cannot be confirmed from the register.
For a specific counterparty rather than an asset, the equivalent starting point is Debtor in Lithuania. Both pages state their coverage and their limits before any figure or status is quoted.
This hub does not itself state deadlines, fees, or procedural steps for any single scenario. Those sit on the page matched to your question, not here.
Related publications
If a counterparty has already told you that a token carries a licence, read When a token claims to carry a licence: what before you take any further step. It covers what to check first, in what order, and what not to assume from the claim alone.
Verified
This overview draws on Regulation (EU) 2023/1114 (MiCA) and Regulation (EU) 2023/1113 (TFR), both in force across the EU. Neither instrument is cited here for a specific national obligation; national implementation, where it applies to your situation, is addressed on the relevant page rather than on this hub.
Frequently asked
What does this change in practice?
It moves tokenised claims from an unregulated grey area into a framework with named obligations for issuers and service providers, and named information duties for transfers. Which obligation applies to you depends on your role, not on the token's label.
Which deadline applies?
There is no single deadline at hub level. Each page linked above states the deadline relevant to its own scenario, because the deadline depends on the procedure, not on the fact that a token is involved.
What do you need from us to start?
A description of what the token or the claim represents, the identity of the issuer or counterparty, and any document already in your hands. That is enough for a first, useful answer.
Aleks Vaher