1
0
mirror of https://github.com/oceanprotocol/docs.git synced 2024-11-02 00:05:35 +01:00
docs/user-guides/compute-to-data/README.md

1.5 KiB

description
How to sell compute jobs on your datasets while keeping your data and algorithms private

Sell NFT Outputs

Introducing, The Problem

{% embed url="https://media0.giphy.com/media/v1.Y2lkPTc5MGI3NjExNjNmMTc3MjFjNTg2MjQwZTQyY2VkNzFiNjk1YzM5ZmJkM2NjMzA4ZiZlcD12MV9pbnRlcm5hbF9naWZzX2dpZklkJmN0PWc/17FxSFyYNOgThnonDK/giphy.gif" fullWidth="false" %}

Anyone could buy your NFT assets and then publicly share them all over the internet. Pretty scary, right? But what if there was a way that buyers could access valuable insights from your data and algorithms without actually *seeing* the data or algorithms themselves? We have a solution for that!

Enter, Compute-to-Data (also lovingly called C2D 🥰). Ocean Protocol's C2D feature enables you to monetize the OUTPUT of compute jobs on your datasets without revealing the contents of the data/algorithms themselves. Let's dive in how!

How to Compute-to-Data 💃

You will need to accomplish 3 main steps in establishing a compute-to-data flow: create an algorithm that's compatible with C2D, publish your C2D-specific algorithm NFT, then publish your data NFT with C2D configurations allowing the algorithm to compute on it. That's it! Then you'll be able to sell compute jobs 🤩 Follow the steps in this section's three subpages to create & sell a compute job from start to finish. 💪😃