Data Analytics report

Blocksize RWA Coverage Index

Expansion-catalog sourceability and production-promotion evidence, explicitly separated from existing Blocksize production coverage.

Evidence as of July 22, 2026. This index measures the separate RWA expansion workflow; it does not negate or replace Blocksize's existing live production market-data coverage.

Executive Summary

Blocksize already supplies broad production market data. Separately, the RWA expansion catalog contains 1,025 canonical economic assets and 3,407 token-deployment rows. 90 assets (8.8%) have at least one candidate source lane, while 709 deployment rows (20.8%) are candidate-sourceable. A July 22 read-only verification returned working data from 6 of 7 representative checks across venue APIs, a Solana router quote, and Ethereum/Base RPC pool state. The runtime RWA path did not use Tiingo. No newly sourced third-party or onchain addition has yet cleared every expansion-workflow promotion gate.

Canonical economic assets

1,025Source: RWA coverage reconciliationTable: reports/rwa_coverage_and_client_usage_reconciliation_2026-07-16.md

Expansion catalog denominator.

Expansion catalog denominator.Source: RWA coverage reconciliationTable: reports/rwa_coverage_and_client_usage_reconciliation_2026-07-16.md

Reconciles the 1,025-asset, 1,150-ticker, and 3,407-deployment grains.

Assets with candidate lane

8.8%Source: RWA sourceability summaryTable: reports/rwa_master_sourceability_source_all_summary_2026-07-16.json

Unique economic assets with at least one candidate source lane.

Unique economic assets with at least one candidate source lane.Source: RWA sourceability summaryTable: reports/rwa_master_sourceability_source_all_summary_2026-07-16.json

Aggregate sourceability counts by row, asset, venue, and asset class.

Working representative probes

6Source: Read-only live RWA source checkTable: reports/rwa_live_source_readiness_2026-07-22.json

Representative source lanes returning usable point-in-time observations on July 22, 2026.

of probes run 7Source: Read-only live RWA source checkTable: reports/rwa_live_source_readiness_2026-07-22.json
Representative source lanes returning usable point-in-time observations on July 22, 2026.Source: Read-only live RWA source checkTable: reports/rwa_live_source_readiness_2026-07-22.json

Representative point-in-time probes across venue API, Solana router, and EVM RPC source lanes.

New expansion feeds promoted

0Source: RWA discovery mitigation planTable: reports/rwa_discovery_mitigation_plan.json

New third-party/onchain additions clearing every expansion gate; excludes existing Blocksize production coverage.

New third-party/onchain additions clearing every expansion gate; excludes existing Blocksize production coverage.Source: RWA discovery mitigation planTable: reports/rwa_discovery_mitigation_plan.json

Promotion-gate issue counts and execution phases.

Working data comes from venue APIs and chain infrastructure

The representative checks returned current Hyperliquid order-book data, Gains and Ostium venue prices, a Jupiter Solana route quote, and live Ethereum/Base pool state. The Raydium-labeled check was blocked because Jupiter routed through Byreal; that is the intended anti-mislabeling behavior. These RWA runtime checks have no Tiingo dependency.

Representative live source verification

Source: Read-only live RWA source checkTable: reports/rwa_live_source_readiness_2026-07-22.json

Representative point-in-time probes across venue API, Solana router, and EVM RPC source lanes.

Representative live source verification
VenueSymbolSource laneCheck resultEvidenceTiingo?Promotion
Aerodrome SlipstreamEURC/USDCEvm Rpc Pool StateWorking point-in-time probeEVM JSON-RPC eth_call; block 48985816NoCandidate only; not production-promoted
GainsAAPL/USDVenue Api Reference StreamWorking point-in-time probehttps://backend-pricing.eu.gains.trade/chartsNoCandidate only; not production-promoted
Hyperliquid Rwa SpotAAPL/USDCVenue Api Order BookWorking point-in-time probeHyperliquid /info l2BookNoCandidate only; not production-promoted
Jupiter RouterAAPLX/USDSolana Router QuoteWorking point-in-time probeSource-specific blockerNoCandidate only; not production-promoted
OstiumXAU/USDVenue Api Synthetic MarketWorking point-in-time probehttps://builder.ostium.io/v1/pricesNoCandidate only; not production-promoted
Raydium ClmmAAPLX/USDSolana Route Filtered QuoteBlocked safelySource-specific blockerNoCandidate only; not production-promoted
Uniswap V3 V4PAXG/USDCEvm Rpc Pool StateWorking point-in-time probeEVM JSON-RPC eth_call; block 25591389NoCandidate only; not production-promoted

Key findings

The largest gap is operational source access and adapter readiness, not catalog breadth. The deployment-row view below preserves a consistent 3,407-row denominator.

Deployment-row sourceability disposition
Deployment-row sourceability disposition data
DispositionDeployment rows
Candidate source lane709
Access or adapter required2,698

