Summary: Ocean Protocol is a decentralized data and compute protocol that turns data access into a layered rights-and-middleware stack. Its current docs make the core mechanism unusually legible: ERC721 Data NFTs represent the base IP or asset container, ERC20 datatokens represent sublicensed access rights, Compute-to-Data keeps private data in place while letting outside algorithms run against it, and Ocean Node bundles the offchain Indexer and Provider layers that actually cache metadata, validate DDOs, check onchain payments and permissions, encrypt and decrypt URLs and metadata, stream data instead of exposing origins, and coordinate compute jobs. That makes Ocean more useful to catalog as tokenized data-access plus operator-run middleware than as a generic AI-data marketplace brand.
What it does:
Lets publishers represent a data asset’s base IP with an ERC721 Data NFT and issue one or more ERC20 datatokens as sublicensed access rights with different terms
Treats 1.0 datatoken as the threshold to consume the corresponding dataset or data service, with spend-to-consume behavior and ordinary ERC20 portability into wallets, DEXes, and DAOs
Supports private-data commercialization through Compute-to-Data, where algorithms run on the same premises as the data and only results leave the data holder’s environment
Uses Ocean Node as the main middleware stack, replacing older Provider, Aquarius, and subgraph components with a combined node that exposes HTTP and libp2p interfaces plus Indexer, Provider, and compute services
Lets marketplace applications such as Ocean Market sit above the protocol to handle discovery, trading, and unlock flows while the underlying contracts and nodes handle rights, fees, and delivery
Key claims:
The official docs describe Ocean as a “decentralized data and compute protocol” whose core tech stack is Data NFTs, datatokens, Ocean Nodes, and Compute-to-Data
Ocean’s contract docs say a Data NFT represents the copyright or exclusive-license base IP of a data asset, while datatokens represent sublicensed access rights; one Data NFT can have multiple datatoken contracts with different license terms
The docs explicitly frame data NFTs plus datatokens as decentralized access control via token-gating, with consuming a data service corresponding to spending datatokens
Ocean’s Compute-to-Data docs say private data stays on-premise while approved third parties run specific compute tasks against it, resolving the privacy-versus-access tradeoff without moving raw data
Current Ocean Node docs say the monorepo replaces the older Provider, Aquarius, and subgraph components, and layers network transport, core components, and modules into one node stack
The Node Architecture docs describe the Indexer as an offchain, multichain metadata and chain-event cache that monitors DDO and datatoken events, validates DDOs against SHACL schemas, and serves queryable proofs and metadata through an API
The same docs describe the Provider layer as the middleware that checks onchain permissions and fee payment, encrypts metadata and source URLs during publish, decrypts them on access, streams data rather than exposing raw URLs, and runs compute services for C2D jobs
The Ocean FAQ says the smart-contract core stack sits on permissionless chains and that anyone can run support middleware, which matters because the real operational control surface still lives partly in whoever runs nodes, indexers, providers, and marketplaces
Whitepaper: Legacy technical whitepaper at https://oceanprotocol.com/tech-whitepaper.pdf. Current docs and Ocean Node materials are a better guide to the present architecture, especially the shift from separate Provider / Aquarius / subgraph components into Ocean Node. Primary-source notes for this pass are saved in ../whitepapers/ocean-protocol-primary-sources-2026-05-15.md.