EST · MMXXVI
Home/Insights/Regulatory/Crypto Lending and Yield Products: Regulatory Classification
Token Offerings & Securities

Crypto Lending and Yield Products: Regulatory Classification

Crypto Lending and Yield Products: Regulatory Classification. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fixed-fee enga

A token issuer designs a lending pool that pays variable yield on deposited stablecoins. The token itself confers no governance rights and no claim on issuer profits. Marketing describes it as a "utility token for DeFi liquidity." Six months after launch, the regulator in a flagship jurisdiction opens an enforcement file, arguing that the yield arrangement transforms the token into a security. The label – utility – did not determine the legal classification; the economic substance did. This is the pattern seen across enforcement actions in the United States, the European Union and Asia: crypto lending and yield products are classified by the rights conferred, the investor expectation of return and the role of the issuer or operator, not by the name printed on the whitepaper.

This analysis maps how lending and yield products are classified under the major regulatory frameworks, the disclosure and authorisation triggers that flow from that classification, and the lessons extracted from past enforcement. It addresses the issuer preparing to launch, the exchange listing a yield token, and the counsel advising on cross-border compliance. The page is structured around the key decision points: what turns a lending arrangement into a regulated instrument, which disclosure obligations apply, and where the enforcement line sits today.

What makes a crypto lending product a security?

A crypto lending or yield product is treated as a security when it combines pooled funds, reliance on the efforts of the issuer or a third party, and an expectation of profit tied to those efforts. This is the test inherited from the US Supreme Court's Howey framework and reflected, with jurisdictional variation, in the EU's MiCA transferable-securities carve-out, Singapore's capital-markets test under the Securities and Futures Act, and Hong Kong's collective-investment-scheme analysis. The substance of the arrangement governs; the label applied in marketing materials carries no weight. A token marketed as a "liquidity-provision utility" is nonetheless a security if holders contribute assets to a common pool managed by the issuer, receive yield generated by the issuer's lending or staking operations, and rely on the issuer's skill to produce that return.

In practice, three structural features repeatedly trigger securities classification. First, the presence of a pooled-fund model: users deposit crypto into a single treasury or contract, and returns are paid from the collective performance of that treasury. Second, managerial discretion: the issuer or operator allocates deposited assets, sets interest rates, selects counterparties or adjusts collateral parameters – decisions on which the investor has no meaningful control. Third, yield paid from issuer activities rather than from a transparent, algorithmic process visible on-chain. Where all three features are present, regulators in the United States, the European Union and Singapore have consistently classified the arrangement as a security, regardless of the technological wrapper. Where yield is mechanically distributed by a smart contract that operates without ongoing issuer input and users retain custody of their principal, the securities classification is less certain, but the analysis still turns on whether investors are relying on the efforts of a promoter group.

The SEC's position has been tested in multiple enforcement actions. In proceedings against centralised lending platforms, the Commission argued that even if the token itself was labelled a utility, the economic arrangement – deposit, earn yield from platform operations, withdraw – satisfied all four prongs of Howey. The issuer's promise of yield, drawn from proprietary lending or trading strategies, created the expectation of profit. The issuer's management of the deposited assets supplied the entrepreneurial effort. The enforcement actions resulted in settlements with registration and refund obligations, not dismissals on classification grounds. The pattern holds: when the issuer controls the yield-generation mechanism and users contribute to a common pool, US securities law applies.

How does MiCA treat lending and yield arrangements?

Under the Markets in Crypto-Assets Regulation, the European Union carves out "crypto-assets that qualify as financial instruments" from MiCA's own-standing regime and routes them instead to the Markets in Financial Instruments Directive (MiFID II) framework. A financial instrument under MiFID includes transferable securities, which in turn capture instruments that confer rights similar to shares or bonds. A lending or yield token that gives holders a claim on returns generated by the issuer's investment or lending activity – particularly if those returns resemble dividend distributions or coupon payments – falls within the transferable-securities definition and exits MiCA. The result: the issuer must comply with the EU Prospectus Regulation, obtain MiFID authorisation if offering or managing the arrangement, and meet disclosure and ongoing-reporting obligations applicable to traditional securities.

