Research

RWA

Absorbed or Synchronized: Two Routes for Tokenized Stock Trading

25 Oct 2026 · 10 min read

The same U.S.-listed share can now become a token by two routes. Inside, DTCC and Nasdaq absorb it within one operator’s books. Outside, the SEC’s Innovation Exemption lets new venues trade it on public blockchains, but only after writing synchronization into its conditions. Absorption ends where the number of operators grows, not where assets get complex.

Tokenized stock trading desk: a hand lifts the phone below screens reading trading halted and live

TL;DR

  • In the autumn of 2026 the United States opened two routes for trading the same listed share as a token: an inside route through DTCC’s tokenization service and Nasdaq’s same-order-book rule, and an outside route through the SEC’s Innovation Exemption, which lets new venues carry tokenized stock trading onto public blockchains.
  • Inside, absorption works because one operator keeps the asset’s whole life in its own books. Outside, the SEC had to write synchronization into the conditions, and its demand that trading halt concurrently with the listing exchange is atomic state binding (S3) stated in the language of market structure.
  • The boundary of absorption is the number of operators. Nothing yet makes “concurrently” true across ledgers run by different parties, so a pause button and a 0.25% volume cap stand in for the mechanism.

The Week Tokenized Stock Trading Got Two Routes

On September 15, 2026, the U.S. Senate voted 49 to 50 against taking up the Digital Asset Market Clarity Act [1], the bill we read in Tokenized Securities Under the CLARITY Act: The Weight of Codification as a proposition that had arrived but not yet taken effect. Two days later the SEC opened another route. It granted a five-year conditional exemption that lets venues not registered as exchanges trade tokenized versions of U.S.-listed stocks on public blockchains [2].

Meanwhile the Depository Trust & Clearing Corporation (DTCC) had finished a July production trial and was preparing to launch its tokenization service at the end of October [4,5]. The same listed share now had two routes into tokenized stock trading. One runs inside existing market infrastructure, where the token represents a share held at DTC and matches against the traditional share in Nasdaq’s order book [3]. The other runs outside it, in permissioned pools on a public blockchain that keep trading when the listing exchange is closed.

This puts the most uncomfortable question to our own thesis. Since The RWA 2.0 Declaration: Blockchain Innovation That Embraces Legacy, we have argued that a token reflects an asset’s whole life only through continuous, bidirectional state synchronization between on-chain and off-chain systems. If incumbent infrastructure can absorb tokenization wholesale, how much of that claim survives? Walking both routes shows where absorption holds and where it ends.

The Inside Route: How the Same Order Book Absorbs Tokenization

On March 18, 2026, the SEC approved a Nasdaq rule under which a tokenized share keeps the same CUSIP and ticker as its traditional counterpart, matches in the same order book with the same execution priority, and settles through DTC on the usual T+1 cycle [3]. The rule covers Russell 1000 stocks and major index ETFs and takes effect once DTC’s tokenization service is ready.

On July 15, more than 30 institutions ran real trades through that service [4]. DTC tokenized assets in its custody and used them in production for collateral pledges, securities lending, Treasury repo, equity trades and central counterparty margin.

The launch scope points the same way [5]. The service starts with 25 equities, ETFs and Treasuries, issued on Canton and on DTCC’s private network. Every token is backed one for one by a security in DTC’s custody, DTC keeps the official books and records, and tokens move around the clock only between wallets registered with DTC.

On this route a token is a new representation of the same asset. When a coupon is paid, a dividend arrives, a stock is halted or a corporate action takes effect, the operator holding the official books processes the change, and keeping token and books consistent is its internal task. Absorption rests on one operator’s perimeter. Because that operator controls every ledger the token can reach, keeping two domains consistent becomes a problem inside a single domain.

