An issuer wraps a bond in a token and lists it on a blockchain-based exchange. The platform operator assumes the token classification turns on the technology – that because the instrument lives on-chain, it escapes traditional securities rules. The regulator disagrees: the asset remains a security, the offer remains a public offer, and the platform is operating an unauthorised trading venue. The assumption that tokenization changes legal substance is the most persistent mistake in digital-asset compliance – and the costliest.
The regulatory principle is simple and near-universal: same asset, same rules. If the underlying instrument confers the rights of a security – profit participation, voting rights, a claim on enterprise performance – then the tokenized version is also a security, regardless of the technology used to record ownership. This principle appears explicitly in guidance from ESMA, the SEC, MAS, FINMA and every other regulator facing the tokenization question. Yet operators routinely launch tokenized instruments believing a whitepaper disclaimer or a utility-framing narrative will override substance. The result is unregistered offers, unlicensed trading platforms and enforcement actions that unwind entire business models. This analysis explains why tokenization does not change classification, what supervisors expect at each stage from issuance through secondary trading, and how to structure the compliance stack when the underlying is a security. It is written for general counsel, compliance officers and operators building tokenization platforms or advising on token structure – readers who understand blockchain mechanics and need the legal answer that holds cross-border.
Same asset, same rules: the principle
The same asset, same rules doctrine means that the legal classification of an instrument is determined by the rights it confers, not by how those rights are recorded. If a token represents ownership of a share, a bond or a collective-investment interest, it is classified as a security in the same way that a paper certificate or a book-entry record would be. The blockchain is a ledger technology, not a legal re-characterisation device. This principle appears in the European Securities and Markets Authority's advice on distributed ledger technology in 2016, in the Swiss FINMA ICO guidance of 2018, in the Singapore MAS guide to digital token offerings of 2020 and in the US SEC's repeated statements that "a token does not avoid securities classification simply because it uses blockchain".
The principle extends to every stage of the instrument's lifecycle. At issuance, the offer of a tokenized security is subject to the same prospectus, registration and disclosure rules that govern conventional securities offerings – whether that is a prospectus under the EU Prospectus Regulation, a registration statement under the US Securities Act, or an offering document under the MAS securities framework. At secondary trading, a platform listing tokenized securities must meet the licensing and operational requirements of a trading venue, an exchange or a multilateral trading facility – the same thresholds that apply to venues listing conventional equities or bonds. At custody, the holder's rights are governed by the law that determines beneficial ownership and security interests in the relevant jurisdiction – which for tokenized instruments often means a cross-border conflict-of-laws analysis because the issuer, the platform, the investor and the custodian may each sit in a different country.
Where operators make the mistake is in assuming that a utility narrative or a whitepaper label can override the substance of rights. A token that promises profit-sharing tied to enterprise performance is a security regardless of whether the whitepaper calls it a "utility token" or describes it as access to a platform. The test is not the label; it is the economic reality. If the holder's expectation is a return derived from the promoter's efforts – the framework from the US Howey test, now applied analogously across most common-law and civil-law jurisdictions – then the instrument is a security and must be treated as one at every point in the chain. In our cross-border practice, we have seen platforms launch with utility-framed instruments only to discover, after six months of operation, that every transaction executed on the venue constitutes dealing in securities without authorisation. The cost at that stage is not the compliance build; it is unwinding the business.
When a token is a security: the classification tests
A tokenized instrument is classified as a security when it confers one or more of the following rights: a claim on profits or revenue from an enterprise, voting or governance rights in a business entity, a contractual entitlement to interest or dividends, a share in the residual value of an undertaking or a collective-investment interest where the holder's return depends on the pooling of capital or the efforts of a manager. These are the core markers that regulators use across jurisdictions – adapted from the US Howey doctrine, the EU concept of a transferable security, and the common-law definition of shares, debentures and units in collective-investment schemes.
The most common test in common-law jurisdictions derives from SEC v W.J. Howey Co.: an investment contract exists where there is an investment of money in a common enterprise with an expectation of profits derived predominantly from the efforts of others. The four elements are cumulative. If the token represents capital staked in an enterprise, if the holder's return depends on the performance of that enterprise rather than on the holder's own efforts, and if there is a promoter or a management team whose skill or activity drives the outcome, the instrument is classified as a security. The test is functional: it looks at economic substance, not at whether the issuer calls the token a utility instrument or lists it on a decentralized exchange. In our licensing practice, we routinely advise issuers who believed that launching on-chain or labelling the token as a governance instrument would place it outside securities perimeters – only to find that the rights embedded in the smart contract meet every element of the Howey test.
Under MiCA, which took full effect for crypto-asset service providers in December 2024, a token is classified as a security if it falls within the definition of a financial instrument under MiFID II – which includes transferable securities (shares, bonds, units in collective-investment undertakings), money-market instruments and derivatives. MiCA explicitly states that tokens qualifying as financial instruments are excluded from the MiCA regime and remain subject to the full MiFID framework – meaning prospectus requirements, trading-venue authorisation and conduct-of-business rules. The MiCA regime applies only to crypto-assets that are not securities – asset-referenced tokens, e-money tokens and "other" crypto-assets. The binary is strict: if the token confers the rights of a financial instrument, it is regulated under MiFID, not under MiCA. An issuer cannot opt into the lighter MiCA regime by adding utility features to a security token.
Switzerland's FINMA applies a three-category taxonomy – payment tokens, utility tokens and asset tokens – but clarifies that asset tokens are securities if they represent a participation right in an enterprise, a debt claim or a derivative. Even a hybrid instrument that combines utility and asset features is treated as an asset token where the asset component is non-trivial. The classification drives licensing: a platform trading asset tokens must hold a securities dealer licence or operate through a regulated exchange; an issuer offering asset tokens must produce a prospectus unless an exemption applies. Singapore's MAS follows a similar principle: a digital token is classified as a security if it represents a share, a debenture or a unit in a collective-investment scheme under the Securities and Futures Act. The classification is tested at the time of offer, and again at secondary trading – because a token initially issued as utility may later be classified as a security if the economic arrangement evolves to include profit-sharing or collective-investment characteristics.
Disclosure and prospectus requirements at issuance
When a token is classified as a security, the issuer must comply with the prospectus and disclosure regime applicable to public offers in the relevant jurisdiction. In the European Union, that means the Prospectus Regulation: an offer to the public or an admission to trading on a regulated market requires an approved prospectus unless an exemption applies. The content requirements are the same as for any conventional security – issuer financials, risk factors, rights attached to the instrument, use of proceeds – and the prospectus must be approved by the national competent authority before the offer begins. A whitepaper is not a substitute for a prospectus. A whitepaper that describes the token's technical mechanics without meeting the content and approval requirements of the Prospectus Regulation does not discharge the issuer's disclosure obligation.
The prospectus exemptions available for conventional securities also apply to tokenized securities. Under the Prospectus Regulation, an offer is exempt from the prospectus requirement if it is addressed solely to qualified investors, if it is addressed to fewer than 150 persons per member state (excluding qualified investors), or if the total consideration in the EU is below one million euro over twelve months. The exemptions are narrow and cumulative – an issuer that exceeds any threshold for a single criterion must produce a prospectus even if other criteria fall within the exemption. In our structuring practice, we have advised issuers who launched a token sale to 120 retail investors in one member state, believing the sub-150 exemption would apply, only to discover that they had marketed the token in five member states – pushing the aggregate investor count over 600 and triggering the full prospectus obligation retroactively.
In the United States, an offer of tokenized securities is subject to registration under the Securities Act of 1933 unless an exemption applies. The registration process requires a Form S-1 filing with detailed financials, risk factors and a description of the business – the same process for any initial public offering. The principal exemptions are Regulation D (Rule 506(b) for private placements to accredited investors without general solicitation, Rule 506(c) for private placements with general solicitation where all purchasers are verified accredited investors), Regulation A (a mini-IPO process allowing offers up to a stated threshold with an offering circular approved by the SEC) and Regulation S (offers made outside the US to non-US persons). Each exemption carries strict conditions – for example, Rule 506(b) prohibits any general solicitation or advertising, while Regulation A requires a qualified offering circular and state-by-state Blue Sky compliance. A token issuer that advertises publicly or lists on a decentralized exchange before closing the offering will typically disqualify itself from the Rule 506(b) exemption, leaving registration as the only path.
Singapore's MAS requires an issuer of digital tokens classified as securities to lodge a prospectus with MAS before the offer, or to satisfy one of the exemptions under the Securities and Futures Act – such as offers to institutional or accredited investors only, offers where the consideration for each investor exceeds a specified threshold, or small offers below an aggregate cap. The prospectus must meet the content standards in the Securities and Futures Regulations and must be registered with MAS. A failure to register or to fit within an exemption means the offer is unlawful, and the issuer faces potential enforcement and investor rescission rights. Critically, MAS has stated that the mere fact of issuing a token on a blockchain does not exempt the issuer from prospectus requirements – technology is not a carve-out.
Trading venue licensing for secondary markets
A platform that operates secondary trading in tokenized securities must hold the licence applicable to a securities trading venue in the jurisdiction where it provides the service. Under MiFID II, a venue that brings together multiple third-party buying and selling interests in a way that results in a contract is classified as a multilateral trading facility (MTF) or, if it matches orders using non-discretionary rules, a regulated market. Both categories require authorisation as an investment firm or a market operator, compliance with pre-trade and post-trade transparency requirements, and adherence to the conduct-of-business and organisational rules in MiFID. The fact that the platform operates on a blockchain or uses smart contracts for settlement does not change the classification: if it provides order-matching and trade execution, it is a trading venue and must be licensed.
The licensing threshold turns on the platform's role. If the platform simply provides technology – a smart contract that enables peer-to-peer trades without the platform intermediating or matching orders – then it may fall outside the regulated-venue definition. But the line is narrow. If the platform maintains an order book, if it sets trading rules or if it takes custody or control of the assets at any point in the process, it will typically cross the threshold into regulated activity. ESMA has clarified that even a decentralized exchange may be classified as an MTF where it performs matching, order management or trade confirmation functions. The absence of a corporate entity does not exempt the platform: ESMA's position is that regulatory obligations attach to the persons who operate or control the protocol, regardless of whether that control is exercised through a foundation, a DAO or an anonymous development team.
In the United States, a platform trading tokenized securities must register as a national securities exchange under Section 6 of the Securities Exchange Act or operate as an alternative trading system (ATS) under Regulation ATS. An ATS is exempt from exchange registration but must register as a broker-dealer, must comply with Form ATS filing and update requirements, and must meet operational and fair-access standards. The SEC has brought enforcement actions against platforms that matched orders in tokenized securities without registering as an exchange or an ATS – notably cases where the platform argued that because it operated on a blockchain and called itself decentralized, it did not meet the "exchange" definition. The SEC rejected that argument: the statutory definition turns on whether the platform brings together buyers and sellers and uses established non-discretionary methods to execute trades. Technology and nomenclature are irrelevant.
Singapore requires a platform trading in securities (including tokenized securities) to hold a capital markets services licence for dealing in securities or operating an organised market. MAS has stated that a platform facilitating secondary trading of digital tokens classified as securities is subject to the same licensing thresholds as a conventional securities broker or exchange. Where the platform holds or controls customer assets, it must also meet custody and client-asset segregation requirements. Hong Kong's SFC follows a similar approach: a platform trading security tokens must be licensed for Type 1 (dealing in securities) and potentially for Type 7 (automated trading services) regulated activities. The licensing process includes capital requirements, fit-and-proper assessments for controllers and key personnel, and ongoing compliance with the SFC's conduct and operational standards.
Custody, beneficial ownership and conflict of laws
When an investor holds a tokenized security, the legal question of who owns the asset and where that ownership is determined becomes complex because the token, the issuer, the platform and the investor may each sit in different jurisdictions. Beneficial ownership of a tokenized security is governed by the law applicable to the instrument – which in many cases is the law of the jurisdiction where the issuer is incorporated or where the token is "located" for conflict-of-laws purposes. But determining the location of a token on a distributed ledger is not straightforward: there is no single physical situs, and domestic conflict rules were written before blockchain existed.
Under the UNIDROIT principles on digital assets and private law (adopted in 2023 but not yet in force), the applicable law for proprietary questions may be determined by the law chosen by the parties in the token's governing terms, or by the law of the jurisdiction most closely connected with the token – which could be the law of the place where the issuer is established, where the majority of ledger nodes operate, or where control is exercised. Many tokenization projects specify in the instrument's terms that the applicable law is the law of the issuer's jurisdiction, which provides certainty for ownership and priority questions – but that choice is effective only if the relevant jurisdiction recognises party autonomy for proprietary matters and if no mandatory rule overrides the choice.
For custody purposes, a regulated custodian holding tokenized securities must meet the same segregation, record-keeping and client-asset protection standards that apply to custodians of conventional securities. In the EU, MiFID requires investment firms holding client financial instruments to segregate those instruments from the firm's own assets and to hold them in a way that ensures they are identifiable and returnable to clients in the event of the firm's insolvency. A custodian holding tokenized securities on-chain must ensure that the private keys or multi-signature controls that represent custody of the token are held in a manner that meets the segregation standard – which typically means wallets segregated by client, robust key-management procedures and regular reconciliation of on-chain balances against client records. Where the custodian sub-custodies to another entity – for example, using a third-party wallet provider – then MiFID requires due diligence on the sub-custodian and written agreement on asset protection.
A practical problem arises where the token is recorded on a public blockchain and the custodian does not hold exclusive control. If the token's smart contract allows the issuer or a protocol administrator to freeze, burn or reassign the token without the custodian's consent, then the custodian may not have sufficient control to meet the regulatory standard of holding the asset "on behalf of" the client. In one structuring engagement, we advised a fund custodian that had agreed to hold tokenized bonds issued on a permissioned ledger; the issuer retained contract-level authority to reverse any transfer if it determined the transfer violated securities law. The custodian's regulator took the position that because the custodian could not prevent the issuer from unilaterally reassigning the token, the custodian was not in fact holding the asset – meaning the arrangement did not meet the custody standard and the fund was effectively un-custodied. The resolution was to renegotiate the smart-contract governance so that any issuer action required a multi-signature approval from the custodian.
Cross-border complications: jurisdiction stacking
The same-asset-same-rules principle operates jurisdiction by jurisdiction, which creates complexity where the tokenization structure spans borders. An issuer incorporated in Switzerland issues tokenized bonds under Swiss law; the bonds are marketed to investors in the EU; the secondary trading platform is operated from Dubai; the custodian is licensed in Malta; the settlement layer is a public blockchain with nodes distributed globally. Which jurisdiction's prospectus, trading-venue and custody rules apply? The answer is: potentially all of them, layered.
At issuance, the offer is subject to the prospectus regime in each jurisdiction where the offer is made to the public or where the token is admitted to trading on a regulated market. If the Swiss issuer markets the bonds to EU retail investors, it must produce a prospectus approved by a national competent authority in the EU (or satisfy a prospectus exemption in each member state where it offers). If it markets to US investors, it must register under the Securities Act or fit within a Rule 506 or Regulation A exemption. The issuer cannot avoid the registration obligation by claiming the offer is "decentralized" – the SEC's position is that if the issuer or its agents conduct promotional activity directed at US investors, the offer is made in the US and registration is required unless an exemption applies.
At secondary trading, the platform is subject to the trading-venue licensing regime of the jurisdiction where it provides services. Under the EU's approach, a platform that provides services into the EU – meaning it actively solicits EU investors or makes its order book accessible to them – is providing investment services in the EU and must be authorised under MiFID or must passport in from another member state. The Dubai regulator applies a similar test: a platform offering services to clients in the UAE must be licensed by VARA or by ADGM/FSRA, depending on where the platform operates. The result is that a tokenized-securities platform with a global user base may need authorisation in multiple jurisdictions – or must implement strict geo-blocking and investor verification to limit service provision to jurisdictions where it holds the appropriate licence.
The custody question is determined by where the custodian is licensed and where the investor is located. If the custodian is a Malta-licensed investment firm and the investor is an Italian resident, then MiFID client-asset rules apply: the custodian must segregate the investor's tokenized securities from the custodian's own assets and must hold them in a way that ensures the investor's claim is protected in the custodian's insolvency. If the custodian sub-custodies to an offshore entity – for example, a BVI trust company holding the private keys – then the Italian investor's claim may be governed by BVI trust law and BVI insolvency rules, creating a conflict-of-laws risk that many retail investors do not understand and that the custodian must disclose.
Common operator mistakes and their consequences
The most common mistake is treating a whitepaper as a compliance document rather than as a marketing narrative. A whitepaper that describes the token as a "utility instrument" or emphasises the technical features of the protocol does not override the economic substance of the rights conferred. If the token gives the holder a profit share, a right to vote on business decisions or a claim on enterprise value, then it is a security regardless of the whitepaper label. Operators who rely on the whitepaper narrative without conducting a legal classification analysis face enforcement risk – either from the regulator that has jurisdiction over the offer or from the regulator that has jurisdiction over the secondary-trading platform. The enforcement action typically results in a cease-and-desist order, a requirement to unwind all sales and offer rescission to investors, and a civil or criminal penalty for operating without authorisation.
A second mistake is assuming that decentralization changes the regulatory classification. The SEC, ESMA and MAS have each stated that the fact that a protocol is decentralized – meaning no single entity controls all aspects of the token's issuance or trading – does not exempt the token or the platform from securities regulation. The analysis turns on who promoted the token, who benefits from the sale, and whether there is a group of persons whose efforts drive the token's value. If a development team or a foundation marketed the token, collected proceeds from the sale and continues to build the protocol, then that team or foundation is the issuer for regulatory purposes, and the token is classified based on the rights it confers. In a 2023 enforcement matter, a US-based project argued that because the protocol was governed by a DAO and the development team had transferred control to token holders, the project was decentralized and the token was not a security. The SEC's position was that the initial sale – when the development team controlled the protocol and investors bought tokens expecting the team's efforts to increase value – was a securities offering, and the subsequent decentralization did not retroactively cure the violation.
A third mistake is launching secondary trading before the issuer has satisfied the prospectus or registration obligation at the primary offering. Many tokenized-securities projects issue the token to early investors under a private-placement exemption and then list the token on a decentralized exchange or a tokenization platform for secondary trading. If the listing occurs before the issuer has registered a resale prospectus or before the holding period for the private-placement exemption has expired, then each secondary sale may constitute a new unlawful offer. In the US, securities acquired in a Regulation D private placement are restricted securities and cannot be resold publicly unless the issuer registers the resale or the holder satisfies the conditions of Rule 144 (including a holding period and volume limits). A platform that lists those restricted securities for trading is facilitating unregistered resales – and both the platform and the sellers may be liable.
Where operators discover post-launch that a token is classified as a security and that the offer or the trading platform was not compliant, the remediation cost is significant. The issuer must typically halt the offer, produce a retroactive prospectus or registration statement, offer rescission to all investors who bought during the non-compliant period, and pay a civil penalty. The platform must shut down trading in the token, apply for the appropriate trading-venue licence, and rebuild its compliance infrastructure to meet the licensing standard. For a platform that has been operating for months or years and has built a user base, the cost of retrofitting compliance can exceed the cost of building the platform correctly from the outset by a factor of five to ten. In a 2022 engagement, we advised a tokenization platform that had listed five tokenized real-estate instruments without checking classification; after a supervisory inquiry, the platform discovered that all five were collective-investment schemes under the Securities and Futures Act. The remediation process took eighteen months, required a capital injection to fund the licensing application, and resulted in the platform shutting down three of the five instruments because the underlying issuers could not produce compliant prospectuses.
Decision matrix: classification to compliance stack
Profile A: token confers voting rights in a corporate entity and a share of residual profits – clear security. Compliance stack: issuer produces a prospectus (or satisfies a private-placement exemption); the primary offer is conducted through a licensed broker or platform authorised for securities distribution; secondary trading is restricted to platforms holding a trading-venue or broker-dealer licence; custody is provided by a regulated custodian meeting client-asset segregation standards. Key risk: if the token is marketed to retail investors in multiple jurisdictions, the issuer must navigate the prospectus regime in each jurisdiction or implement strict investor qualification to limit the offer to jurisdictions where an exemption is available.
Profile B: token confers a right to interest payments from a pool of underlying receivables – structured as a bond or a collective-investment unit, therefore a security. Compliance stack: issuer must produce a prospectus or offering document meeting the content requirements for debt securities or collective-investment schemes; the offer must be registered or fit within a private-placement exemption; the secondary-trading platform must be licensed as a venue or an ATS; if the token pays periodic distributions, the platform or the issuer must withhold tax where required. Key risk: if the receivables pool is managed by a third party, the token may also be classified as a unit in a collective-investment scheme, which triggers additional licensing for the manager and additional disclosure requirements for the pooling arrangement.
Profile C: token initially issued as a pure utility instrument (access to a platform service) but later evolves to include profit-sharing – starts as a non-security, becomes a security. Compliance stack: at launch, if the token is genuinely utility (no expectation of profit from others' efforts), it may fall outside securities perimeters and be subject only to the lighter MiCA CASP regime (EU) or no specific financial-services licensing (other jurisdictions). But when the issuer introduces profit-sharing or governance rights – for example, through a protocol upgrade or a staking mechanism that distributes enterprise revenue – the token is reclassified as a security from the point of the change. The issuer must then halt secondary trading, produce a prospectus for the new instrument, and ensure that any platform listing the token obtains a securities trading-venue licence. Key risk: the reclassification is often overlooked until a supervisory inquiry, at which point the issuer and the platform face retroactive compliance and potential enforcement for operating without authorisation.
Profile D: token issued as a pure payment instrument (no rights beyond transferability) but marketed with language suggesting value will increase based on the development team's efforts – may be classified as a security under the Howey test even if the contractual rights are minimal. Compliance stack: if a regulator determines that the marketing created an expectation of profits from the team's efforts, then the token is a security despite the absence of formal profit-sharing or governance rights. The issuer must then produce a prospectus or satisfy a private-placement exemption; the platform must be licensed for securities trading; and the marketing materials must be revised to remove any suggestion of investment return. Key risk: this is the profile that creates the most post-launch enforcement, because the issuer often assumes that a payment token is outside securities perimeters and does not conduct a Howey-style analysis of the marketing narrative. The SEC has brought multiple enforcement actions on this fact pattern.
When to engage counsel: the preventive checkpoint
The preventive checkpoint is before the issuer finalises the token design and before the platform commits to listing tokenized instruments. Classification is a threshold question: if the answer is that the token is a security, then the entire compliance stack – prospectus, trading-venue licence, custody structure – must be built to meet securities standards. Retrofitting that stack after launch is typically five to ten times more expensive than building it correctly from the outset. In our licensing and structuring practice, we conduct classification assessments at the design stage – testing the proposed rights against the Howey test, the MiFID financial-instrument definition, and the local-law definitions of shares, debentures and collective-investment interests across the jurisdictions where the issuer plans to offer or where the platform will operate.
A classification assessment maps the rights conferred by the token (voting, profit-sharing, management participation, redemption rights), the relationship between the investor and the promoter (does value derive from the promoter's efforts?), the marketing narrative (does the whitepaper or promotional material create an expectation of profit?), and the technical mechanics (is the token truly transferable peer-to-peer, or does the platform intermediate?). The output is a legal opinion on classification and a roadmap for compliance: if the token is a security, we map the prospectus path, the private-placement exemptions available across the target jurisdictions, the trading-venue licensing requirement for the platform, and the custody and tax implications. If the token is not a security, we document the basis for that conclusion and flag the design features that must not change – because any evolution toward profit-sharing or collective-investment characteristics will trigger reclassification.
The analysis must be cross-border. A token that qualifies for a prospectus exemption in Switzerland may still require registration in the US if marketed to US investors; a platform licensed in Malta can passport across the EU under MiFID but must apply separately for authorisation in Singapore or Hong Kong if it offers services there. We work with allied counsel in the target jurisdictions to map the layered compliance stack and to identify where the issuer or the platform can structure around a licensing requirement – for example, by limiting the offer to qualified investors only, by geo-blocking retail access from high-threshold jurisdictions, or by using a distributor that already holds the relevant licence rather than applying for a new licence at the issuer or platform level.
The business model that treats tokenization as a regulatory arbitrage – that assumes on-chain instruments escape traditional licensing because they are "crypto" – fails at first supervisory contact. Every major regulator has now stated that tokenization does not change classification, and enforcement actions are frequent. For a scoped classification and compliance assessment before you commit to the token structure, write to info@oboluslaw.com or reach us through the contact page.
Objection handler: "We called it a utility token"
A common assumption is that calling a token a "utility token" in the whitepaper settles the legal classification – that the label, combined with a clause stating "this token is not a security," is sufficient to place the instrument outside securities perimeters. This assumption is incorrect. The legal classification of a token is determined by the substance of the rights it confers, not by the name the issuer chooses or the disclaimer the whitepaper contains. If the token gives the holder a share of profits, a claim on enterprise value or governance rights that affect business decisions, then it is classified as a security under the laws of most jurisdictions – regardless of what the issuer calls it.
The principle comes from the US Supreme Court's decision in Reves v Ernst & Young (1990), which held that the label parties attach to a transaction does not control its legal classification – the court looks to the economic reality and the reasonable expectations of the parties. The same principle applies to tokenized instruments. If an investor buys a token expecting a profit from the efforts of a development team, and if the whitepaper describes a roadmap where the team will build features and grow adoption to increase the token's value, then the economic reality is an investment contract – and the instrument is a security under the Howey test, even if the whitepaper calls it a utility token. ESMA and MAS have each stated the same principle: the label and the technology are not determinative; the classification turns on the rights and the economic substance.
In our structuring assessments, we have reviewed dozens of whitepapers that describe a token as utility but then set out a profit-sharing mechanism, a staking reward derived from protocol revenue or a governance structure where token holders vote on business strategy. Each of those features converts the token into a security. The way to preserve a utility classification is to ensure that the token confers only access or consumption rights – the right to use a service, to redeem for a defined good, or to participate in a decentralized network without any expectation of profit from others' efforts – and to ensure that the marketing does not create an investment narrative. If the whitepaper includes a tokenomics section showing projected value appreciation, a roadmap where the team's development is the driver of value, or a "benefits to holders" section listing potential profit, then the token is classified as a security, and the utility label is irrelevant.
Case study: a tokenized-bond programme that stalled
In a recent cross-border engagement, a financial-services group approached us after a tokenized-bond issuance stalled mid-programme. The issuer – a holding company incorporated in Luxembourg – had issued tokenized bonds representing senior secured debt, recorded on a permissioned Ethereum sidechain. The bonds were marketed to institutional and high-net-worth investors in the EU and Switzerland, with settlement and custody provided by a third-party platform licensed as a central securities depository in a member state. The issuer believed that because the bonds were tokenized and settled on-chain, they fell outside the Prospectus Regulation and could be offered under the lighter disclosure regime applicable to private placements. The issuer did not produce a prospectus. Six months into the programme, the national competent authority in Luxembourg opened a supervisory inquiry and took the position that the tokenized bonds were transferable securities and that the offer to more than 150 non-qualified investors per member state triggered the prospectus requirement – which had not been satisfied.
The issuer's error was assuming that tokenization changed the classification. The bonds were debt securities – they conferred a contractual right to interest and repayment, they were transferable and they were marketed as an investment. The fact that ownership was recorded on a blockchain rather than in a book-entry system did not change the legal nature of the instrument: under the Prospectus Regulation, a bond is a bond regardless of the technology used to record ownership. The issuer had relied on the private-placement exemption (offers to fewer than 150 persons per member state, excluding qualified investors), but the marketing had reached more than 200 investors in Germany alone, and the offer had been promoted through a webinar that was accessible to the public – which the regulator determined constituted general solicitation and disqualified the private-placement exemption.
The remediation required the issuer to suspend all further offers, produce a prospectus compliant with the Prospectus Regulation, obtain approval from the Luxembourg CSSF, and offer rescission to all investors who had bought bonds during the non-compliant period. The prospectus process took nine months; the rescission cost was significant because the bonds had declined in secondary-market value and investors exercised their right to return the bonds at the original purchase price. The lesson for the issuer – and for the platform that had facilitated the issuance – was that tokenization does not exempt an instrument from securities regulation; the same-asset-same-rules principle applies in full, and the compliance build must match the substance of the instrument from the outset.
Related practices at OBOLUS
Related at OBOLUS
- Token Offerings & Securities – Classification, prospectus strategy and cross-border compliance for issuers and platforms listing tokenized instruments.
- Data Protection and Liability in DePIN Networks – Privacy and liability framing where blockchain infrastructure intersects with data-protection regimes.
- Utility Token Legal Opinion in Nigeria – Jurisdiction-specific classification and compliance for token launches outside the major hubs.
FAQ
Is my token a security under this regime?
Your token is classified as a security if it confers profit-sharing rights, voting rights in a business entity, a contractual entitlement to interest or dividends, or a collective-investment interest where the holder's return depends on the efforts of a promoter or management team. The classification is tested against the law of each jurisdiction where you offer or list the token – most commonly the Howey test in common-law jurisdictions and the MiFID financial-instrument definition in the EU. The label in your whitepaper does not control the classification; the test is the economic substance of the rights. A lawyer conducts the assessment by mapping the rights conferred, the relationship between the investor and the promoter, the marketing narrative, and the technical mechanics of the token against the relevant legal tests. If the token meets the definition of a security in any target jurisdiction, you must structure the offer and the secondary trading to comply with that jurisdiction's securities laws.
Do I need a whitepaper or prospectus?
If your token is classified as a security, you need a prospectus that meets the content and approval requirements of the Prospectus Regulation (EU), the Securities Act (US), or the equivalent regime in your target jurisdictions – unless you fit within a private-placement exemption. A whitepaper alone does not satisfy the prospectus requirement: a prospectus must include audited financials, detailed risk factors, a description of the issuer's business, the rights attached to the instrument, and a statement of how proceeds will be used, and it must be approved by the relevant regulator before you begin the offer. If your token is not a security – genuinely a utility instrument with no profit expectation – then a whitepaper describing the technical mechanics and the use case may be sufficient, though some jurisdictions may still require the whitepaper to meet specific content or filing requirements under consumer-protection or anti-fraud rules.
What disclosure is required at launch?
The disclosure required at launch depends on whether your token is classified as a security and whether you are conducting a public offer or a private placement. For a public offer of a security, you must produce a prospectus meeting the statutory content requirements and have it approved by the relevant regulator. For a private placement, you typically must provide an offering memorandum or subscription agreement that discloses material risks, the business model, the use of proceeds, and the terms of the instrument – and you must ensure that the offer is made only to qualified or accredited investors and without general solicitation, as required by the exemption you rely on. For a token classified as a non-security, many jurisdictions require a whitepaper or disclosure document that sets out the token's utility, the technical architecture, the team behind the project, and the risks – even if no formal approval is required. The key rule is that you cannot omit material facts or make misleading statements: misrepresentation at launch exposes you to civil liability for investor losses and to regulatory enforcement regardless of whether the token is classified as a security.
About OBOLUS. OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance architecture that sits around them. Digital assets are the whole of our practice. We assess classification against the substance of rights, not the marketing label – testing token structures against Howey, MiFID and the local-law definitions of securities across the jurisdictions where you plan to offer or list. Our disputes team coordinates freezing relief and on-chain tracing across leading common-law forums – England & Wales, DIFC, Singapore, Hong Kong – when misappropriation or fraud occurs. To discuss your situation, contact info@oboluslaw.com.
By Roman Levitt, Technology & DeFi Counsel – Roman specialises in the legal classification of tokenized instruments, smart-contract governance and the regulatory treatment of decentralized protocols across major and emerging digital-asset hubs.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.