The distinction between an asset-referenced token (ART) and a transferable security is subtle but material. An ART references a basket of fiat currencies or commodities and is stabilised against that reference; MiCA regulates it directly, with a whitepaper regime, reserve requirements and issuer authorisation. A token that references a portfolio of crypto-assets managed by the issuer and pays variable yield based on that portfolio's performance does not stabilise value – it distributes returns. That distribution mechanism pushes the token toward the transferable-securities classification. ESMA guidance clarifies that the economic substance controls: if the holder is exposed to the investment performance of a managed pool, the instrument is likely a financial instrument outside MiCA. Issuers launching in the EU must assess both the reference mechanism (does it stabilise?) and the yield structure (is it a return on managed assets?) before choosing a compliance path.

A second MiCA category – utility tokens – nominally includes tokens that grant access to a good or service on a DLT network. But the regulation explicitly states that a utility token may not function as a means of payment or confer rights akin to financial instruments. If the utility token's primary appeal is its yield or its claim on platform revenue, the utility label collapses and the token reverts to either ART, e-money token or – most likely – the financial-instrument carve-out. In our cross-border practice, issuers often discover this boundary when preparing the MiCA whitepaper: describing the "utility" requires admitting that the token's function is to earn interest from a lending pool, at which point the classification shifts and the prospectus route opens. The exercise is not theoretical; ESMA and national competent authorities have opened inquiries into token launches that claimed utility status but operated as yield instruments.

What disclosure obligations attach to lending products?

When a lending or yield product is classified as a security, disclosure moves from optional marketing to mandatory, liability-bearing documentation. In the United States, an unregistered offering of securities – absent an exemption – requires the issuer to file a registration statement with the SEC, provide investors with a prospectus and maintain ongoing periodic reporting. In the EU, the Prospectus Regulation requires a prospectus approved by the national competent authority before a public offer or admission to trading, unless the offering falls within a size or investor exemption. In Singapore, an offer of capital-markets products requires either a prospectus lodged with the Monetary Authority of Singapore or reliance on a private-placement or small-offer exemption. In every case, the disclosure standard is not "what the issuer wishes to say" but "what a reasonable investor needs to assess the risks and the investment."

The substantive content of a securities disclosure document for a crypto lending product includes the pooled-asset structure, the issuer's investment or allocation strategy, the source of yield (counterparty lending, staking, trading), the collateral model and liquidation procedures, conflicts of interest, the operator's track record, technical risks (smart-contract audits, custody arrangements, key management), legal risks (regulatory uncertainty, classification risk in other jurisdictions) and financial projections or performance history if any are used in marketing. Critically, the document must address risk factors with specificity. Generic statements that "digital assets are volatile" do not satisfy the standard; the disclosure must explain the mechanics by which a smart-contract exploit, a counterparty default or a market dislocation would affect the investor's principal and yield. In enforcement actions, the SEC and other regulators have emphasised that inadequate or misleading risk disclosure converts even a registered offering into a violation.

Ongoing disclosure obligations apply once the initial offering is complete. Securities laws in most jurisdictions require periodic financial reporting (quarterly or annual), material-event disclosures (a significant counterparty default, a governance change, a regulatory investigation) and – in some regimes – real-time disclosure of changes to the investment strategy or the yield model. The burden is not trivial: it requires the issuer to maintain audited financials, establish disclosure controls, appoint a compliance officer and, in many cases, list on a regulated venue that itself imposes continuing obligations. Operators launching lending products as "DeFi protocols with no issuer" have learned that the absence of a legal entity does not eliminate liability; regulators pierce the anonymity and hold the founding team or DAO members accountable for the disclosure gap.

When does a yield mechanism trigger authorisation?

Beyond disclosure, classification as a security or a regulated financial instrument triggers activity authorisation: the party managing the pool, allocating assets or paying yield must hold the appropriate licence or register with the relevant authority. In the EU under MiFID II, operating a lending or yield product classified as a financial instrument requires authorisation as an investment firm, particularly if the activity includes portfolio management or proprietary dealing. In Singapore, offering a capital-markets product without a capital-markets services licence is an offence; the licensing categories include dealing in securities, fund management and providing custodial services for securities, all of which may be implicated by a lending-pool structure. In the United States, operating as an unregistered broker-dealer or investment adviser subjects the operator to SEC enforcement, disgorgement and potential criminal referral.