Same share, two perimeters Inside, one operator holds every ledger the token can reach; outside, the same share’s state sits in ledgers run by different parties, joined only by three written conditions.
One operator's perimeter inside, ledgers of different parties outside Two routes for trading the same listed share as a token. Inside route, through DTCC's tokenization service and Nasdaq's rule: the Nasdaq order book, with the same CUSIP, ticker and priority as the traditional share, settles via DTC on T+1 into one operator's perimeter, DTC. Inside that perimeter, the official books and records, where coupons, dividends, halts and corporate actions are processed, are kept consistent with the tokens as an internal task; the tokens are on chain, on Canton and DTCC's private network, move only between DTC-registered wallets and are backed one for one by DTC custody. Outside route, through the SEC Innovation Exemption: three ledgers run by different parties, with no common perimeter. The listing exchange decides halts; the issuer and its transfer agent originate dividends and votes; the venue pool is a permissioned automated market maker pool on a public, permissionless chain where token holders trade, and one venue plans to run on Canton. Three dashed links, conditions written in the exemption whose mechanism is left to the venue, run into the pool: concurrent halts from the listing exchange, same rights from the issuer and transfer agent, and issuer objection from the issuer, 30 days, per venue. Colour marks the sync degree: the one-operator perimeter, halts and the concurrent-halts link in the colour of Atomic State Binding (S3); coupons, dividends, votes and the same-rights link in the colour of Bidirectional Coupling (S2); corporate actions and issuer objection neutral. Inside routeDTCC tokenization service · Nasdaq ruleNasdaq order booksame CUSIP, ticker and priorityOne operator: DTCsettles via DTC, T+1Official books and recordscoupondividendhaltcorporate actionTokens on chainCanton · DTCC private networkDTC-registered wallets only1:1 backed by DTC custodykept consistentinternal taskOutside routeSEC Innovation ExemptionListing exchangehaltIssuer and transfer agentdividendvoteVenue poolpermissioned market maker poolpublic, permissionless chaintoken holders tradeone venue plans Cantonhaltdividendvoteconcurrent haltssame rightsissuer objection30 days, per venueinside one operator's bookscondition written; mechanism left to the venueAtomic State Binding (S3)Bidirectional Coupling (S2) One operator's perimeter inside, ledgers of different parties outside Two routes for trading the same listed share as a token. Inside route, through DTCC's tokenization service and Nasdaq's rule: the Nasdaq order book, with the same CUSIP, ticker and priority as the traditional share, settles via DTC on T+1 into one operator's perimeter, DTC. Inside that perimeter, the official books and records, where coupons, dividends, halts and corporate actions are processed, are kept consistent with the tokens as an internal task; the tokens are on chain, on Canton and DTCC's private network, move only between DTC-registered wallets and are backed one for one by DTC custody. Outside route, through the SEC Innovation Exemption: three ledgers run by different parties, with no common perimeter. The listing exchange decides halts; the issuer and its transfer agent originate dividends and votes; the venue pool is a permissioned automated market maker pool on a public, permissionless chain where token holders trade, and one venue plans to run on Canton. Three dashed links, conditions written in the exemption whose mechanism is left to the venue, run into the pool: concurrent halts from the listing exchange, same rights from the issuer and transfer agent, and issuer objection from the issuer, 30 days, per venue. Colour marks the sync degree: the one-operator perimeter, halts and the concurrent-halts link in the colour of Atomic State Binding (S3); coupons, dividends, votes and the same-rights link in the colour of Bidirectional Coupling (S2); corporate actions and issuer objection neutral. Inside routeDTCC tokenization service · Nasdaq ruleNasdaq order booksame CUSIP, ticker and priorityOne operator: DTCsettles via DTC, T+1Official books and recordscoupondividendhaltcorporate actionkept consistentinternal taskTokens on chainCanton · DTCC private networkDTC-registered wallets only1:1 backed by DTC custodyOutside routeSEC Innovation ExemptionListing exchangehaltconcurrent haltsVenue poolpermissioned market maker poolpublic, permissionless chaintoken holders tradeone venue plans Cantonhaltdividendvotesame rightsissuer objection30 days, per venueIssuer and transfer agentdividendvoteinside one operator's bookscondition written in the exemptionmechanism left to the venueAtomic State Binding (S3)Bidirectional Coupling (S2)
Figure 1Who Holds the Books on Each Route

