Data Analytics report

Blocksize Oracle Lineage & Rights Evidence Index

Source semantics, lineage-independence, and rights evidence for RWA and oracle candidates.

Evidence as of July 22, 2026. This is a product and sourcing control artifact, not legal advice.

Executive Summary

The index covers 34 providers and 34 distinct lineage groups. For 25 providers, a commercial redistribution grant is not stated in the reviewed public evidence. Public APIs, onchain contracts, and signed reports can establish technical access or provenance, but they do not by themselves grant Blocksize the right to redistribute the data.

Officially researched providers

34Source: Official-source rights and lineage matrixTable: reports/rwa_official_source_rights_lineage_matrix_2026-07-16.csv

Rows backed by linked public provider materials.

Rows backed by linked public provider materials.Source: Official-source rights and lineage matrixTable: reports/rwa_official_source_rights_lineage_matrix_2026-07-16.csv

Provider-by-provider review of price semantics, access, public rights evidence, lineage, and official sources.

Redistribution not externally documented

25Source: Official-source rights and lineage matrixTable: reports/rwa_official_source_rights_lineage_matrix_2026-07-16.csv

Provider rows whose public evidence does not state a commercial redistribution grant.

Provider rows whose public evidence does not state a commercial redistribution grant.Source: Official-source rights and lineage matrixTable: reports/rwa_official_source_rights_lineage_matrix_2026-07-16.csv

Provider-by-provider review of price semantics, access, public rights evidence, lineage, and official sources.

Distinct lineage groups

34Source: Official-source rights and lineage matrixTable: reports/rwa_official_source_rights_lineage_matrix_2026-07-16.csv

Economic/source dependency groups used to avoid double-counting.

Economic/source dependency groups used to avoid double-counting.Source: Official-source rights and lineage matrixTable: reports/rwa_official_source_rights_lineage_matrix_2026-07-16.csv

Provider-by-provider review of price semantics, access, public rights evidence, lineage, and official sources.

Key findings

Source categories span venues, oracle networks, issuers, commercial market-data partners, and infrastructure. Their values are not interchangeable: executable books, reference marks, issuer NAV, and oracle aggregates need different labels and quality gates.

Providers by researched category
Providers by researched category data
CategoryProviders
Tokenized Issuer9
Oracle7
Venue7
Commercial Market-Data Partner2
Managed Rpc Infrastructure2
Oracle Commercial2
Tokenized Issuer Platform2
Oracle Publisher1
Oracle Publisher Vendor1
Tokenized Issuer Broker1

Public documentation most often leaves commercial redistribution unstated or agreement-scoped. That is a diligence queue, not evidence that use is forbidden or granted.

Public commercial-redistribution evidence status
Public commercial-redistribution evidence status data
Evidence statusProviders
Not externally documented25
Agreement or license required6
Restricted / not granted3

Lineage groups prevent false source diversity. A vendor aggregate, its component venues, and a downstream oracle report cannot automatically be counted as independent confirmations of the same price.

Provider lineage and rights evidence

Source: Official-source rights and lineage matrixTable: reports/rwa_official_source_rights_lineage_matrix_2026-07-16.csv

Provider-by-provider review of price semantics, access, public rights evidence, lineage, and official sources.

Provider lineage and rights evidence
ProviderCategoryLineage groupExternal rights evidence
AevoVenueaevo_native_book; options and perps separate from external index/oracle lineageNot externally documented
AlchemyManaged Rpc Infrastructurealchemy_rpc_transport; preserve the underlying chain/protocol lineageRestricted / not granted
API3Oracleapi3_beacon_set; each API provider can be lineage-tagged, but an aggregate dAPI is one compositeNot externally documented
AsterVenueaster_native_book; do not conflate Aster source with upstream oracle/indexNot externally documented
Chainlink Data Feeds / SmartDataOraclechainlink_aggregate; SmartData/NAV must keep issuer administrator lineage; multiple chain deployments are not independentNot externally documented
Chainlink Data StreamsOracle Commercialchainlink_streams; correlated with Chainlink feeds if overlapping upstreamsAgreement or license required
ChronicleOraclechronicle_aggregate; source identities/quality tier should remain attachedNot externally documented
Databento US EquitiesCommercial Market-Data Partnerdatabento_dataset_plus_underlying_venues; a vendor composite is not independent from its licensed venue inputsAgreement or license required
DinariTokenized Issuer Brokerdinari_sip_or_dfn; official-exchange lineage, not independent from CTA/UTP or other SIP vendorsAgreement or license required
DriftVenuedrift_dlob; vAMM and indicative-quote components must remain tagged and not counted as independentNot externally documented
Franklin Templeton / BenjiTokenized Issuerfranklin_transfer_agent_nav; all chain deployments are one fund/TA sourceNot externally documented
Gains NetworkVenuegains_don_reference; do not treat pair price as venue book depthNot externally documented
Hyperliquid / HIP-3Venuehyperliquid_native_book; each HIP-3 dex and its deployer oracle must retain separate lineageNot externally documented
MatrixdockTokenized Issuermatrixdock_issuer_quote; external Chainlink XAU/USD or SmartData may be upstream and must be taggedNot externally documented
MidasTokenized Issuermidas_reference_oracle; verification agent and issuer oracle are not separate price sourcesNot externally documented

34 results · Showing first 15

Recommended next steps

  1. Attach executed contract or license references to each production source.
  2. Keep executable, indicative, oracle, NAV, and derived price semantics explicit in every receipt.
  3. Require lineage-group checks before consensus calculations.
  4. Reconcile the internal policy register against external documentary evidence and counsel-approved decisions.

Further questions

Which high-value providers can supply a written redistribution and signing grant? Which apparent independent sources share an upstream index, venue set, issuer NAV, or oracle aggregate?

Caveats

The external matrix summarizes public materials and is not legal advice. The internal rights register is a policy-state input and may encode approvals not visible in public documentation; it must not be presented as an external contractual grant without the supporting agreement.

Sources

  1. Official-source rights and lineage matrixreports/rwa_official_source_rights_lineage_matrix_2026-07-16.csv · python · 2026-07-22T00:00:00Z

    Provider-by-provider review of price semantics, access, public rights evidence, lineage, and official sources.

    SQL query
    SELECT provider, category, price_semantics, lineage_group, commercial_redistribution_rights, decision_note, official_sources FROM official_source_rights_lineage_matrix
  2. Internal source-rights registerreports/rwa_source_rights.csv · python · 2026-07-22T00:00:00Z

    Internal policy and readiness state, kept separate from public documentary evidence.

    SQL query
    SELECT provider_id, rights_status, production_access_ready, can_redistribute_production FROM internal_source_rights_register