The authorisation trigger often catches issuers by surprise. A token issuer may assume that because the token is traded on a third-party exchange, the issuer itself needs no licence. That assumption collapses when the issuer also manages the deposited assets, rebalances a portfolio or allocates collateral – activities that constitute portfolio management or dealing. The analysis depends on the level of discretion. A fully automated smart contract that algorithmically sets interest rates based on utilisation, with no governance vote and no issuer override, presents a weaker authorisation case than a model in which the issuer's treasury committee adjusts rates weekly or shifts deposits among counterparties. Regulators apply a control test: who has the power to affect investor returns? If the answer includes the issuer, the activity is regulated, and a licence is required before launch.

In a recent cross-border matter, a fund structured a stablecoin lending product across three jurisdictions: the issuer entity sat in Malta, the custody arrangement was in Switzerland, and the target investor base was institutional clients in Singapore. The regulatory stack required MFSA authorisation under the transitioning MiCA framework, a custodial arrangement that satisfied FINMA's segregation expectations, and either a capital-markets-services licence or a private-placement exemption in Singapore. The licensing path was not discovered in parallel; it was mapped sequentially, starting with the classification analysis, then the activity analysis, then the cross-border nexus. The lesson: authorisation is not an afterthought appended to the launch plan – it is the first gate, and it is jurisdiction-specific.

How do regulators distinguish genuine DeFi from unregistered securities?

Regulators in the flagship jurisdictions acknowledge a conceptual distinction between a truly decentralised finance protocol and a token arrangement that merely borrows DeFi language. The distinction turns on control, not on the presence of a smart contract. A protocol that operates without ongoing governance by an identifiable group, where code is immutable or changes only through a widely dispersed, token-weighted vote, and where no single party can redirect user funds or alter yield parameters, sits at the edge of regulatory reach. A protocol marketed as "decentralised" but governed by a founding team that retains an admin key, adjusts interest rates by majority-team vote or controls a significant share of governance tokens is, in substance, a managed investment product, and regulators treat it as such.

The analysis begins with the control architecture. Does a multi-signature wallet held by three founders control the contract's upgrade function? Can the team pause deposits, seize funds or change the fee structure unilaterally? If yes, the protocol is centralised in the aspects that matter for securities law. Even where governance is formally decentralised through a DAO, courts and regulators have found that a core development team or a treasury committee exercising practical control over the DAO's direction is sufficient to impose liability. The SEC has brought enforcement actions against DeFi protocols on this basis, arguing that the founding team's continued involvement in development, marketing and parameter adjustment makes them the relevant "issuer" under securities laws. The CFTC has taken similar positions in derivatives matters.

A second factor is the economic model. Does the yield paid to users come from external sources (actual lending to third-party borrowers, staking rewards on a proof-of-stake chain) or is it subsidised by the issuer through token emissions or treasury drawdowns? Subsidy models – where early users are paid from the issuer's reserves to attract deposits – closely resemble Ponzi structures and attract immediate enforcement attention. The SEC and ESMA have both warned that unsustainable yield paid to generate traction is a red flag for manipulation or unregistered offerings. In contrast, yield that flows directly from transparent on-chain activity (a borrower pays interest that flows, via smart contract, to the lender, minus a programmatic protocol fee) presents a cleaner picture, though even here the question remains: who set the fee, who deployed the contract, and who markets the arrangement?

A third element is investor sophistication and access. Protocols that restrict access to accredited or institutional investors, require KYC at the deposit interface and operate under a legal wrapper (a fund or an SPV) are easier to fit within private-placement exemptions. Protocols that allow anonymous, open access and market to retail users via social media cannot credibly claim a private-placement defence. Regulators expect that if the product is offered widely and promised yield is central to its appeal, it will comply with public-offering disclosure rules or satisfy a clear exemption. The "code is law" argument – that a smart contract cannot be an offer because it is merely software – has not prevailed in court. The contract and the promotional activity around it together constitute the offer, and both fall within securities-law reach.