Why Tokenized Treasuries Get Absorbed

Absorbable assets are often read as simple assets. Treasuries and money market funds have stable prices and plain structures, the argument goes, so they fit existing infrastructure, and only complex assets need anything new. That reading misplaces the cause.

A Treasury pays interest and matures. Our sync degree hierarchy sorts assets into four levels by the synchronization they need to perform their financial function. Periodic interest and a maturity date place an asset at Bidirectional Coupling (S2), where transitions in two domains must be bound as one causal unit. Once it becomes the subject of a regulatory action such as a freeze, it rises to Atomic State Binding (S3), where both domains succeed together or fail together. A tokenized Treasury does not demand little.

DTC can absorb it because a single party carries that demand. The hierarchy defines the sync degree over pairs of an asset and a system, so the same Treasury can leave its demand as an internal matter or spread it across several parties, depending on which system handles it. DTC operates every ledger its tokens can reach, so coupons, maturity and freezes resolve in its own books in one pass. What became simple is the shape of the ledger.

The Outside Route: What the Exemption Had to Write Down

The Innovation Exemption opens different ground [2]. A Tokenized Securities Venue carries tokenized stock trading through permissioned automated market maker pools on public, permissionless blockchains, without registering as an exchange. By late October three firms had told the SEC they intend to operate such venues, and one of them plans to run on Canton, the network DTCC uses on the inside route [6]. One chain sits on both routes. What separates them is who holds the books, not the technology.

Of the exemption’s many conditions, three require the token’s state to follow a state that lives somewhere else.

  • Same rights. The token must carry the rights and privileges of the underlying share, so dividends and votes must reach token holders. A dividend starts with the issuer and its transfer agent, while the holders sit on a public chain.
  • Concurrent halts. When the primary listing exchange halts a stock, the venue must stop trading the token concurrently. The halt is decided in the exchange’s systems, while the trades that must stop happen in a pool on a public chain.
  • Issuer objection. For a stock the issuer did not tokenize itself, the venue must notify the issuer and wait 30 days, and an objection in that window keeps the stock off that venue. Issuers object venue by venue.
Tokenized stock trading desk: a sticky note reading concurrently = S3 beside a highlighted rule

The halt condition, the moment it clicked: “concurrently” is S3.

Volume is capped too. A stock in the S&P 500 or the Russell 1000 can trade on one venue only up to 0.25% of its prior-month average daily volume, and a venue may list at most 75 such stocks [2].

Side by side, the three conditions read as one specification. Same rights asks every state change on the issuer’s side to reach the holders on the chain, which is bidirectional coupling. Concurrent halts ask that no state exist in which one domain has stopped and the other has not, which is atomic state binding. An issuer objection is a decision by a party with authority that takes effect in particular ledgers. The SEC wrote a synchronization specification in the language of market structure.

