Ocean Protocol primary sources — 2026-05-15

Scope

Primary-source capture for a new Ocean Protocol mechanism page focused on tokenized data-access rights, Ocean Node middleware, and Compute-to-Data.

Primary sources reviewed

• https://oceanprotocol.com/
• https://docs.oceanprotocol.com/discover/what-is-ocean
• https://docs.oceanprotocol.com/discover/faq
• https://docs.oceanprotocol.com/discover/faq.md?ask=What%20are%20the%20core%20onchain%20and%20offchain%20components%20of%20Ocean%20Protocol%20including%20datatokens,%20NFTs,%20compute-to-data,%20provider,%20indexing,%20and%20marketplaces?
• https://docs.oceanprotocol.com/developers/contracts/datanft-and-datatoken
• https://docs.oceanprotocol.com/developers/compute-to-data
• https://docs.oceanprotocol.com/developers/ocean-node
• https://docs.oceanprotocol.com/developers/ocean-node/node-architecture
• https://github.com/oceanprotocol/ocean-node
• https://oceanprotocol.com/tech-whitepaper.pdf

Key source notes

• The current docs describe Ocean as a decentralized data and compute protocol whose live stack centers on Data NFTs, datatokens, Ocean Nodes, and Compute-to-Data.
• Ocean’s access-control model is explicitly two-layered: ERC721 Data NFTs represent the base IP / copyright side of a data asset, while ERC20 datatokens represent sublicensed access rights that can be transferred and priced independently.
• The docs say one Data NFT can issue multiple datatoken contracts with different terms, which makes Ocean analytically closer to a reusable rights-issuance framework than a single-marketplace app.
• Compute-to-Data is presented as the privacy-preserving commercialization layer: algorithms run where the data sits, and only results leave the premises.
• Ocean Node is the current middleware focal point. The docs say it replaces the older Provider, Aquarius, and subgraph components with a single stack.
• Node Architecture materials split Ocean Node into network, component, and module layers, with the two main control-plane components being Indexer and Provider.
• The Indexer is described as an offchain multichain metadata and chain-event cache that monitors DDO and datatoken events, validates DDOs against SHACL schemas, and exposes query APIs and proofs.
• The Provider is described as the operator-facing delivery and policy layer that checks permissions and fee payment onchain, encrypts URLs and metadata at publish time, decrypts them at access time, streams data instead of returning raw URLs, and runs compute services.
• The FAQ says Ocean’s core contracts live on permissionless chains and that anyone can run support middleware, but the practical chokepoints remain obvious in whoever operates node infrastructure, indexers, providers, and marketplaces.
• The older technical whitepaper is still useful as historical framing, but the current docs are a better description of the post-Ocean-Node architecture.

Why this cleared the bar

Ocean is not just another AI-data marketplace pitch. The useful reusable mechanism is the split between base-IP custody, sublicensed access rights, offchain metadata/event indexing, provider-controlled delivery policy, and privacy-preserving compute-at-data-premises execution. That decomposition makes it a strong comparison point for later private-data, storage, indexing, and tokenized-access systems.