What lessons emerge from past enforcement actions?

Enforcement actions against crypto lending platforms since 2021 share a common pattern. The platforms described their products as "accounts" that "earn interest" but did not register the offer as securities. They emphasised the technological novelty – blockchain rails, smart contracts, token custody – but the SEC, CFTC and state regulators focused on the economic substance: users deposited assets into a common pool, the platform lent those assets to borrowers or deployed them in trading strategies, and users received a return that depended on the platform's lending and risk-management decisions. Every element of the Howey test was satisfied. The platforms settled, agreeing to cease unregistered offerings, pay penalties and, in some cases, establish restitution funds. Not one prevailed on a defence that the arrangement was exempt or that tokens were not securities.

The first lesson is that a utility framing does not override economic substance. Platforms that issued native tokens and allowed users to earn higher yields by staking those tokens argued that the token was a utility (access to enhanced yield) rather than a security. The argument failed because the enhanced yield itself was a return on the pooled investment of the deposited crypto, managed by the platform, and the token merely unlocked a higher rate. The SEC treated the entire arrangement – deposit plus token plus yield – as a unitary securities offering. Issuers planning a similar model must start with the presumption that any yield paid from issuer-managed activity is a security unless a clear exemption applies.

The second lesson is that registration is not optional when the test is met. Several platforms asserted that requiring registration would be unworkable given the pace of crypto innovation and that securities laws were designed for equity and debt, not digital assets. The courts and regulators rejected the argument. The Supreme Court established Howey in 1946, long before the internet, let alone blockchains, but the test has been applied to orange groves, whisky casks, franchises, and now crypto. The technology does not exempt the arrangement. If the platform cannot operate under the registration regime, the platform must restructure the product – or not offer it at all.

The third lesson concerns cross-border operations. A platform incorporated in a low-regulation jurisdiction but serving US users or marketing in the EU cannot escape the reach of US or EU securities law by pointing to its foreign domicile. Courts in the United States apply a conduct-and-effects test: if the offer or sale occurs in the US, or if the conduct abroad has a substantial effect on US investors, US law applies. The EU takes a similar position under the Rome I and II regulations. Regulators have coordinated enforcement across borders; in one matter, the SEC and the FCA shared information, leading to parallel actions. Operators who assume they can geo-block a website and avoid jurisdiction learn that VPN usage, targeted marketing and the practical availability of the product to prohibited users bring the regulator's long-arm authority into play.

How should issuers structure a compliant lending product?

Structuring a compliant lending or yield product begins with classification. The issuer must determine – before code is deployed, before marketing begins – whether the arrangement is a security, an e-money token, an asset-referenced token or an unregulated utility under the target jurisdiction's framework. This is not a checkbox exercise; it requires legal analysis of the token's rights, the economic relationship between the user and the issuer, the source of yield and the degree of user control over the deposited assets. Where multiple jurisdictions are involved – the issuer sits in one, users are in another, custody is in a third – the analysis must be run in each applicable regime, and the most restrictive classification governs the global structure.

If the product is classified as a security, the compliance path splits between registered offerings and exempt offerings. A registered offering in the United States requires filing Form S-1 with the SEC, preparing a prospectus, engaging auditors, and committing to periodic reporting. The process is slow (months, not weeks) and expensive, but it is the only route for a public retail offering. In the EU, the Prospectus Regulation path similarly requires NCA approval and ongoing disclosure. Most crypto issuers instead pursue an exemption: in the US, Regulation D (Rule 506(b) or 506(c)) for accredited investors; in the EU, the private-placement or qualified-investor exemptions. The trade-off is clear: exemptions limit the investor base and impose transfer restrictions, but they avoid the full registration burden.