Each rung contains those below Same rights is met at bidirectional coupling; a concurrent halt is met only at atomic state binding, where the in-between state cannot be reached.
Which sync degree meets each condition of the exemption, and how a halt looks at each degree The exemption's conditions tested on the four sync degrees, an order in which each rung contains the ones below. Each rung also shows how a halt looks there, on two ledgers, the exchange above and the pool below, over a short stretch of time: a thin line is trading, a dark bar is halted, and a coral bar is the gap in which one ledger is halted and the other is not. S3 Atomic State Binding: the halt commits in both ledgers as one transition, or in neither, so the in-between state is unreachable; in the picture one frame holds both ledgers and one step halts both at the same moment: both halt in one step, or neither does. S2 Bidirectional Coupling: transitions are bound in one causal order and mismatches are retried until the ledgers converge; in the picture the ledgers are linked both ways and retried, the exchange halts first and the pool passes through an in-between state before it halts. S1 Unidirectional Observation: a feed reports a halt after it happens, and two one-way feeds are still S1; in the picture the exchange halts, the pool keeps trading, and the news reaches the pool later. S0 Static: one record that does not change, nothing has to move. Halt concurrently, no state with one ledger halted and the other trading, is tested against S1, S2 and S3: at S1 it is not met, a gap of trades after the halt remains; at S2 it is not met, the in-between state is still reachable; at S3 it is met. Same rights, dividends and votes reaching holders on chain, is met at S2. Issuer objection, an authority's decision recorded venue by venue, is not a sync degree. Below: on the outside route today, a pause button and a 0.25% volume cap keep the conditions until an S3 mechanism exists. S3Atomic State Bindingthe halt commits in both ledgers as one transition,or in neither: the in-between state is unreachableexchangepoolone stepboth halt in one step,or neither doesS2Bidirectional Couplingtransitions bound in one causal order;mismatches retried until the ledgers convergeexchangepoolretriedlinked both ways and retried;the in-between state can occurS1Unidirectional Observationa feed reports a halt after it happens(two one-way feeds are still S1)exchangepoollaterthe pool hears aboutthe halt afterwardS0Statica record that does not changerecordone record; nothing has to movehalt concurrently: methalt concurrently: in-between state still reachablehalt concurrently: gap, trades after the haltsame rights: metThe exemption's conditionstradinghaltedgapHalt concurrentlyno state with one ledgerhalted and the other tradingIssuer objectionan authority's decision,recorded venue by venuenot a sync degreeSame rightsdividends and votesreach holders on chain Which sync degree meets each condition of the exemption, and how a halt looks at each degree The exemption's conditions tested on the four sync degrees, an order in which each rung contains the ones below. Each rung also shows how a halt looks there, on two ledgers, the exchange above and the pool below, over a short stretch of time: a thin line is trading, a dark bar is halted, and a coral bar is the gap in which one ledger is halted and the other is not. S3 Atomic State Binding: the halt commits in both ledgers as one transition, or in neither, so the in-between state is unreachable; in the picture one frame holds both ledgers and one step halts both at the same moment: both halt in one step, or neither does. S2 Bidirectional Coupling: transitions are bound in one causal order and mismatches are retried until the ledgers converge; in the picture the ledgers are linked both ways and retried, the exchange halts first and the pool passes through an in-between state before it halts. S1 Unidirectional Observation: a feed reports a halt after it happens, and two one-way feeds are still S1; in the picture the exchange halts, the pool keeps trading, and the news reaches the pool later. S0 Static: one record that does not change, nothing has to move. Halt concurrently, no state with one ledger halted and the other trading, is tested against S1, S2 and S3: at S1 it is not met, a gap of trades after the halt remains; at S2 it is not met, the in-between state is still reachable; at S3 it is met. Same rights, dividends and votes reaching holders on chain, is met at S2. Issuer objection, an authority's decision recorded venue by venue, is not a sync degree. Below: on the outside route today, a pause button and a 0.25% volume cap keep the conditions until an S3 mechanism exists. The exemption's conditionsHalt concurrentlyno state with one ledgerhalted and the other tradingSame rightsdividends and votesreach holders on chaintradinghaltedgapS3Atomic State Bindingthe halt commits in both ledgersas one transition, or in neither:the in-between stateis unreachableexchangepoolone stepboth halt in one step,or neither doesS2Bidirectional Couplingtransitions bound in onecausal order; mismatchesretried until the ledgers convergeexchangepoolretriedlinked both ways and retried;the in-between state can occurS1Unidirectional Observationa feed reports a haltafter it happens(two one-way feeds are still S1)exchangepoollaterthe pool hears aboutthe halt afterwardS0Statica record that does not changerecordone record; nothing has to movehalt concurrently: metin-between state still reachablegap: trades after the haltsame rights: metIssuer objectionan authority's decision,recorded venue by venuenot a sync degree
Outside route todayA pause button and a 0.25% volume cap keep the conditions until an S3 mechanism exists
Figure 2Which Sync Degree Meets Each Condition

