PRIM3 Brief #6: The U.S. Tokenization Framework — Three Things Founders Need to Know

The bipartisan tokenization legislation moving through both chambers of Congress and the parallel rulemaking from the SEC and CFTC represent the most consequential piece of U.S. crypto policy since the original 1933 Act got applied to tokens in 2017. The current state of the framework — combining the Lummis-Gillibrand-derived market-structure bill, the SEC's emerging tokenized-securities-safe-harbor framework, and Treasury's tokenized-MMF guidance — gives U.S. tokenization founders a clearer path than they've had in a decade.

Most of the coverage of this framework is high-altitude and political. PRIM3's view is that the operational details determine whether a protocol can actually use it — and three specific details are doing most of the work. This brief lays them out.

Detail One: The Custody-Architecture Question

The first operational detail is whether the framework treats fully-on-chain custody (multisig, MPC, native protocol custody) as equivalent to qualified-custodian custody for purposes of compliance. The current draft language is ambiguous on this and the rulemaking will resolve it.

Two outcomes are possible. Outcome A: the framework treats credibly-implemented on-chain custody (with documented audit trails, key-rotation protocols, and incident-response infrastructure) as equivalent to qualified custodian custody. Outcome B: the framework requires a qualified-custodian intermediary for any tokenized asset that touches U.S. investor wallets above certain thresholds.

The difference between A and B is, for many Web3-native tokenization plays, existential. If outcome A lands, protocols like the credible on-chain securitization plays we see in our pipeline can operate without a traditional custodian-bank dependency. If outcome B lands, the protocols become custodian-dependent on a tier of institutional custodians (BNY Mellon, State Street, Fidelity Digital, Anchorage) that may not be commercially feasible partners for early-stage protocols.

Our reading, based on the SEC's recent statements and the White House's August 2025 digital asset working group output, is that outcome A is more likely than outcome B for tokenized treasury and MMF instruments specifically, with a hybrid approach for other tokenized asset classes. But this is not settled and the comment period on the SEC's pending guidance ends in Q2 2026. Founders should be writing comments.

Detail Two: The Secondary-Market Trading Question

The second operational detail is whether the framework's safe-harbor for tokenized-security issuance extends credibly to secondary-market trading on DEX-style venues, or whether secondary trading has to occur on registered ATSes (Alternative Trading Systems) or national securities exchanges.

The mainstream Web3 reading of the framework assumes it will allow DEX-style secondary trading of tokenized securities. The current draft language is more conservative than that reading. It contemplates a path to secondary-market trading on DEX venues, but only after each venue clears a specific compliance bar that includes, among other things, real-time KYC at the wallet level, transfer-restriction enforcement at the contract level, and reporting obligations equivalent to what registered ATSes face today.

This is, in our view, the single most important detail for any tokenized-securities founder to internalise. The framework will permit secondary trading on DEX-style infrastructure if and only if the DEX infrastructure has been built to handle institutional-grade compliance from the contract layer up. Bolted-on compliance, KYC at the front-end with permissionless transfer at the contract level, will not clear the bar.

The teams positioned to win this segment are the ones that have been quietly building compliance-native DEX infrastructure for the past three years, often without much public attention. We're tracking five of them seriously in our pipeline. None of them is on most lists of "DEXes to watch." That's a useful signal.

Detail Three: The Cross-Jurisdictional Composition Question

The third operational detail is how the U.S. framework composes with other major jurisdictions — particularly EU MiCAR, Singapore MAS Project Guardian, and the UK FCA's digital securities sandbox.

The U.S. framework as currently drafted does not include automatic recognition of foreign jurisdictional regimes. A tokenized security issued under MiCAR cannot, under the current draft, be freely held by a U.S. qualified purchaser without separate U.S.-side compliance work. The reverse is also true. This creates a cross-jurisdictional friction that the press coverage is largely ignoring.

For founders, the implication: any tokenized-asset architecture that depends on cross-jurisdictional fungibility for liquidity needs to bake in jurisdiction-specific compliance from day one. The teams building credible answers here are the ones whose architecture supports per-jurisdiction whitelisting, per-jurisdiction transfer restrictions, and per-jurisdiction reporting at the smart contract level rather than as application-layer add-ons.

Kima Network, disclosed, portfolio, has been working on the cross-jurisdictional settlement-and-compliance layer for two years and has, in our view, the cleanest implementation among the bridgeless cross-chain protocols. The reason that matters: in 2026, "cross-chain" isn't the right framing; "cross-jurisdictional" is. The infrastructure that solves cross-jurisdictional compliance and settlement composably is the infrastructure that wins this regulatory cycle.

What This Means For Founder Strategy

PRIM3 is telling portfolio founders three specific things about the framework right now:

For tokenized RWA founders: the U.S. is going to become a workable jurisdiction for tokenized assets in 2026–2027, but the operational bar is high. Founders should be hiring securities lawyers in Q1 2026 if they aren't already. The cost of clean compliance work upfront is roughly 30–50% lower than the cost of remediation later, based on what we've seen in our portfolio.

For DEX and trading-infrastructure founders: the framework rewards compliance-native architecture. Bolted-on compliance is a strategic dead end for any venue that wants to handle tokenized securities flow. Founders should be making this architectural decision now, not after a tokenization product launches.

For cross-jurisdictional infrastructure founders: this is one of the highest-conviction sectors in PRIM3's underwriting universe right now. The framework's lack of automatic cross-jurisdictional recognition creates a structural demand for infrastructure that solves the problem composably. Founders building credibly here have a unusually clear runway through 2027–2028.

For DeFi founders not in tokenization: the framework is structurally favourable to your sector indirectly — institutional capital flowing into compliant tokenization creates demand for institutional-grade DeFi composability. Founders should be designing for institutional-grade demand on the integration side, even if the tokenized asset isn't your product.

A Pragmatic Note On Timing

The framework is moving but not yet fully implemented. The realistic timeline, based on our conversations with policy staff and senior law-firm partners working on this, is:

• Q2 2026: SEC tokenized-securities guidance finalised (high confidence)
• Q3–Q4 2026: First credible tokenized-securities issuances under the new safe harbour (moderate confidence)
• 2027: First credible DEX-style secondary-market venues clearing the institutional bar (moderate confidence, contingent on architectural work)
• 2028: The framework operating at meaningful scale (low confidence on timing, high confidence on direction)

Founders building toward this should be planning for a 12–18 month gap between framework finalisation and product going live at scale. The credible teams are using that gap to do the deep architectural work that lets them be operational immediately when the framework clears.

Where We're Allocating

PRIM3 is overweight on tokenization infrastructure in 2026, with active diligence on five positions in compliance-native architecture, cross-jurisdictional settlement, and institutional-grade tokenization plumbing. We're underweight on tokenization plays that depend on the framework being more permissive than it's likely to be. We're cautious on tokenization plays that haven't yet hired serious securities counsel.

If you're building credibly in any of these segments and want to compare notes on the framework's implementation timeline, pitch us via prim3.vc.