In jurisdictions where MiCA applies and the product is not a financial instrument, the issuer must prepare a crypto-asset whitepaper, notify the relevant NCA and, if the token is an ART or EMT, obtain authorisation. The whitepaper is not a marketing document; it is a liability document. It must describe the issuer, the technical architecture, the rights conferred by the token, the risks, the reserve mechanism (for ARTs/EMTs) and the conflict-of-interest disclosures. ESMA has published guidelines on whitepaper content; NCAs enforce them. An incomplete or misleading whitepaper exposes the issuer to administrative sanctions, investor claims and the prospect that the entire offering is void. Issuers must also establish governance (a board, compliance function, audit committee), meet capital or reserve requirements and implement AML/CFT controls that satisfy the Travel Rule and the applicable VASP framework.

A compliant structure also addresses custody and segregation. If users deposit crypto into the issuer's control, those assets are client assets in most jurisdictions, and the issuer must segregate them from its proprietary funds, maintain records and – often – use a licensed custodian or hold its own custody licence. MiFID, MAS, SFC and FINMA all impose custody obligations. Failure to segregate is not just a regulatory breach; it is a path to insolvency risk. If the issuer becomes insolvent and user funds were commingled with operating funds, users are unsecured creditors. We have seen this outcome in multiple crypto-lender collapses. The legal remedy – segregation and a trust or escrow structure – is available and standard, but it must be designed before launch, not retrofitted in distress.

What are the tax and accounting considerations?

Crypto lending and yield products raise distinct tax and accounting issues that parallel, but do not duplicate, the regulatory classification analysis. For the issuer, the question is whether yield payments to users are deductible interest expense, distribution of profit or something else. For the user, the question is whether yield received is income, a return of capital or a capital gain. The answer is jurisdiction-specific and often depends on the same substance-over-form principles that govern securities classification. If the arrangement is a debt instrument – the issuer borrows stablecoins and pays interest – the tax treatment follows debt rules. If the arrangement is equity-like (the user acquires a profit-sharing right), it follows equity or partnership rules. If the token itself is the subject of the analysis, the tax authority will look at the nature of the return: is it a reward for staking (services income or mining income), a distribution of investment profit (dividend or capital gain) or interest on a loan?

Accounting is equally substance-driven. Under IFRS and US GAAP, the issuer must determine whether user deposits are liabilities (a loan from the user) or equity (a capital contribution). If the issuer has an obligation to return the deposited assets and pay yield, the arrangement is a financial liability, recorded at amortised cost or fair value depending on the instrument's terms. If the arrangement gives the user a residual claim (the right to profit but no repayment obligation), it may be equity. The classification affects the balance sheet, the income statement and the disclosure notes. In our cross-border structuring practice, we coordinate with auditors to align the accounting treatment with the legal classification; a mismatch – where the legal structure says "loan" but the accounts show "equity" – creates audit-qualification risk and undermines credibility with regulators and investors.

Tax considerations also shape the optimal domicile for the issuer entity and the custody structure. A fund that issues a yield token to institutional investors may choose to incorporate in the Cayman Islands or BVI as a tax-neutral vehicle, allowing investors to apply their home-country tax rules without an additional layer of entity-level tax. An issuer targeting EU retail users may incorporate in Malta or Lithuania to benefit from MiCA passporting, but will then face corporate tax in that jurisdiction and must plan for withholding obligations on cross-border interest payments. The interplay between tax and licensing is not linear: the jurisdiction with the lightest regulatory burden may impose the highest tax, and vice versa. The decision must be made with both analyses on the table.

How do listing and trading rules apply?

When a crypto lending or yield token is classified as a security, its secondary trading is subject to the same rules that govern equity and debt. In the United States, a platform offering trading in securities must register as a national securities exchange or as an alternative trading system (ATS) under SEC Regulation ATS, or operate under a broker-dealer exemption. Platforms that listed yield tokens without registering faced enforcement actions; the SEC's position is that trading in any security, digital or otherwise, requires compliance with the Exchange Act. In the EU, MiFID obliges trading venues to obtain authorisation as a multilateral trading facility (MTF) or organised trading facility (OTF) if they offer trading in financial instruments, and most member states prohibit off-venue trading in instruments admitted to a regulated market.