What “Concurrently” Asks

What the exemption leaves unwritten is as clear as what it writes. It demands an outcome and leaves the mechanism to the venue. The halt is decided in the exchange’s systems, while the pool runs on a public chain whose block timing the venue does not set. If the interval between decision and effect is not zero, the share is halted while the token keeps trading. Halts often come just before material news, so those seconds are when information is most uneven.

For “concurrently” to mean something, events in the two systems must fall into one order that both sides accept: no trade after the halt time, and agreement on which side of it every trade fell. Two ledgers sharing one order of events is the real condition behind a concurrent halt. On the inside route it comes for free, because there is only one ledger.

Concurrently, across two ledgers When a halt decided at the listing exchange reaches the pool late, the share is halted while the token still trades through the gap.
The gap behind a concurrent halt, illustrative timing An illustrative timeline with no time scale. Outside route, two ledgers: on the listing exchange the share trades until the halt is decided, then is halted. In the pool on a public chain the token keeps trading until the halt reaches the pool, then is paused. Between the two moments lies a gap in which the share is halted while the token still trades; the trades in the gap are marked, and such halts often come just before material news, when information is most uneven. Inside route, one ledger: DTC's books and the tokens halt at the same moment, so there is no gap. The gap closes only when the two ledgers share one order of events, so that no trade follows the halt time and both sides agree on which side of it every trade fell. Outside route: two ledgershaltedpausedListing exchangesharePool on a public chaintokenhalt decidedhalt reaches the poolgap: share halted, token tradesoften just before material newsInside route: one ledgershare and token halted, no gapDTC books and tokensshare and tokentime, illustrative (no scale) The gap behind a concurrent halt, illustrative timing An illustrative timeline with no time scale. Outside route, two ledgers: on the listing exchange the share trades until the halt is decided, then is halted. In the pool on a public chain the token keeps trading until the halt reaches the pool, then is paused. Between the two moments lies a gap in which the share is halted while the token still trades; the trades in the gap are marked, and such halts often come just before material news, when information is most uneven. Inside route, one ledger: DTC's books and the tokens halt at the same moment, so there is no gap. The gap closes only when the two ledgers share one order of events, so that no trade follows the halt time and both sides agree on which side of it every trade fell. Outside route: two ledgershalt decidedhalt reachesthe poolListing exchangehaltedpausedPool on a public chaingap: share halted, token tradesoften just before material newsInside route: one ledgerDTC books and tokenshalted together, no gaptime, illustrative (no scale)
Closes the gapAtomic state binding (S3): one order of events, and the halt commits in both ledgers or in neither
Figure 3The Gap Behind a Concurrent Halt

The sync degree hierarchy predicts which mechanisms can make a halt concurrent. A feed that reports the halt to the pool, or two such feeds running in opposite directions, works at Unidirectional Observation (S1): the pool learns of the halt only after the trades it should have refused. A mechanism that binds the two ledgers’ transitions into one causal order reaches Bidirectional Coupling (S2), but it settles mismatches by retrying until the ledgers converge, so one ledger can sit halted while the other still trades.

Making either one faster narrows the gap without removing it, because the condition forbids the state itself, however brief. Only atomic state binding meets the condition as written: the halt commits in both ledgers as one transition or in neither, so the in-between state cannot be reached, under one order of events that both sides can check afterward.

The volume cap reads differently in this light. Beyond a judgment about market size, 0.25% limits the size of a gap that cannot yet be closed. U.S. equities traded about $1.1 trillion a day in 2025 [11]. Even a venue that could list every Tier 1 stock would be held to about $2.75 billion a day, and the 75-stock limit keeps the real ceiling lower. Every dollar under that ceiling must halt concurrently. Until a mechanism exists, a pause button and a cap keep the conditions, and the ceiling marks how much trading the market is asked to run without one.