Candidate sourceability is necessary but not sufficient for production. Promotion remains gated by sustained quality windows, manipulation controls, replay evidence, identifiers, benchmark alignment, and issuer/NAV checks. Gate counts overlap and must not be summed.

Expansion promotion gates with affected feeds
Expansion promotion gates with affected feeds data
Promotion gateAffected feeds
Manipulation Concentration492
Liquidity Depth Volume486
Freshness Cadence442
Replayable Payload442
Venue Identifier127
Blocksize Benchmark Alignment90
Route Or Pool Discovery72
Issuer Nav Alignment67
Token Or Contract Discovery42
State Instrument Confirmation7

Venue concentration shows where adapter and access work can unlock the most deployment rows. It does not imply independent lineage, legal redistribution clearance, or production quality.

Candidate deployment rows by venue

Source: RWA sourceability summaryTable: reports/rwa_master_sourceability_source_all_summary_2026-07-16.json

Aggregate sourceability counts by row, asset, venue, and asset class.

Candidate deployment rows by venue
VenueCandidate rows
Hyperliquid Rwa Spot156Source: RWA sourceability summaryTable: reports/rwa_master_sourceability_source_all_summary_2026-07-16.json
Jupiter Router143Source: RWA sourceability summaryTable: reports/rwa_master_sourceability_source_all_summary_2026-07-16.json
Aevo131Source: RWA sourceability summaryTable: reports/rwa_master_sourceability_source_all_summary_2026-07-16.json
Aster99Source: RWA sourceability summaryTable: reports/rwa_master_sourceability_source_all_summary_2026-07-16.json
Ostium57Source: RWA sourceability summaryTable: reports/rwa_master_sourceability_source_all_summary_2026-07-16.json
Gains55Source: RWA sourceability summaryTable: reports/rwa_master_sourceability_source_all_summary_2026-07-16.json
Uniswap V3 V430Source: RWA sourceability summaryTable: reports/rwa_master_sourceability_source_all_summary_2026-07-16.json
Aerodrome Slipstream25Source: RWA sourceability summaryTable: reports/rwa_master_sourceability_source_all_summary_2026-07-16.json
Curve Stableswap5Source: RWA sourceability summaryTable: reports/rwa_master_sourceability_source_all_summary_2026-07-16.json
Apex Omni4Source: RWA sourceability summaryTable: reports/rwa_master_sourceability_source_all_summary_2026-07-16.json
Hyperliquid Spot3Source: RWA sourceability summaryTable: reports/rwa_master_sourceability_source_all_summary_2026-07-16.json
Balancer Pools1Source: RWA sourceability summaryTable: reports/rwa_master_sourceability_source_all_summary_2026-07-16.json

Recommended next steps

  1. Resolve native identifiers and source access for the highest-yield candidate venues.
  2. Run continuous quality windows and persist replayable payload evidence.
  3. Apply manipulation, concentration, and Blocksize benchmark gates before consensus inclusion.
  4. Promote only when every required technical, lineage, issuer, and rights gate passes.

Further questions

Which candidate venues produce the fastest incremental asset coverage after rights and adapter effort? Which catalog assets are already covered by existing Blocksize products but need a clearer RWA taxonomy mapping?

Caveats

Catalog assets, ticker strings, token deployments, venue rows, and production feeds are different grains. Candidate-sourceable does not mean licensed, independent, manipulation-resistant, or production-promoted. A point-in-time success does not replace continuous freshness, replay, manipulation, benchmark, consensus, rights, and signoff windows. The zero-promotion statement applies only to new expansion sources.

Sources

  1. RWA sourceability summaryreports/rwa_master_sourceability_source_all_summary_2026-07-16.json · python · 2026-07-22T00:00:00Z

    Aggregate sourceability counts by row, asset, venue, and asset class.

    SQL query
    SELECT * FROM sourceability_summary
  2. RWA discovery mitigation planreports/rwa_discovery_mitigation_plan.json · python · 2026-07-22T00:00:00Z

    Promotion-gate issue counts and execution phases.

    SQL query
    SELECT issue_id, affected_feed_count, clear_feed_count, severity FROM mitigation_issues WHERE affected_feed_count > 0 ORDER BY affected_feed_count DESC
  3. RWA coverage reconciliationreports/rwa_coverage_and_client_usage_reconciliation_2026-07-16.md · python · 2026-07-22T00:00:00Z

    Reconciles the 1,025-asset, 1,150-ticker, and 3,407-deployment grains.

    SQL query
    SELECT canonical_assets, ticker_strings, deployment_rows FROM coverage_reconciliation
  4. Read-only live RWA source checkreports/rwa_live_source_readiness_2026-07-22.json · python · 2026-07-22T00:00:00Z

    Representative point-in-time probes across venue API, Solana router, and EVM RPC source lanes.

    SQL query
    SELECT venue, requested_symbol, source_lane, status, observation FROM live_source_readiness_check