For the issuer, this means that the decision to classify the token as a security affects not only the initial offering but the entire lifecycle. If the token is a security, secondary trading will be limited to licensed venues, broker-dealers and, in practice, institutional or accredited investors unless the issuer goes through a full public listing. Retail users expecting open, anonymous trading on a DEX will not have that option if the token is a security – or if they do, both the issuer and the platform facilitating the trading risk enforcement. The alternative is to structure the token so that it does not meet the securities test, which in the lending and yield context is difficult. The economic appeal of the product is the yield, and the yield requires either pooled funds or issuer management, both of which point toward securities classification.

Listing standards on regulated exchanges add another layer. An exchange admitting a security to trading typically requires the issuer to meet minimum financial thresholds, disclose audited financials, maintain a free float, appoint a listing sponsor and comply with continuing obligations (timely disclosure, annual reports, governance standards). Many crypto issuers do not have the corporate infrastructure or the financial transparency to meet these standards, which is why most yield tokens trade – if they trade at all – on unlicensed platforms or via OTC desks in jurisdictions with lighter enforcement. That model works until a user in a major jurisdiction files a complaint or a regulator investigates, at which point the lack of licensing becomes an existential issue. Issuers planning to offer a yield token to a broad user base must either accept the full public-company compliance burden or restrict the offering to sophisticated, exempt investors from the start.

What role do audits and third-party verification play?

Regulators increasingly expect that crypto lending platforms will obtain third-party verification of their financial condition and their reserve holdings. This expectation is driven by the collapse of platforms that claimed full backing but were in fact operating with shortfalls or commingling client and proprietary funds. Verification takes two main forms: financial-statement audits and reserve attestations. A financial-statement audit, conducted by an accounting firm under IFRS or US GAAP, provides an opinion on the issuer's overall financial position – assets, liabilities, revenue, expenses. A reserve attestation, often called a proof-of-reserves report, verifies that the platform holds, on a specific date, sufficient crypto assets to meet its obligations to depositors.

The legal significance of each differs. A clean audit opinion is typically required for a registered securities offering and is a listing prerequisite on most regulated exchanges. It provides assurance that the financial statements are fairly presented and that internal controls are adequate. A reserve attestation, by contrast, is a point-in-time snapshot and does not cover solvency, liquidity or the adequacy of the business model. Nonetheless, reserve attestations have become a reputational baseline: platforms that refuse to publish them face user scepticism and, increasingly, regulatory scrutiny. In Singapore, MAS has indicated that VASP applicants should demonstrate regular independent verification of digital-asset holdings. In the EU, the custody and segregation requirements under MiFID imply that an independent verification mechanism must be in place.

Smart-contract audits are a separate, technical layer. A smart-contract audit reviews the code for vulnerabilities – reentrancy bugs, overflow errors, access-control flaws – that could allow an attacker to drain the pool. While not a legal requirement in most jurisdictions, a contract audit is standard practice for serious issuers, and the absence of one is a red flag in the due-diligence process. More than one enforcement action has noted that the issuer launched without a contract audit, suffered an exploit and then failed to reimburse users, compounding the securities-law violation with a fraud claim. Issuers should engage a reputable contract-auditing firm, publish the audit report and, critically, address or accept the identified risks before deploying the contract. An audit report that lists critical vulnerabilities and is ignored is worse than no audit at all.

When should an issuer engage counsel?

The optimal time to engage legal counsel is before the whitepaper is drafted, before the token sale is announced and before marketing begins. This is not because early engagement is a best practice – it is because remediation after launch is, in most cases, impossible. Once tokens are distributed and users have deposited funds, the issuer cannot unwind the structure without triggering tax events, redemption obligations and potential claims of rug-pull or abandonment. If the product was launched as a utility but is later determined to be a security, the issuer faces an unregistered-offering violation that cannot be cured by filing a registration statement retroactively. The violation has occurred; the remedy is disgorgement, penalties and, often, a lifetime bar from the industry for the principals.

