
Author: João Lages
Tokenization is not for every asset owner, investor or financial institution. It is most useful when three conditions exist together: there is a legally defined right worth recording; several parties must coordinate ownership, eligibility, cash flows or settlement; and a programmable record can remove a measurable friction across the product’s life. If the right is vague, the transaction is one-off or the token adds another ledger without replacing any work, conventional infrastructure is usually the better answer.
This distinction matters because “who is tokenization for?” is often answered with an industry list: real estate, private equity, commodities, funds or banking. Asset class alone does not establish fit. The same warehouse can support a credible tokenized secured note, an impractical direct co-ownership scheme or a simple bilateral loan that gains nothing from a token. The decision belongs to issuers and operating teams before it belongs to technologists. This article provides a European framework for making it.
A token is a programmable representation of a value or right. Its strongest use is not merely digitising a certificate. It is connecting actions that are separated across databases, organisations and settlement processes. The Bank for International Settlements’ 2025 analysis describes the potential in bringing money and other assets onto programmable platforms so that messaging, reconciliation and asset transfer can operate as one process.
For a proposed product, that potential should be translated into a named operational change. Does the token become the authoritative holder record, or is it reconciled to one? Can an eligibility rule travel with the instrument instead of being checked manually at each transfer? Can delivery and payment become conditional on one another? Can distributions, redemptions and cancellations use the same ownership data? A business case that cannot identify the old process, the new process, the accountable operator and the exception path is not yet a tokenization case.
Four recurring frictions justify closer analysis:
Tokenization may address one or more of these. It does not make an asset valuable, perfect legal title, create investor demand or remove regulated intermediaries whose responsibilities remain necessary.
Asset owners, developers and operating companies can be good candidates when they need to issue a clearly documented financial claim to several investors and administer it over time. The instrument might be an SPV note, company share, profit-participation security or another contractual entitlement. The sponsor benefits when the same controlled workflow can support investor onboarding, subscriptions, issuance, transfer approval, payments and maturity.
The decisive variable is repeatability. A sponsor planning a programme of private-credit or real-asset issuances can spread legal, technical and operational infrastructure across several products. Standardised eligibility rules and registry procedures become valuable because they are exercised repeatedly. A one-off issuer with five known investors and no expected transfers may find that company records, bank payments and conventional documents are simpler.
The investor’s right must come first. “A token backed by property” does not say whether the holder owns a share, has a secured debt claim, ranks behind a mortgage lender or merely receives a contractual payment linked to sale proceeds. The token should implement an enforceable instrument rather than fill gaps in it. Lympid’s guide to the legal and operating model for asset tokenization explains the required alignment between the asset, claim, authoritative record and servicing chain.
Fund managers and administrators have a different reason to tokenize. They are not turning each portfolio asset into a separately owned fraction. They may be representing units or shares in a collective vehicle and using digital infrastructure to improve subscriptions, commitments, capital calls, transfer controls, distributions and redemptions.
This can be useful for closed-ended private-market funds with multiple closings, many eligible investors and long operating lives. The token may support a cleaner investor register and controlled transfers, while the manager, administrator, depositary or custodian continues to perform the responsibilities attached to the fund. It is less compelling when a fund has a small stable investor base, infrequent dealing and an established administrator whose system already handles the process efficiently.
A fund cannot be designed backwards from a token standard. The sponsor must first decide whether capital is pooled under a defined investment policy, who exercises discretion, how assets are valued, what liquidity rights exist and which record controls ownership. The comparison between a fund, a standalone instrument and tokenized fund units is therefore an economic and regulatory decision before it is a technology decision.
Banks, central securities depositories, trading venues and other financial-market infrastructures pursue tokenization at a different scale. Their value case is integrated issuance, collateral, trading and settlement—not retail fractionalisation. Conditional delivery-versus-payment, automated collateral movements and programmable compliance can reduce sequential processing when assets and trusted settlement money operate on compatible infrastructure.
European activity is moving beyond experiments, but it remains uneven. In August 2026, the ECB reported that the referenced volume of tokenised assets had risen from €4.7 billion at the end of the first quarter of 2025 to €23.3 billion at the end of the first quarter of 2026. The ECB has also emphasised that fragmentation and access to trusted settlement money remain constraints. Its April 2026 analysis of Europe’s digital capital market described a heterogeneous market and rapid growth in tokenized money-market funds, rather than one unified market.
The lesson for institutions is specific: tokenization fits where participants can redesign a shared process, not where each participant builds an isolated ledger. Interoperability, finality, cash settlement, legal certainty and operational resilience determine whether a pilot can scale.
Payment and deposit use cases require their own analysis. The European Banking Authority’s report on tokenised deposits treats a deposit recorded on DLT as a depositor’s claim against a credit institution; changing the ledger does not, by itself, change the fundamental nature of that claim. Tokenized deposits may support programmability and new settlement models, but they remain banking products with the associated institutional and regulatory perimeter.
A non-bank should not describe an asset-backed token as a deposit merely because it targets stable value or instant transfers. The issuer, reserve arrangement, redemption promise and holder rights determine whether the instrument resembles a deposit, electronic money token, asset-referenced token, security or another claim. This is one reason broad claims that tokenization is “for every business” are misleading.
Consider a lending platform that originates secured SME loans through ring-fenced issuing vehicles. It expects twelve issuances each year, admits several hundred professional or eligible investors, distributes interest quarterly and permits controlled bilateral transfers. Each note series has its own borrower, collateral, maturity and covenants, but the investor onboarding, registry, payment and transfer processes repeat.
This is a credible tokenization candidate. A shared infrastructure can enforce issuance caps, admit only approved wallets, reconcile subscriptions to minted notes, maintain the holder record, allocate quarterly payments and block transfers that breach eligibility rules. The economic and legal work remains series-specific: underwriting, security perfection, cash-control agreements, servicing, covenant monitoring and workouts. The technology earns its place because it standardises recurring administration without pretending that credit risk or enforcement has disappeared.
Two decision points remain. First, the issuer must state whether the on-chain record is legally authoritative or reconciled to a registrar. Second, the transfer function must have a lawful execution and settlement route. Technical transferability alone does not create secondary liquidity.
Now consider an SPV formed to acquire one collectible asset from a known seller. Five investors will fund the purchase, hold for seven years and decide unanimously when to sell. No new investors, interim transfers or recurring issuances are expected. A specialist stores and insures the asset, while one administrator distributes annual reports.
A token may be technically possible, but its economic case is weak. The investors can hold conventional shares or notes, the cap table rarely changes and the product has few lifecycle events to automate. Adding wallets, key recovery, smart-contract governance, reconciliation and vendor dependencies may increase rather than reduce operational risk. If marketing later promises “liquidity,” the project also creates an expectation that the structure cannot support.
The answer could change if the sponsor builds a repeatable platform for many assets, expands the investor base, introduces controlled transfers and uses one operating model across the programme. Tokenization suitability is not a permanent property of the asset; it depends on the transaction and its expected lifecycle.
Tokenization should normally be rejected or postponed in five situations:
A smaller denomination or a transferable smart contract can be useful, but neither establishes a market. In June 2025, ESMA’s review of the DLT Pilot Regime reported only three authorised infrastructures and minimal live trading activity, while identifying interoperability and central-bank-money access as continuing frictions. The evidence supports selective implementation, not automatic adoption.
Investors benefit only when the operating model improves access or administration without obscuring the claim. Useful changes may include lower viable subscription sizes, faster onboarding, clearer ownership records, more frequent reporting, controlled transfers and more predictable distributions. Those improvements are conditional. Smaller units do not make a risky asset diversified, a digital wallet does not guarantee safekeeping of the legal right, and continuous technical availability does not ensure an executable trade.
Before subscribing, an investor should be able to verify six points: the instrument and issuer; the asset or cash-flow source; ranking and security; the authoritative ownership record; the payment and exit mechanics; and the regulated firms responsible for distribution, custody or trading. These questions are more important than the blockchain selected.
A commercially strong tokenization case must still fit the legal perimeter. Under ESMA’s guidelines on classifying crypto-assets as financial instruments, tokenized financial instruments remain financial instruments for regulatory purposes, and authorities should apply a technology-neutral, substance-over-form approach. Shares, bonds, fund units and derivatives do not become MiCA products merely because they use DLT.
Classification determines the offer documents, issuer constraints, distribution permissions, product-governance duties, custody and registry arrangements, and any trading infrastructure. National company, property, insolvency and tax law also affect the enforceability of the promised right. The latest European legal-tokenization framework for issuers explains how to map the instrument and activities separately.
This is general information rather than legal, tax, investment or financial advice. A live transaction requires analysis of its governing law, issuer, target investors, distribution countries and service-provider permissions.
| Gate | Evidence that supports tokenization | Reason to pause |
|---|---|---|
| Right | A precise share, note, fund unit or contractual entitlement | Marketing language substitutes for enforceable terms |
| Scale | Many holders, repeated issuances or recurring lifecycle events | One bilateral transaction with little expected change |
| Record | A defined authoritative ledger and correction procedure | On-chain and legal records can diverge without priority rules |
| Control | Eligibility, issuance and transfer rules can be executed consistently | Controls depend on manual work that the token cannot observe |
| Settlement | Asset and cash movements can be coordinated through credible rails | The token settles while payment and legal title remain disconnected |
| Operations | Named parties handle servicing, incidents, defaults and exit | No accountable operator exists after launch |
A project that passes all six gates may justify detailed design. Passing only the “right” gate means an instrument can be tokenized, not that it should be. Passing only the “scale” gate means the project has volume, not a coherent legal product.
Different users need different delivery models. A bank or licensed asset manager with its own compliance, administration and custody relationships may purchase modular registry or issuance technology. An asset sponsor without those functions may need coordinated product structuring, onboarding, distribution controls, payments and lifecycle administration. An integrated white-label investment platform can reduce handoffs when responsibilities are explicit.
Lympid is relevant to European issuers that need financial-product structuring, tokenization technology and regulated distribution infrastructure coordinated in one implementation. It does not make every asset suitable for tokenization, replace issuer due diligence or guarantee liquidity. The useful starting point is narrower: identify a legally sound claim, a recurring coordination problem and a measurable operating improvement. If those three elements are present, tokenization may be the right architecture. If one is missing, the project should solve that dependency before building the token.