Market size against the 0.25% cap One venue may trade a Tier 1 stock only up to 0.25% of its daily volume: against USD 1.1T a day of U.S. equities, at most USD 2.75B a day, and every dollar of it must halt concurrently.
One venue's ceiling as one square of 400 squares of U.S. equity trading A unit chart of U.S. equity trading in 2025, about USD 1.1 trillion a day, drawn as 400 equal squares in blocks of 25, so each square is USD 2.75 billion a day, 0.25% of the total; the left edge counts the total down the grid, USD 275 billion, 550 billion, 825 billion and 1.1 trillion. One square, filled, is one venue's Tier 1 ceiling: at most USD 2.75 billion a day, about USD 690 billion a year over 252 trading days, and every dollar under it must halt concurrently, which takes atomic state binding (S3). Two more squares, dashed, bring the three notified venues to at most three squares, USD 8.25 billion a day, an upper bound. The other 397 squares are traded inside the incumbent perimeter. The figures are upper bounds that assume a venue lists every Tier 1 stock; the 75-stock limit keeps the real ceiling lower, and Tier 2 stocks are not drawn.U.S. equity market, 2025USD 1.1T traded a day = 400 squares · one square = USD 2.75B (0.25%)cumulativeone venue's cap275B550B825B1.1TUp to USD 2.75B a dayone venue's Tier 1 ceilingabout USD 690B a yearmust halt concurrently (S3)Up to USD 8.25B a daythree notified venuesupper boundUSD 1.09T a daythe other 397 squares, tradedinside the incumbent perimeter One venue's ceiling as one square of 400 squares of U.S. equity trading A unit chart of U.S. equity trading in 2025, about USD 1.1 trillion a day, drawn as 400 equal squares in blocks of 25, so each square is USD 2.75 billion a day, 0.25% of the total; the left edge counts the total down the grid, USD 275 billion, 550 billion, 825 billion and 1.1 trillion. One square, filled, is one venue's Tier 1 ceiling: at most USD 2.75 billion a day, about USD 690 billion a year over 252 trading days, and every dollar under it must halt concurrently, which takes atomic state binding (S3). Two more squares, dashed, bring the three notified venues to at most three squares, USD 8.25 billion a day, an upper bound. The other 397 squares are traded inside the incumbent perimeter. The figures are upper bounds that assume a venue lists every Tier 1 stock; the 75-stock limit keeps the real ceiling lower, and Tier 2 stocks are not drawn.U.S. equity market, 2025USD 1.1T traded a day = 400 squaresone square = USD 2.75B (0.25%)one venue's cap275B550B825B1.1TUp to USD 2.75B a dayone venue's Tier 1 ceilingabout USD 690B a yearmust halt concurrently (S3)Up to USD 8.25B a daythree notified venuesupper boundUSD 1.09T a daythe other 397 squares, tradedinside the incumbent perimeter
Basis
Upper bounds: a venue listing every Tier 1 stock, 252 trading days; the 75-stock limit keeps the real ceiling lower. Tier 2 stocks (2.5%, 250 stocks) not drawn.Sources: Cboe, 2025 U.S. Equities Year in Review; SEC Release No. 34-106402.
Figure 4The Ceiling on Trading That Must Halt Concurrently

What the Objections Priced In

The market answered quickly. OKXICE, the planned venue of OKX and Intercontinental Exchange (ICE), listed nine objecting issuers in a public notice on October 15 and sixteen on October 19, with Microsoft, Alphabet and Goldman Sachs among the new names [7]. Neither notice gave reasons.

Nasdaq did. As an issuer it said it would keep its own shares off the exemption’s venues, because it did not want them traded where best prices are not displayed in real time and trades are not reported to the consolidated tape. Its FAQ argued that the exemption weakens an issuer’s ability to keep a complete, accurate and contemporaneous view of how its securities are priced and traded [8]. The exchange that won approval for the same-order-book route declined the outside route for its own stock.

