A token issuer preparing a United States launch discovers that the securities-versus-commodity question no longer turns on a single fixed test. Under proposed federal market-structure legislation currently before Congress, a digital asset would move between regulatory regimes as it matures – securities oversight at launch, commodities treatment once a network reaches functional decentralization. The framework is not yet law, but the concept has reshaped every compliance roadmap for businesses planning token offerings into the US market. For operators building across borders, the practical question is not which regulator wins the turf battle, but how to structure a compliant launch when the legal classification is designed to change over time.
The proposed legislation introduces a maturity threshold – a defined point at which a token transitions from securities regulation under the SEC to commodities oversight under the CFTC. If adopted, the regime would replace years of case-by-case enforcement with statutory clarity on when a token offering requires registration, when it may proceed under an exemption, and when it exits securities law altogether. This analysis unpacks the classification logic, the disclosure obligations at each stage, and the cross-border reality that faces every issuer whose user base, development team and treasury sit in different jurisdictions.
What the proposed framework changes
The proposed framework replaces the Howey-derived analysis with a statutory maturity model. A digital asset begins its life as a security if it is sold in connection with development efforts that create an expectation of profit from the work of others. It exits securities regulation when the network reaches functional decentralization – defined in the draft legislation as a state where no single person or coordinated group controls the protocol, voting rights are distributed, and the asset trades on secondary markets independent of ongoing managerial efforts. The shift is structural: classification becomes a phase, not a permanent label.
Under current law, the SEC applies the Howey test – an investment of money in a common enterprise with profits derived solely from the efforts of others – case by case. Tokens marketed as utilities have been charged as unregistered securities when the facts showed centralized control and a reasonable expectation of profit tied to the issuer's post-sale work. The proposed legislation codifies elements of that analysis but sets a statutory exit: once decentralization is demonstrated, the asset is reclassified as a commodity and moves to CFTC jurisdiction. Exchanges, advisers and custodians would register with the appropriate agency depending on which side of the maturity line the asset sits.
In our practice, businesses often begin the classification assessment with the assumption that an offshore issuer, an open-source codebase or a governance token wrapper removes US jurisdiction. It does not. If the token is offered to US persons, sold through US-facing platforms or promoted in ways that reach the US market, both the SEC and the proposed regime reach the offering. The maturity concept affects which regulator applies, not whether US law applies at all.
The cross-border angle turns on two realities: the issuer's domicile may be outside the United States, but if the user base or the liquidity sits inside it, the US regulatory perimeter applies. A foundation in Switzerland issuing to holders worldwide still faces the maturity-threshold analysis if a material portion of buyers are US persons. The second reality is that most token businesses already operate under multiple regimes – MiCA in the EU, VARA in Dubai, MAS licensing in Singapore – and the US framework adds another layer that does not replace the others. A token that exits securities regulation in the United States may still be a transferable security under MiCA or a capital-markets product under Singapore's Payment Services Act. Operators building a compliant stack must map each jurisdiction's classification separately and structure the launch to satisfy the strictest perimeter.
How maturity is defined and demonstrated
Functional decentralization under the draft framework is a factual determination. The legislation sets out criteria: no single entity or coordinated group may exercise control over the protocol; governance rights must be distributed such that no coalition can unilaterally change core functionality; and the asset must trade on markets where price discovery occurs independently of the issuer's ongoing efforts. The burden of demonstrating maturity sits with the issuer, and the proposed regime contemplates a certification process – filing a notice with the SEC and the CFTC that includes technical documentation, governance data and evidence of secondary-market activity.
The certification is not automatic. Regulators retain discretion to challenge a maturity claim, and the draft legislation allows for a review period during which the asset remains under securities oversight. Until the certification is accepted, the token is treated as a security for all purposes – registration, prospectus delivery, broker-dealer intermediation, custody under the Investment Advisers Act. For issuers that launch with partial decentralization or phased governance roll-outs, the maturity line may sit years into the lifecycle, not months.
In practical terms, the maturity test shifts the focus from the offering to the network. A pre-functional network – one where the development team controls the protocol, holds a founder allocation that dilutes secondary holders, or retains veto rights over governance proposals – remains a security indefinitely. A fully operational blockchain with distributed validators, on-chain governance and no central administrator may exit securities regulation within quarters of launch, provided the evidence supports the claim. The gap is structural: many projects market themselves as decentralized at token generation but retain operational control well into the second or third year of trading. The proposed framework makes that gap enforceable – misrepresenting maturity would be a securities violation with civil and criminal exposure.
Disclosure requirements before and after maturity
Before a token crosses the maturity threshold, it is subject to the full disclosure regime for securities offerings. If the offering is registered, the issuer files a registration statement – analogous to an S-1 for equity – with detailed risk factors, use-of-proceeds disclosures, management background, financial statements and a description of the digital asset's rights and restrictions. If the offering proceeds under an exemption – Regulation D for accredited investors, Regulation A for smaller raises, Regulation S for offshore placements – the disclosure obligations scale down but remain substantial. A Regulation D filing requires a Form D and delivery of offering materials that describe the investment; a Regulation A requires an offering circular reviewed by the SEC.
A whitepaper is not a substitute for a prospectus. The proposed framework does not use the term "whitepaper" in its disclosure provisions; it refers to offering documents that must meet statutory content standards. Many issuers treat a technical whitepaper – describing the protocol, the token economics and the roadmap – as compliance with disclosure law. It is not. A whitepaper that omits risk factors, conflicts of interest, the team's prior ventures, the use of proceeds or the basis for any projected token utility fails the disclosure test under both current law and the proposed regime. If a token is a security at launch, the issuer must deliver a compliant prospectus or offering memorandum, not a marketing deck labeled as a whitepaper.
After maturity – once the asset is certified as functionally decentralized and moves to commodities oversight – the ongoing disclosure burden shifts. The CFTC does not impose prospectus-delivery or periodic-reporting obligations on the asset itself, but platforms trading the asset must register as designated contract markets or swap execution facilities if they offer derivatives, and spot exchanges may face registration as commodity trading platforms under the proposed regime. The issuer's disclosure obligation at that stage is limited: updates to protocol governance, material changes to the codebase and security incidents that affect asset holders. The framework contemplates a lighter-touch regime post-maturity, but it is not disclosure-free.
In cross-border offerings, the disclosure question multiplies. A token offered under MiCA requires a crypto-asset whitepaper filed with the national competent authority; one offered in Singapore requires a prospectus or product highlights sheet depending on whether it is a capital-markets product; one offered in Hong Kong under the SFC's virtual-asset trading platform regime requires disclosure that satisfies the Securities and Futures Ordinance. None of these is equivalent to a US registration statement, and none automatically satisfies the others. Issuers launching globally must prepare multiple disclosure documents, each tailored to the local regime, or structure the offering to exclude US persons and avoid the US disclosure burden altogether. The latter works only if the issuer genuinely restricts access – geofencing, IP blocking and investor representations are scrutinized, and a nominal exclusion coupled with US-facing promotion invites enforcement.
Registration exemptions and when they apply
The proposed framework preserves the existing exemption architecture for securities offerings and adds a new safe harbor for tokens that are sold primarily for consumptive use rather than investment. The safe harbor applies if the token grants access to a network or application, the buyer's motivation is functional rather than speculative, and secondary trading is incidental to the primary utility. The criteria are narrow: the issuer must demonstrate that the network is operational at the time of sale, that the token has present utility, and that marketing materials do not emphasize price appreciation or investment returns. A token sold with a roadmap promising future features, marketed on the basis of scarcity or limited supply, or promoted through price charts and ROI projections does not qualify.
For offerings that do not meet the safe harbor, the familiar exemptions apply. Regulation D Rule 506(b) allows unlimited capital raises to accredited investors without general solicitation; Rule 506(c) permits general solicitation if all purchasers are verified accredited investors. Both require a Form D filing within 15 days of the first sale and restrict resale under Rule 144 for twelve months. Regulation A allows offerings up to a specified ceiling with scaled disclosure and the ability to solicit non-accredited investors, but requires an offering circular qualified by the SEC – a process that typically runs several months. Regulation S applies to offers and sales outside the United States, but the offshore-transaction requirement is strict: US persons may not participate, and the issuer must implement procedures to prevent immediate flowback into the US market.
A common planning mistake is layering exemptions without regard to integration risk. An issuer conducting a Regulation S sale offshore and a concurrent Regulation D raise in the United States risks integration – the SEC treating the two offerings as a single unregistered public offering that does not qualify for either exemption. The proposed framework does not eliminate integration analysis; it clarifies that a token offering is a single continuous offering unless the issuer can demonstrate separate economic terms, distinct marketing efforts and a substantive gap in time between tranches. For businesses raising in stages – a seed round for accredited investors, a public sale under Regulation A, a non-US placement under Regulation S – the sequencing, disclosure consistency and prohibition on flowback matter as much as the exemption itself.
Custody, intermediation and platform registration
The proposed legislation requires platforms facilitating trading in digital-asset securities to register as alternative trading systems (ATS) or national securities exchanges, and those handling custody to register as broker-dealers or comply with the Investment Advisers Act custody rule. Once a token matures and moves to commodities oversight, platforms must register with the CFTC as designated contract markets, swap execution facilities or, if the statute creates it, a new category of spot commodity exchange. The intermediary's registration obligation follows the asset's classification: a platform trading a pre-maturity token must register with the SEC; the same platform trading the post-maturity asset must register with the CFTC.
In practice, this creates a compliance cliff for exchanges. A business that lists a token at launch as a security must maintain broker-dealer registration, implement order-protection and best-execution policies, file reports with FINRA, and segregate customer assets under Rule 15c3-3. When the token crosses the maturity threshold and the issuer files a certification, the platform must transition the asset to its commodities book, cease applying securities-law protections, and begin complying with CFTC rules on position limits, trade reporting and margining. Platforms that operate across both categories – listing securities-stage tokens alongside mature commodities – must maintain dual registration, separate books and distinct compliance teams. The operational cost is substantial, and many smaller platforms have indicated they will restrict listings to post-maturity assets only to avoid the broker-dealer burden.
Custody obligations differ before and after maturity. A custodian holding digital-asset securities for advisory clients must comply with the Investment Advisers Act custody rule: annual surprise examinations, qualified-custodian status, client account statements. The rule was written for traditional securities and applies awkwardly to private-key architectures, but the SEC has indicated that digital-asset custodians must meet the same standard or seek a no-action letter for alternative arrangements. After maturity, the CFTC custody regime applies – lighter for spot assets, more prescriptive for derivatives and margined positions. For businesses offering custody as a service across multiple token types, the legal stack becomes a matrix: each asset's maturity status determines which regulator's custody rule applies, and the stack must be updated every time an issuer certifies a maturity transition.
Cross-border considerations for US-facing offerings
An issuer domiciled outside the United States remains subject to US law if the offering reaches US persons. The proposed framework preserves the extraterritorial reach of US securities law: an offer, sale or promotion that targets the US market triggers registration or exemption obligations regardless of where the issuer sits. The maturity threshold applies the same way – a non-US issuer claiming functional decentralization must file the certification with the SEC and the CFTC and bear the burden of proving that US-based holders are not relying on the issuer's ongoing managerial efforts.
The practical challenge is that most global token offerings touch the US market at some point. A token listed on a centralized exchange with US users reaches US persons even if the issuer took no direct action to solicit them; a token promoted in English-language Telegram groups or Twitter threads with US participants constitutes a US-directed offering. Structuring a genuinely non-US offering requires more than a website disclaimer. It requires geofencing at the contract level – smart-contract logic that blocks addresses associated with US IP ranges or wallet providers serving US customers – and consistent enforcement. We have seen issuers implement geo-blocks for the token sale, then allow the token to list on US-accessible exchanges within weeks, converting the Regulation S exemption into an enforcement exposure.
The interaction between the US framework and other regimes is not harmonized. A token classified as a transferable security under MiCA does not automatically qualify as a security under the proposed US legislation, and a token that exits US securities regulation at maturity may remain a regulated financial instrument in the EU, Singapore or Hong Kong indefinitely. Issuers operating in multiple jurisdictions must maintain separate classification analyses and separate disclosure documents for each regime. The least-common-denominator approach – treating the token as a security everywhere until every applicable jurisdiction agrees it is not – adds cost and restricts secondary liquidity, but it eliminates classification risk. The alternative – maintaining jurisdiction-specific regulatory stacks – requires legal and compliance infrastructure that scales with the number of user jurisdictions, not the size of the offering.
When the maturity test is disputed
The proposed framework allows the SEC to challenge a maturity certification within a defined review period. If the SEC disputes the issuer's claim of functional decentralization, the token remains under securities oversight until the dispute is resolved. The challenge may be informal – a comment letter questioning the evidence – or formal enforcement action alleging that the certification was materially false. For issuers that misjudge the maturity line, the exposure is substantial: secondary trading that occurred after the claimed maturity date may be recharacterized as unregistered securities transactions, and platforms that delisted the asset from their ATS books may face broker-dealer violations for facilitating unregistered trades.
In disputes we see, the most common factual issue is the definition of "control." An issuer that claims decentralization because governance tokens are distributed may still exercise control if it holds a founder allocation with supervoting rights, retains a multisig key that can pause the protocol, or employs a development team that unilaterally pushes code updates without on-chain approval. The SEC has taken the position – consistent with the proposed legislation's language – that functional decentralization requires genuine diffusion of control, not merely the appearance of distributed governance. A token with a DAO structure on paper but off-chain coordination among large holders is not decentralized for regulatory purposes.
The burden of proof matters. The draft framework places it on the issuer to demonstrate maturity, not on the regulator to prove ongoing centralization. This reverses the usual enforcement posture and makes the certification process adversarial by design. Issuers filing for maturity must prepare a factual record – validator distributions, voting outcomes, evidence that secondary prices move independently of the issuer's announcements – that can withstand scrutiny. In borderline cases, businesses often hold the certification back until the network's decentralization is unambiguous, even if that delays the transition to commodities oversight by quarters or years. The cost of a premature certification – securities-fraud exposure – outweighs the benefit of lighter-touch regulation.
Choice of entity and structuring for the maturity transition
The maturity transition affects entity structure. Many issuers have separated the token sale from ongoing protocol development by using a foundation in a neutral jurisdiction – Switzerland, the Cayman Islands, Singapore – to hold the intellectual property and treasury, while a separate operating company conducts the offering under a US exemption. The structure worked under the old enforcement regime because it created legal distance between the developers and the token, reducing the argument that profits were tied to managerial efforts. Under the proposed framework, the separation becomes less effective: the maturity test looks to de facto control, not legal structure, and a foundation that is controlled by the same persons as the operating company does not establish decentralization.
A cleaner structure for the maturity transition is a phased transfer of control. The issuer launches the network under centralized governance, registers the token offering as a security or proceeds under an exemption, and operates transparently as the development team. Over time, governance rights vest in token holders, the development team's allocation unlocks on a schedule that prevents it from holding a majority, and protocol upgrades move to on-chain votes. When decentralization is achieved, the issuer files the maturity certification and winds down or converts the development entity into a service provider compensated by the DAO at market rates. The structure is deliberate, documented and defensible – it does not claim decentralization prematurely, and it does not retain hidden control after certification.
For offshore issuers, the entity choice also implicates tax. A foundation in the Cayman Islands that sells tokens to US persons may have US-source income subject to withholding, and if it engages in a US trade or business – such as operating servers or employing personnel in the United States – it may be subject to US corporate tax on effectively connected income. The interplay between the securities classification and the tax classification is not automatic: a token that is a security for SEC purposes may be property for tax purposes, and its sale may generate capital gain rather than ordinary income depending on the holder's classification. Cross-border token structures require coordinated securities, tax and AML advice, and the maturity transition adds a further planning point – when the token exits securities regulation, the tax treatment may change if the character of income shifts from investment returns to commodity sales.
Common mistakes and enforcement risks
The first planning error is assuming that the proposed framework, because it is not yet law, can be ignored. It cannot. The statutory language has been refined through multiple drafts, the concepts have bipartisan support in Congress, and the SEC and CFTC have both signaled that they view the maturity model as workable. Issuers launching today may find themselves subject to the regime within months if the legislation passes, and structuring choices made now – choice of exemption, disclosure completeness, the timing of the offering relative to network launch – will be judged under the new framework retroactively if enforcement follows. The safer course is to structure offerings as if the maturity test applies, even if the statute has not yet been signed.
A second mistake is under-investing in the maturity-certification record. Issuers often wait until they wish to file the certification to begin assembling evidence of decentralization, only to discover that key data – historical validator distributions, governance-vote participation rates, evidence of price discovery independent of the issuer's announcements – was not recorded or is incomplete. The certification is a factual filing, not a legal argument, and the record must be built contemporaneously. We advise clients launching networks to implement data-capture systems at genesis: logging every governance action, recording validator entry and exit, tracking secondary-market depth and capturing evidence that protocol changes occur through distributed consensus. When the maturity filing is prepared, the evidence is ready.
A third error is failing to distinguish between technical decentralization and regulatory decentralization. A blockchain may be decentralized in the sense that no single validator controls consensus, but remain centralized for securities-law purposes if a single entity controls the issuance of new tokens, holds a disproportionate treasury allocation, or retains the ability to upgrade the protocol without token-holder approval. The proposed framework's maturity test is economic and governance-focused, not technical. An issuer claiming decentralization must show that economic value accrues to the network as a whole, not to a central promoter, and that governance decisions are made by a distributed set of stakeholders, not a development team executing a roadmap.
Enforcement risk is immediate. The SEC has continued to bring actions against token issuers for unregistered securities offerings even while the proposed legislation moves through Congress, and the cases show that the agency is not waiting for statutory clarity to enforce existing law. Issuers that launch without registration or a valid exemption, that misrepresent a token's investment characteristics, or that omit material risks in offering documents face civil penalties, disgorgement and, in cases involving fraud, criminal referral. The proposed framework will not retroactively cure violations that occur before it becomes law. Compliance today protects against enforcement tomorrow.
Decision matrix for issuers
Issuer profile A – a development team launching a blockchain with a native token and immediate utility: if the network is operational at launch, the token grants consumptive access, and marketing does not emphasize investment returns, the issuer may qualify for the proposed consumptive-use safe harbor. Structure the launch with evidence of present utility, avoid speculative promotion, and prepare to demonstrate that buyers are using the token for its intended network function. If the safe harbor does not fit, proceed under Regulation D for accredited investors or Regulation A with SEC-qualified disclosure. Indicative timeline for safe-harbor assessment: legal review typically requires three to five weeks to pressure-test the facts against the statutory criteria; key risk is that post-launch trading behavior – speculation, listing on exchanges marketed to investors – undermines the consumptive-use characterization.
Issuer profile B – a centralized platform launching a governance token with phased decentralization: the token begins as a security. Register the offering or proceed under an exemption that matches the capital target and investor base. Plan for a multi-year timeline to functional decentralization: vesting schedules for the founding team, documented governance milestones, validator on-boarding tracked on-chain. File the maturity certification only when control is genuinely diffused, supported by a factual record that shows distributed governance is operational, not aspirational. Indicative timeline: the maturity transition for a well-structured phased launch typically occurs 18 to 36 months post-genesis; key risk is that the development team retains de facto control longer than the legal structure suggests.
Issuer profile C – an offshore foundation conducting a global token sale excluding US persons: structure the offering under Regulation S with robust geo-blocking and no US promotion. Monitor secondary markets to prevent immediate flowback; if the token lists on a US-accessible exchange, that listing may constitute a US offering unless the exchange independently restricts US persons. Even if the US market is excluded at launch, prepare for the possibility of US-person participation in secondary trading – if material, the issuer may need to assess whether post-maturity commodities law applies. Indicative timeline: Regulation S structuring requires four to six weeks for legal documentation, smart-contract implementation of IP-based restrictions and coordination with listing venues; key risk is that exclusion is nominal and US participation occurs despite the restrictions, converting the exempt offering into an enforcement issue.
The firm's position on pre-law structuring
We treat the proposed framework as the compliance baseline even though it is not yet enacted. That means structuring token offerings with full registration or a documented exemption, preparing disclosure that meets prospectus standards regardless of whether the issuer calls it a whitepaper, and building the factual record for a maturity certification from day one of network operation. The legislation's passage timeline is uncertain – it may be law within quarters or face further amendment and delay – but the regulatory expectation it reflects is already operational. The SEC has signaled that it views functional decentralization as the dividing line between securities and commodities oversight, and issuers that plan to that standard reduce enforcement risk whether or not the statute is signed.
In our practice, the structuring conversation begins with a classification analysis that assumes the maturity test applies. We assess whether the token, as designed, begins its life as a security, and if so, whether it is capable of crossing the maturity threshold or will remain a security indefinitely because control is not designed to diffuse. For tokens that will mature, we map the phased governance transition, draft the certification-record requirements and structure the entity to allow the development team to exit operational control without abandoning the protocol. For tokens that remain securities by design – closed-end fund tokens, revenue-sharing instruments, tokens that represent fractional ownership in an asset – we structure the offering as a registered product or a long-term exempt placement, with no maturity exit planned.
The cross-border angle is central to every structuring decision. A token launching in the United States and the EU must satisfy both the proposed US maturity framework and MiCA's transferable-security or e-money-token classification. A token launching offshore to avoid US registration must implement exclusion procedures that withstand scrutiny when US persons inevitably appear in secondary trading. For businesses whose operations span multiple jurisdictions – treasury in one, development in a second, users in a third – the legal stack is multi-jurisdictional from the start, and the US component is one input to a global compliance model. In those situations the question is not whether to comply with US law, but how to sequence the jurisdictions, structure the disclosure, and allocate legal budget across regimes so that the business can operate commercially while each jurisdiction's requirements are met.
For a scoped assessment of your token's classification under the proposed framework, contact OBOLUS at info@oboluslaw.com.
Related practices
- Token Offerings & Securities – Compliant structuring for issuers, underwriters and platforms across registration and exemption pathways.
- HKD-referenced stablecoins: when offshore issuers need a Hong Kong licence – Comparative classification logic for stablecoins facing multiple regimes.
- Airdrop legal structuring from a cross-border perspective – Distribution mechanisms and the regulatory treatment of token transfers without consideration.
FAQ
Is my token a security under this regime?
It depends on whether the network is functionally decentralized. Under the proposed framework, a token is a security if sold in connection with efforts that create an expectation of profit from the work of a promoter or development team. If your network is centralized at launch – you control the protocol, hold a large treasury allocation, or market the token on the basis of your roadmap – it begins as a security. It exits securities regulation when you can demonstrate functional decentralization: distributed governance, no single controlling entity, and secondary trading independent of your ongoing work. Until you file a maturity certification and it is accepted, the token remains a security.
Do I need a whitepaper or prospectus?
You need a compliant offering document, not a marketing whitepaper. If your token is a security at launch, you must deliver either a registration statement filed with the SEC or an offering memorandum that meets the disclosure requirements of the exemption you are relying on – Regulation D, Regulation A or Regulation S. A technical whitepaper that describes the protocol without addressing risk factors, conflicts of interest, use of proceeds and the team's background does not satisfy securities-law disclosure obligations. The document's title does not matter; its content must meet statutory standards.
What disclosure is required at launch?
If you are conducting a registered offering, you file a registration statement with full risk-factor disclosure, financial statements and use-of-proceeds detail, reviewed and declared effective by the SEC. If you proceed under Regulation D for accredited investors, you deliver an offering memorandum with risk disclosure and file a Form D within 15 days of the first sale. If you use Regulation A, you file an offering circular qualified by the SEC. If you rely on the proposed consumptive-use safe harbor, you must be able to demonstrate that the token has present utility and that buyers are using it for network access, not investment – evidence of that use becomes part of your compliance record. After the token matures and exits securities regulation, ongoing disclosure shifts to material protocol changes, governance updates and security incidents.
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 that sit around them. Digital assets are the whole of our practice. Our disputes team coordinates freezing relief and on-chain tracing across leading common-law forums, and our regulatory desk structures offerings to meet the requirements of multiple regimes simultaneously – MiCA, VARA, the US framework and the classification logic that applies in each. We assess classification against the substance of rights, not the marketing label. To discuss your situation, contact info@oboluslaw.com.
By Roman Levitt, Technology & DeFi Counsel – specializing in token classification, US and cross-border securities structuring, and the regulatory treatment of decentralized protocols.
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.