Counsel's role at the design stage is to map the classification across the target jurisdictions, identify the licensing and disclosure requirements and pressure-test the structure against enforcement precedent. For a yield product, this means modelling the cashflows (where does the yield come from?), analysing the governance (who can change the parameters?), reviewing the whitepaper for misstatements or omissions and confirming that the token distribution complies with applicable exemptions. If the target market includes the United States and the EU, counsel will run both the Howey analysis and the MiCA/MiFID classification in parallel and advise on the narrowest compliance path. If the analyses diverge – the token is exempt in the US under Regulation D but is an ART in the EU requiring CASP authorisation – the issuer must either accept multi-jurisdictional compliance or narrow the geographic scope.

In a recent engagement, a token issuer approached us six weeks before a planned launch, having already drafted a whitepaper, opened pre-sale marketing and secured commitments from investors. The classification analysis revealed that the token, as structured, was a security in the US, the EU and Singapore. The issuer had no registration, no prospectus and no licences. The launch was paused, the whitepaper was withdrawn and the structure was rebuilt with a private-placement wrapper, transfer restrictions and a licensed custodian. The delay cost four months and additional legal spend, but the alternative was an enforcement action and potential criminal referral. If counsel had been engaged at the concept stage, the structure would have been built correctly from the outset, and the launch would have proceeded on time.

For a classification and compliance roadmap tailored to your token structure and target markets, contact OBOLUS at info@oboluslaw.com. The assessment covers the applicable legal tests across the relevant jurisdictions, the disclosure and authorisation requirements, the licensing path for the issuer and any platform offering secondary trading, and the steps to bring an existing product into compliance if it was launched without registration.

FAQ

Is my token a security under this regime?

The answer depends on the rights the token confers and the economic arrangement around it. If the token gives holders a claim on yield generated by the issuer's management of pooled assets, it is likely a security under US law, a financial instrument under MiFID in the EU, and a capital-markets product in Singapore. The label you apply in the whitepaper does not determine the classification; the regulator will analyse the substance. If you are uncertain, engage counsel to run the classification test in each target jurisdiction before you launch. A mis-classification converts a product launch into an unregistered securities offering.

Do I need a whitepaper or prospectus?

It depends on the classification. If the token is a security, you need either a registered prospectus (in a public offering) or reliance on a private-placement exemption with appropriate disclosure to exempt investors. If the token falls within MiCA as a crypto-asset that is not a financial instrument, you need a crypto-asset whitepaper notified to the NCA. If the token is an ART or EMT, you also need authorisation as a CASP. A whitepaper is not a substitute for a prospectus; they serve different legal functions. The whitepaper satisfies MiCA; the prospectus satisfies securities law. If both apply, you produce both.

What disclosure is required at launch?

If the product is a security, disclosure must cover the issuer's business, the risks, the source of yield, the use of proceeds, the technical architecture (including custody and smart-contract audits), conflicts of interest and financial statements. If the product is subject to MiCA, the whitepaper must describe the token's function, the issuer's governance, the reserve model (if applicable) and the rights conferred. Both regimes impose liability for material omissions or misleading statements. The standard is not "what the issuer wishes to disclose" but "what a reasonable investor needs to assess the risk and the investment." Under-disclosure exposes the issuer to regulatory sanctions and investor claims.

Related at 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 that sit around them. Digital assets are the whole of our practice. Operators we advise routinely encounter the classification issue at the design stage, where the structure can still be adjusted before capital is committed and marketing begins. We assess classification against the substance of rights conferred, not the label applied in the whitepaper, and map the disclosure and authorisation requirements in each target market. To discuss your situation, contact info@oboluslaw.com.

By Roman Levitt, Technology & DeFi Counsel – Roman specialises in the legal analysis of smart-contract-based financial instruments, token classification and the regulatory treatment of decentralised protocols across major jurisdictions.

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.

Discuss your matter with OBOLUS

Tell us about the business, the jurisdictions in scope and the deadline. Every brief is confidential and we reply within two hours.

Or email info@oboluslaw.com. We treat your brief as confidential.

Tell us the task — we'll map your options in 30 minutes.

Fixed-fee packages with defined scope and SLAs. The first call is free and under NDA. Business clients only.

Map your optionsinfo@oboluslaw.com · reply < 2 hours