Those are synchronization reasons. U.S. equity markets already solved one version of this problem, the same stock trading on many venues, and the consolidated tape and best-price rules are the answer: they bind the prices of scattered venues into one observable state. O’Hara and Ye found that the fragmented U.S. market works like a single virtual market with many points of entry, and that in those conditions fragmentation did not harm market quality [9]. The exemption’s venues stand outside that shared state. What Nasdaq asked for is shared state across venues, which grows from the same root as keeping a token and its share in step.

Where Absorption Ends

Laid over each other, the two routes show where the boundary falls. Absorption holds as long as an asset’s life ends inside one operator’s ledger. While interest, maturity, dividends, corporate actions, halts, freezes and the exercise of rights all resolve in one operator’s books, a token is enough as a new representation in existing infrastructure. The boundary is crossed when the same asset must mean the same thing at the same moment in a ledger another party runs: a venue on a public chain, a DeFi collateral position, a clearinghouse in another jurisdiction.

The inside route approaches the boundary as it grows. DTCC plans to add networks in 2027 [5], and each one is another representation the official books must match. On the collateral side, the European Securities and Markets Authority (ESMA) asked on October 9 whether a central counterparty could access, transfer and convert tokenized collateral into cash if a clearing member defaults [10]. The July trial already ran central counterparty margin, and disposing of collateral in a default is an event in which its state must change in several ledgers together.

Tokenized stock trading sketch on glass: one ledger circle, arrows out to venue, DeFi and CCP

Sorting lifecycle events that end in one ledger from those that cross it.

Restating the RWA 2.0 Claim

This review narrows our thesis. Saying that every tokenized asset needs new infrastructure would overstate it. Much of the tokenized stock trading in large-cap names, and of the trading in tokenized Treasuries, will stay inside incumbent perimeters, where incumbent infrastructure is efficient. The need for new infrastructure begins where the perimeter ends.

The narrower claim is also sturdier, because tokens cross the perimeter by design. The SEC’s exemption exists to let them trade outside it. DeFi collateral, discussed in Why RWA Isn’t Real DeFi Collateral Yet: The Non-Atomicity of the Collateral Layer, has always lived outside it, and so has the cross-border trading examined in Three Layers of Cross-Border Regulatory Conflict in Tokenized Securities. Once a token steps outside, the regulator writes synchronization into the conditions. Starting from market structure, it arrived at the top rung of our sync degree hierarchy.

What remains is atomic state binding between operators, a mechanism that carries those conditions across ledgers run by different parties. Without it, caps and a pause button keep them. Caps are safe, and they keep the market small.

Conclusion: The Market Outside the Same Order Book

The same order book is the route of absorption. While one operator holds an asset’s life, tokenization adds one more representation to existing infrastructure, and that route is real and wide.

On the outside route of tokenized stock trading, synchronization turns from one operator’s internal property into a condition for trading to be allowed at all. The SEC wrote it as one word, concurrently. Where different parties run the ledgers, only atomic state binding makes that word true, and building it is infrastructure work.

So our answer to “if incumbent infrastructure absorbs tokenization, is RWA 2.0 still needed?” is conditional. Where absorption reaches, no. Where it ends, wherever the same asset must mean the same thing in ledgers run by several parties, the need for atomic state binding was there from the start.

Open Questions

  • If a halt decision on the listing exchange and a trade on a public chain land in the same second, who decides which came first, and on what evidence?
  • When an issuer objects to one venue but not another, where can a holder see that the same token carries a different permission state at each venue?
  • Will the consolidated tape extend to tokenized venues, or will tokenized markets build a shared state of their own?
  • As DTC adds networks, does the inside route remain one operator’s ledger, or does it become a federation that needs the same synchronization guarantees?

References

Subscribe

New research, by email.

  • One email when a new article is published
  • Confirm once, leave with one click
  • Privacy