What It Takes to Operate a Tokenized Stock Market For a team preparing to launch a tokenized stock venue, the SEC’s September 17 Innovation Exemption turns a long-running regulatory discussion into an immediate operating question. The Commission has established a temporary, conditional path for certain venues to trade tokenized NMS stocks through permissioned automated market maker liquidity pools, giving builders a concrete framework around which to organize a business. The exemption creates room for a new market structure to develop, with the prospect of bringing onchain trading infrastructure into one of the world’s largest financial markets. A venue pursuing that opportunity has several systems to bring together before it can operate reliably. Trading contracts need to work alongside participant access controls, market data, monitoring, and reporting. As activity grows, the operator needs a consistent account of what happened across the venue and how that activity relates to the conditions under which it can trade. Much of that work depends on the data infrastructure beneath the market. Trading limits become a data problem Consider the calculation behind a venue’s trading volume. A tokenized stock may trade through multiple pools, with activity distributed across contracts that each record their own transactions. The operator needs to assemble those events into a complete view of trading in the security, apply the relevant measurement period, and compare the result with external market data. The SEC’s order makes this particularly consequential. Its volume conditions reference average daily share volume in the underlying stock during the prior month, and affiliated venues must aggregate their activity when calculating compliance with the limits. That requires a coordinated view across the businesses and contracts in scope. An operator building this calculation needs information beyond the activity recorded by any individual pool contract. Contract addresses must map to the correct security. Trading records need consistent units and timestamps. The reference data used in a calculation must be identifiable, along with the set of affiliated venues whose activity was included. These choices become part of how the market operates. A missing pool or an inconsistent measurement window can change the reported result, while an error in the underlying reference data can make an otherwise correct calculation misleading. The team responsible for monitoring trading needs to understand the figure well enough to act on it and reproduce it later. As the venue adds securities and liquidity, maintaining that consistency becomes a recurring operational workload. One trading history serves several audiences The same activity also feeds the information participants use to evaluate the venue. The exemption calls for publicly available transaction data, including prices, sizes, times, pool addresses, and measures of pool activity. That information supports both market transparency and the SEC’s assessment of how these venues function. SEC statement on transaction transparency A liquidity provider deciding where to commit capital will want to analyze trading patterns and changes in pool composition. The venue’s operations team needs to investigate unusual activity. A reviewer examining a past period needs records that reconcile with what participants saw at the time. Different reporting purposes may require different measurement windows and definitions. A public report and an internal monitoring dashboard can legitimately show different figures for the same security. The operator needs to explain those differences and reproduce each calculation, a task that becomes more difficult when every output depends on an independently assembled dataset. Building these functions on a shared, queryable record gives the venue a more manageable foundation. Teams can define the calculations for each purpose explicitly, preserve the inputs behind them, and trace a published figure back to the activity that produced it. New reporting requirements can then be addressed through that existing record, reducing the need to assemble another data pipeline each time the audience or question changes. Verifiable data as operating infrastructure Space and Time provides the data infrastructure for this kind of market. It indexes onchain activity and allows it to be queried alongside offchain datasets, with Proof of SQL generating cryptographic evidence that a query ran correctly against the committed data. For a tokenized stock venue, that creates a practical way to bring pool activity, security mappings, and reference market data into the same calculation. A query can aggregate trading across the relevant contracts and affiliated venues, while its proof allows the result to be checked independently. The same underlying records can support public reporting, internal analysis, and historical review. This is particularly useful when several organizations need to rely on the output. A venue operator, a liquidity provider, and an oversight function can examine a calculation without each maintaining a separate reconstruction of the market. The operator can show which records and logic produced a figure, with verification available to the party receiving it. Building this capability early also changes the economics of expansion. Every additional pool or security introduces more activity to monitor and explain. A shared data foundation lets the operator extend established calculations as the market grows, keeping reporting and analysis connected to the systems already recording its business. The venues pursuing the SEC’s exemption now have an opportunity to establish how tokenized stock markets operate in practice. Their ability to attract sustained participation will depend partly on how clearly they can account for their own activity. With verifiable data built into that foundation, they can give participants a market they can evaluate and give their own teams the infrastructure to run it as it grows.