Industries/ AI, Data & Compute/ Data Marketplaces

Data Marketplaces on PYRAX

Data marketplaces let organizations buy, sell, and license datasets — from training corpora to real-time feeds — but the core paradox is that a buyer must inspect data to value it, and once seen it is copied for free. PYRAX resolves this with compute-to-data: PYRAX Compute runs the buyer's model against the seller's private dataset in place, and only a verified ComputeReceipt and payment cross the wire, so value is exchanged without the raw data ever leaving the owner.

Market size
$1.1B (2024)
Projection
$16.3B by 2033 · ~35% CAGR

The market

$1.1B
Data marketplace market (2024)
70%
Enterprise data-monetization interest
~55%
Share of data that is 'dark'/unused
$4.9M
Cost of a data breach (avg.)

Source: Precedence Research, 2024. Figures are indicative and provided for context.

What's broken today

Sellers must expose samples to prove value, and buyers can copy or resell what they preview.
Regulated and proprietary data (health, financial, biometric) can rarely be moved off-premises at all.
Buyers cannot verify a dataset's provenance, freshness, or that a model was actually trained on it.
Royalties and licensing terms are hard to enforce once data has changed hands.

How PYRAX transforms it

Concrete network elements mapped to this business.

Compute-to-data via PYRAX Compute

Buyers submit a training or query job that executes against the seller's dataset in place; the data never moves, and only the receipted result and payment are exchanged.

Content-addressed encrypted storage

Datasets are stored encrypted and referenced by content hash, so any use is pinned to an immutable, verifiable version of the exact data licensed.

Shielded transfers + viewing keys

Purchases, access grants, and usage stay private on-chain, while scoped viewing keys let a regulator or auditor confirm a licensed use without seeing the underlying records.

On-chain escrow + programmable royalties

Escrow releases payment against a verified ComputeReceipt, and multi-VM contracts split royalties to every upstream data contributor automatically on each access.

eth_getProof verifiable state

Provenance, license terms, and access logs are provable directly from state proofs, so buyers can independently verify a dataset's lineage and rights.

Buildathon: dApp ideas

Ship-ready concepts for data marketplaces on PYRAX.

DataInPlace

01

Compute-to-data marketplace where buyers run models against private datasets that never leave the seller's node.

Compute-to-dataPYRAX Compute

ProvenanceVault

02

Content-addressed registry that binds every dataset to an immutable hash and a verifiable lineage trail.

StorageComputeReceipt

RoyaltySplit

03

Contract that pays every upstream contributor their share automatically on each licensed access.

EVMEscrow

ShieldLicense

04

Private licensing rail where purchases are shielded and each grant issues a scoped viewing key for auditors.

ShieldedGov

FeedEscrow

05

Streaming-data subscription that escrows PYRX and meters delivery of real-time feeds per verified batch.

EscrowPYRAX Compute

TrainReceipt

06

Training broker that returns a ComputeReceipt proving a model was fit on the exact licensed corpus.

ComputeReceiptCompute-to-data

ConsentledData

07

Individual-consent marketplace letting people license their personal data with revocable, viewing-key-scoped access.

ShieldedCairo

LineageProof

08

Provenance verifier that uses eth_getProof to attest a dataset's version and terms to any consumer.

ZKStorage