mirror of
https://github.com/oceanprotocol/docs.git
synced 2024-11-26 19:49:26 +01:00
Trent McConaghy
GitHub
commit
bb4ffc0c6b
@ -15,6 +15,12 @@ redirects:
|
||||
core-concepts/did-ddo: developers/identifiers.md
|
||||
concepts/ocean-tokens/: discover/basic-concepts.md
|
||||
tutorials/wallets-and-ocean-tokens: discover/wallets-and-ocean.md
|
||||
discover/explore: discover/README.md
|
||||
discover/ocean-101: discover/README.md
|
||||
discover/basic-concepts: user-guides/basic-concepts.md
|
||||
discover/wallets/README: user-guides/wallets/README.md
|
||||
discover/wallets/metamask-setup: user-guides/wallets/metamask-setup.md
|
||||
discover/wallets-and-ocean: user-guides/wallets-and-ocean.md
|
||||
using-ocean-market: user-guides/using-ocean-market.md
|
||||
using-ocean-market/marketplace-publish-data-asset: user-guides/publish-data-nfts.md
|
||||
using-ocean-market/marketplace-download-data-asset: user-guides/buy-data-nfts.md
|
||||
|
||||
BIN
.gitbook/assets/discover/ambassadors.png
Normal file
BIN
.gitbook/assets/discover/ambassadors.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 356 KiB |
BIN
.gitbook/assets/discover/builders.png
Normal file
BIN
.gitbook/assets/discover/builders.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 140 KiB |
BIN
.gitbook/assets/discover/c2d-mental-model.png
Normal file
BIN
.gitbook/assets/discover/c2d-mental-model.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 57 KiB |
BIN
.gitbook/assets/discover/onramp-offramp.png
Normal file
BIN
.gitbook/assets/discover/onramp-offramp.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
BIN
.gitbook/assets/discover/wait.png
Normal file
BIN
.gitbook/assets/discover/wait.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.1 MiB |
BIN
.gitbook/assets/general/dapps.png
Normal file
BIN
.gitbook/assets/general/dapps.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 313 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 459 KiB |
BIN
.gitbook/assets/general/whirlpool.png
Normal file
BIN
.gitbook/assets/general/whirlpool.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 47 KiB |
32
SUMMARY.md
32
SUMMARY.md
@ -1,22 +1,24 @@
|
||||
# Table of contents
|
||||
|
||||
- [👋 Welcome](README.md)
|
||||
- [🌊 Discover](discover/README.md)
|
||||
- [Explore](discover/explore.md)
|
||||
- [Ocean 101](discover/ocean-101.md)
|
||||
- [Basic Concepts](discover/basic-concepts.md)
|
||||
- [Wallets](discover/wallets/README.md)
|
||||
- [Set Up MetaMask Wallet](discover/wallets/metamask-setup.md)
|
||||
- [🌊 Discover Ocean](discover/README.md)
|
||||
- [Why Ocean?](discover/why-ocean.md)
|
||||
- [What is Ocean?](discover/what-is-ocean.md)
|
||||
- [What can you do with Ocean?](discover/benefits.md)
|
||||
- [OCEAN: The Ocean token](discover/ocean-token.md)
|
||||
- [Networks](discover/networks/README.md)
|
||||
- [Bridges](discover/networks/bridges.md)
|
||||
- [Manage Your OCEAN](discover/wallets-and-ocean.md)
|
||||
- [Glossary](discover/glossary.md)
|
||||
- [Network Bridges](discover/networks/bridges.md)
|
||||
- [FAQ](discover/faq.md)
|
||||
- [Glossary](discover/glossary.md)
|
||||
- [📚 User Guides](user-guides/README.md)
|
||||
- [Guide to the Ocean Market](user-guides/using-ocean-market.md)
|
||||
- [Publish Data NFTs](user-guides/publish-data-nfts.md)
|
||||
- [Buy NFT Data](user-guides/buy-data-nfts.md)
|
||||
- [Sell NFT Computations (Compute-to-Data)](user-guides/compute-to-data/README.md)
|
||||
- [Basic concepts](user-guides/basic-concepts.md)
|
||||
- [Using Wallets](user-guides/wallets/README.md)
|
||||
- [Set Up MetaMask](user-guides/wallets/metamask-setup.md)
|
||||
- [Manage Your OCEAN](user-guides/wallets-and-ocean.md)
|
||||
- [Using Ocean Market](user-guides/using-ocean-market.md)
|
||||
- [Publish Data NFTs](user-guides/publish-data-nfts.md)
|
||||
- [Buy NFT Data](user-guides/buy-data-nfts.md)
|
||||
- [Compute-to-Data in Ocean Market](user-guides/compute-to-data/README.md)
|
||||
- [Make a Boss C2D Algorithm](user-guides/compute-to-data/make-a-boss-c2d-algorithm.md)
|
||||
- [Publish a C2D Algorithm NFT](user-guides/compute-to-data/publish-a-c2d-algorithm-nft.md)
|
||||
- [Publish a C2D Data NFT](user-guides/compute-to-data/publish-a-c2d-data-nft.md)
|
||||
@ -111,8 +113,8 @@
|
||||
* [👀 Predictoor](predictoor/README.md)
|
||||
* [Introduction](predictoor/pdr-intro.md)
|
||||
* [Architecture](predictoor/pdr-architecture.md)
|
||||
* [Parameters](predictoor/pdr-parameters.md)
|
||||
* [How to Earn](predictoor/pdr-earn.md)
|
||||
* [How to Earn](predictoor/pdr-earn.md)
|
||||
* [Parameters](predictoor/pdr-parameters.md)
|
||||
* [Pdr FAQ](predictoor/pdr-faq.md)
|
||||
* [Pdr Resources](predictoor/pdr-resources.md)
|
||||
* [💰 Data Farming](data-farming/README.md)
|
||||
|
||||
@ -52,3 +52,10 @@ The [networks docs](../discover/networks/README.md) have more info about network
|
||||
- Main DF github repos: [df-py (backend)](https://github.com/oceanprotocol/df-py), [df-web (frontend)](https://github.com/oceanprotocol/df-web)
|
||||
- The [Ocean Data Farming Series](https://blog.oceanprotocol.com/ocean-data-farming-series-c7922f1d0e45) blog has a chronological account of all Data Farming activities since its inception. It links to related blog posts.
|
||||
|
||||
|
||||
----
|
||||
|
||||
_Next: [Passive DF (and veOCEAN)](passivedf.md)_
|
||||
|
||||
_Back: [Docs main](../README.md)_
|
||||
|
||||
|
||||
@ -67,3 +67,10 @@ Where in Predictoor and Predictoor DF, values are:
|
||||
**Rapid compounding.** In other DF streams, rewards come weekly; so compounding is weekly. In Predictoor and Predictoor DF, a predictoor's revenue (rewards) come every epoch (every 5min or 1h). Therefore compounding in Predictoor could be _very_ fast, for much healthier yields yet.
|
||||
|
||||
**Estimation fidelity.** Since Predictoor is so young, we don't have detailed estimates of Predictoor APYs yet. We're excited to see where this takes us:)
|
||||
|
||||
|
||||
----
|
||||
|
||||
_Next: [FAQ](faq.md)_
|
||||
|
||||
_Back: [APYs](apys.md)_
|
||||
|
||||
@ -47,3 +47,9 @@ Costs should not be under-estimated. Eg if you're only doing Passive DF, and you
|
||||
|
||||
The **[guide to estimate APYs](apys-guide.md)** drills deeper into estimating APYs.
|
||||
|
||||
|
||||
----
|
||||
|
||||
_Next: [APYs Guide](apys-guide.md)_
|
||||
|
||||
_Back: [Reward Schedule](reward-schedule.md)_
|
||||
|
||||
@ -33,3 +33,9 @@ You will need to wait at least one week, but not more than two weeks to claim yo
|
||||
### Forgot to claim?
|
||||
|
||||
If you forget to claim your OCEAN rewards, then do not worry because they continue to accumulate! It's all fine. You can claim them anytime after Thursday. 😃
|
||||
|
||||
----
|
||||
|
||||
_Next: [Reward Schedule](reward-schedule.md)_
|
||||
|
||||
_Back: [Predictoor DF Guide](predictoordf-guide.md)_
|
||||
|
||||
@ -284,4 +284,12 @@ veFeeDistributor has a start\_time of 1663804800 (Thu Sep 22 2022 00:00:00).
|
||||
|
||||
## Notes
|
||||
|
||||
[1] The initial version of Data Farming - in DF Alpha phase (DF1-DF4) - _did_ involve providing liquidity to datatoken pools, and therefore did incur risk of Impermanent Loss (IL). For this reason and others, we moved away from pools, to veOCEAN for the DF/VE Alpha phase and beyond (>=DF5). Therefore there has been no IL risk since then. [Here are details](https://blog.oceanprotocol.com/veocean-is-launching-data-farming-is-resuming-abed779211e3).
|
||||
[1] The initial version of Data Farming - in DF Alpha phase (DF1-DF4) - _did_ involve providing liquidity to datatoken pools, and therefore did incur risk of Impermanent Loss (IL). For this reason and others, we moved away from pools, to veOCEAN for the DF/VE Alpha phase and beyond (>=DF5). Therefore there has been no IL risk since then. [Here are details](https://blog.oceanprotocol.com/veocean-is-launching-data-farming-is-resuming-abed779211e3).
|
||||
|
||||
----
|
||||
|
||||
Congrats! You've completed reading Data Farming docs.
|
||||
|
||||
_Next: Jump to [Docs main](../README.md) and click on your interest._
|
||||
|
||||
_Back: [APYs Guide](apys-guide.md)_
|
||||
|
||||
@ -56,3 +56,10 @@ psdnOCEAN contract & token info can be found at:
|
||||
- [CoinGecko](https://www.coingecko.com/en/coins/poseidon-ocean)
|
||||
- [GeckoTerminal](https://www.geckoterminal.com/eth/pools/0xf8c4cd95c7496cb7c8d97202cf7e5b8da2204c2b)
|
||||
|
||||
|
||||
----
|
||||
|
||||
_Next: [Volume DF](volumedf.md)_
|
||||
|
||||
_Back: [Passive DF Guide](passivedf-guide.md)_
|
||||
|
||||
|
||||
@ -49,3 +49,11 @@ In this step you will:
|
||||
- Accept the transaction in your wallet.
|
||||
|
||||
Congratulations! You have now locked your OCEAN for veOCEAN and are generating passive yield automatically. You can [claim your passive OCEAN rewards](claim-rewards.md) every Thursday - note that your first time claiming rewards will require at least one week, but not more than 2 weeks of wait!
|
||||
|
||||
|
||||
----
|
||||
|
||||
_Next: [Liquid Staking](liquid-staking.md)_
|
||||
|
||||
_Back: [Passive DF (and veOCEAN)](passivedf.md)_
|
||||
|
||||
|
||||
@ -100,3 +100,10 @@ We have built [a new contract](https://github.com/oceanprotocol/contracts/blob/m
|
||||
|
||||
We have an [ongoing bug bounty via Immunefi](https://immunefi.com/bounty/oceanprotocol/) for Ocean software, including veOCEAN and DF components. If you identify an issue, please report it there and get rewarded.
|
||||
|
||||
|
||||
----
|
||||
|
||||
_Next: [Guide to Passive DF](passivedf-guide.md)_
|
||||
|
||||
_Back: [DF Main](README.md)_
|
||||
|
||||
|
||||
@ -28,5 +28,8 @@ In Predictoor DF (and Predictoor proper), you run prediction bots to earn contin
|
||||
- ⚠️ **To be eligible** for a given DF round: you MUST run [OCEAN payout script](https://github.com/oceanprotocol/pdr-backend/blob/main/READMEs/payout.md) <= 4 days after the round ends, i.e. between Thu 00:00 UTC & Sun 11:59 PM UTC
|
||||
- **To claim:** See the [payout README](https://github.com/oceanprotocol/pdr-backend/blob/main/READMEs/payout.md) for specific instructions.
|
||||
|
||||
----
|
||||
|
||||
_Next: [Claim Rewards](claim-rewards.md)_
|
||||
|
||||
_Back: [Predictoor DF](predictoordf.md)_
|
||||
|
||||
@ -93,3 +93,9 @@ Therefore `DCV_bound` is higher. Specifically: `DCV_bound = 37500 * (0.001 + 0.2
|
||||
The BTC/USDT 5m and 1h feeds follow the same Volume DF mechanics as the other feeds, despite being free on the webapp.
|
||||
|
||||
Details: the BTC feeds _are_ priced at the smart contract level. The webapp receives datatokens for those feeds and makes the prediction values public. Because the BTC feeds _are_ priced, then: their DCV is non-negligible; allocating veOCEAN to them makes sense; and Volume DF rewards accrue to them as well.
|
||||
|
||||
----
|
||||
|
||||
_Next: [Predictoor DF Guide](predictoordf-guide.md)_
|
||||
|
||||
_Back: [Volume DF Guide](volumedf-guide.md)_
|
||||
|
||||
@ -71,4 +71,11 @@ The image below shows the total OCEAN released by DF for the first 20 years. The
|
||||
|
||||
## Further resources
|
||||
|
||||
The blog post ["Data Farming Main is here"](https://blog.oceanprotocol.com/ocean-data-farming-main-is-here-49c99602419e) provides further detail yet.
|
||||
The blog post ["Data Farming Main is here"](https://blog.oceanprotocol.com/ocean-data-farming-main-is-here-49c99602419e) provides further detail yet.
|
||||
|
||||
|
||||
----
|
||||
|
||||
_Next: [APYs](apys.md)_
|
||||
|
||||
_Back: [Claim Rewards](claim-rewards.md)_
|
||||
|
||||
@ -40,3 +40,9 @@ We'll show you how!
|
||||
|
||||
That's it! You've successfully allocated (aka "voted on") your favorite assets in the Ocean ecosystem using your veOCEAN and are generating active rewards yield. Now, just wait until next Thursday to see if you can [claim any OCEAN rewards](claim-rewards.md) on the Active Rewards section of the [Rewards page](https://df.oceandao.org/rewards) for your portion of the assets' sales. Remember that your first time claiming rewards will require at least one week, but not more than 2 weeks of wait!
|
||||
|
||||
|
||||
----
|
||||
|
||||
_Next: [Predictoor DF](predictoordf.md)_
|
||||
|
||||
_Back: [Volume DF](volumedf.md)_
|
||||
|
||||
@ -71,3 +71,10 @@ The actual code is in [calcrewards.py](https://github.com/oceanprotocol/df-py/bl
|
||||
|
||||
When DF restarts each Thursday, the global allocation towards each asset resets back to zero and then starts counting up again until the end of the round. After allocating your veOCEAN to different datasets, it will take time for your voting power to be accounted for.
|
||||
|
||||
|
||||
----
|
||||
|
||||
_Next: [Volume DF Guide](volumedf-guide.md)_
|
||||
|
||||
_Back: [Liquid Staking](liquid-staking.md)_
|
||||
|
||||
|
||||
@ -1,24 +1,43 @@
|
||||
---
|
||||
description: >-
|
||||
Your resource hub for diving deep into the core concepts, exploring main
|
||||
components, and accessing practical examples and integration guides to unleash
|
||||
the power of Ocean Protocol in your applications
|
||||
description:
|
||||
cover: ../.gitbook/assets/cover/developer_banner.png
|
||||
coverY: 0
|
||||
---
|
||||
|
||||
# 👨💻 Developers
|
||||
|
||||
With Ocean, crypto wallets transform into magical data wallets, where your data can roam freely and securely. Crypto exchanges? Well, they've taken on a new role as data marketplaces, where you can showcase and trade your valuable data treasures. And hold on tight because DAOs are here to create epic data co-ops, where collaboration and innovation reign supreme! 🤝
|
||||
### What can you build with Ocean?
|
||||
|
||||
But hold on tight, because we have even more in store for you! With Ocean Protocol, you gain access to a treasure trove of tools that will unlock your data scientist superpowers and allow you to unleash your creativity. Whether you're a Python aficionado or a JavaScript maestro, we have you covered with [ocean.py](../data-scientists/ocean.py/README.md) and [ocean.js](ocean.js/README.md) libraries. So, get ready to dive into the depths of data innovation and create the next groundbreaking dAapp (that's a decentralized App, by the way) using [ocean.js's](ocean.js/README.md) powerful capabilities or unleash your skills with [ocean.py](../data-scientists/ocean.py/README.md). It's time to shake up the data world like never before! 🌐🚀
|
||||
1. **Token-gated dApps & REST APIs**: monetize by making your dApp or its REST API token-gated. [Here's how](https://github.com/oceanprotocol/token-gating-template).
|
||||
1. **AI dApps**: monetize your AI dApp by token-gating on AI training data, feature vectors, models, or predictions.
|
||||
1. **Data Markets**: build a decentralized [data market](../developers/build-a-marketplace/README.md).
|
||||
1. **Private user profile data**: storing user profile data on your centralized server exposes you to liability. Instead, have it on-chain encrypted by the user's wallet, and just-in-time decrypt for the app. [Video](https://www.youtube.com/watch?v=xTfI8spLq1k&ab_channel=ParticleNetwork), [slides](https://docs.google.com/presentation/d/1_lkDVUkA0Rx1R7RpkaSeLkX3PeOBoMQyRhvxjwTvd6A/edit?usp=sharing).
|
||||
|
||||
<figure><img src="../.gitbook/assets/general/developers.png" alt=""><figcaption><p>Ocean Protocol Explorer</p></figcaption></figure>
|
||||
Example live dapps:
|
||||
- **Data Markets**: [Acentrik Market](https://market.acentrik.io/) for enterprises, and [Ocean Market](https://market.oceanprotocol.com) for general.
|
||||
- **Token-gated dapps**: [Autobot](https://autobotocean.com/) for analytics, and [Ocean Waves](https://waves.oceanprotocol.com/) for music.
|
||||
- **Token-gated feeds**: [Ocean Predictoor](https://predictoor.ai) for AI prediction feeds
|
||||
|
||||
At the core of the Ocean Protocol, you'll find a constellation of [smart contracts](contracts/README.md) that bring extraordinary capabilities to every data asset. Here's where the magic happens! Every asset gets its own cool and unique [**ERC721 data NFT**](contracts/data-nfts.md#what-is-a-data-nft), along with one (or more) [**ERC20 datatokens**](contracts/datanft-and-datatoken.md). It's like giving your data its very own superhero cape! 🦸♂️
|
||||
### How do developers start using Ocean?
|
||||
|
||||
These [smart contracts](contracts/README.md) form the backbone of Ocean Protocol, empowering data assets with unparalleled value and enabling seamless integration with the wider blockchain ecosystem. Through the [contracts](contracts/README.md), data becomes not only valuable but also tradable, allowing you to unleash the true potential of your data treasures.
|
||||
- **App level: [Use an Ocean Template](https://oceanprotocol.com/templates)**.
|
||||
- **Library level: [Use ocean.js](ocean.js/README.md)** is a library built for the key environment of dApp developers: JavaScript. Import it & use it your frontend or NodeJS.
|
||||
- **Contract level: [Call Ocean contracts](contracts.md)** on Eth mainnet [or other chains](../discover/networks.md).
|
||||
|
||||
<figure><img src="../.gitbook/assets/contracts/smart-contracts.png" alt=""><figcaption><p>Smart Contracts</p></figcaption></figure>
|
||||
### Developer Docs Quick-links
|
||||
|
||||
Now, if you're new to the world of web3 and blockchain technologies, fear not! We've got you covered. Before diving into the depths of Ocean Protocol, we recommend starting with some introductory guides. These [guides](../user-guides/README.md) will gently introduce you to the magical world of [web3](../discover/wallets/README.md) and help you understand the [basics](../discover/wallets-and-ocean.md) before you embark on your epic data-driven adventure.
|
||||
- [Architecture](architecture.md) - blockchain/contracts layer, middleware, dapps
|
||||
- Earning revenue: [code to get payment](revenue.md), [fractional $](fractional-ownership.md), [community $](community-monetization)
|
||||
- Schemas: [Metadata](metadata.md), [identifiers/DIDs](identifiers.md), [identifier objects/DDOs](ddo-specification.md), [storage](storage.md), [fine-grained permissions](fg-permissions.md)
|
||||
- Components:
|
||||
- [Barge](barge.md) - local chain for testing
|
||||
- [Ocean subgraph](subgraph.md) - grabbing event data from the chain
|
||||
- [Ocean CLI](ocean-cli.md) - command-line interface
|
||||
- [Compute-to-data](compute-to-data.md) - practical privacy approach
|
||||
- [Aquarius](aquarius.md) - metadata cache
|
||||
- [Provider](provider.md) - handshaking for access control
|
||||
- [FAQ](faq.md)
|
||||
|
||||
----
|
||||
|
||||
_Next: [Architecture](architecture.md)_
|
||||
|
||||
@ -1,47 +1,37 @@
|
||||
---
|
||||
description: Why Ocean Protocol?
|
||||
description:
|
||||
cover: ../.gitbook/assets/cover/discover_banner.png
|
||||
coverY: 7.413145539906106
|
||||
---
|
||||
|
||||
# 🌊 Discover
|
||||
# 🌊 Discover Ocean
|
||||
|
||||
{% embed url="https://youtu.be/4P72ZelkEpQ" %}
|
||||
Ocean's mission is to level the playing field for AI and data.
|
||||
|
||||
Society is increasingly reliant on data as AI becomes more popular. However, a small handful of organizations possess and control massive amounts of our personal data, posing a threat to a free and open society ☢️
|
||||
How? **By helping _you_ monetize AI models and data, while preserving privacy.**
|
||||
|
||||
The concentration of vast datasets in the hands of a few organizations can lead to significant negative consequences for society. These include:
|
||||
Ocean is a decentralized data exchange protocol to drive AI. Its core tech is:
|
||||
- Data NFTs & datatokens, to enable token-gated access control, data wallets, data DAOs, and more.
|
||||
- Compute-to-data: buy & sell private data, while preserving privacy
|
||||
|
||||
* 📛 **Monopolistic Control**: When a small number of organizations control large amounts of data and AI tools, they gain a significant advantage over competitors. This can lead to monopolistic behavior, where these organizations dominate the market and stifle competition. As a result, innovation may suffer, prices can be inflated, and consumer choice becomes limited.
|
||||
* 📛 **Single Point of Failure**: Concentrating data in the hands of a few organizations creates a single point of failure. If a breach or data leak occurs within one of these organizations, the impact can be far-reaching, affecting a significant portion of the population whose data is held by that organization. The potential scale of such breaches can be much larger than if data were distributed across multiple entities, making the consequences more severe.
|
||||
* 📛 **Algorithmic Bias and Discrimination**: AI tools rely on data to make decisions and predictions. If the datasets used for training are biased or incomplete, AI systems can perpetuate and amplify existing biases and discrimination. The concentration of datasets in the hands of a few organizations can exacerbate this issue, as their AI models may reflect the biases present in their data, leading to unfair or discriminatory outcomes in various domains, such as hiring, lending, and criminal justice.
|
||||
* 📛 **Lack of Transparency and Accountability**: The complex nature of AI algorithms and the concentration of power make it difficult to understand and scrutinize the decisions made by these systems. When only a few organizations control AI tools, it can limit transparency and accountability. This lack of visibility can lead to distrust in AI systems, as people are unable to understand how decisions are being made or to challenge them when they are unfair or erroneous. The desire to extract value from data can create a conflict between the need to protect individual privacy and the pursuit of business interests.
|
||||
* 📛 **Lack of Privacy**: In today's digital age, traditional data-sharing methods often compromise privacy, raising concerns among individuals and organizations alike. With the increasing amount of personal and sensitive information being collected, stored, and shared, it has become essential to address it.
|
||||
* 📛 **Limited Data Monetization**: Many data owners struggle to monetize their data assets effectively due to various factors. Firstly, they often lack data-driven business models that can translate their data into valuable insights and actionable opportunities. Additionally, data quality and trust play a critical role, as inaccurate or unreliable data hinders the development of data-driven products and erodes trust among potential buyers. Limited market access is another challenge, with the fragmented data economy and the absence of standardized platforms or marketplaces making it difficult for data owners to connect with the right audience.
|
||||
* 📛 **Intermediaries and Inefficiencies**: In the current data economy, intermediaries play a significant role in facilitating data transactions between data owners and data consumers. However, the reliance on intermediaries introduces additional costs and complexities that can hinder efficient data monetization.
|
||||
### Ocean Users Are...
|
||||
|
||||
If we don't enable personal **sovereignty** over our data, then we could be at the mercy of Big Tech's decisions again in the future of Web3. What's worse, we could even be excluded from developing AI innovations entirely. ☢️☠️
|
||||
- **[Developers](../developers/README.md).** Build token-gated AI dApps & APIs
|
||||
- **[Data scientists](../data-scientists/README.md).** Earn via predictions & challenges
|
||||
- **[OCEAN holders](../data-farming/README.md).** Get rewards by locking OCEAN & curating data, via Data Farming.
|
||||
- **[Ocean ambassadors](https://oceanprotocol.com/explore/community)**
|
||||
|
||||
{% embed url="https://giphy.com/clips/spongebob-PPEmM68bHy2zEZUcs7" %}
|
||||
### Quick Links
|
||||
|
||||
That's why we made the decision to take action, and it led to the creation of the **Ocean Protocol**.
|
||||
- [Why Ocean?](why-ocean.md) and [What is Ocean?](what-is-ocean.md)
|
||||
- [What can you do with Ocean?](benefits.md)
|
||||
- [OCEAN: The Ocean token](ocean-token.md)
|
||||
- [Networks](networks/README.md), [Bridges](networks/bridges.md)
|
||||
- [FAQ](faq.md), [Glossary](glossary.md)
|
||||
|
||||
**Ocean Protocol was founded to level the playing field for AI and data.**
|
||||
----
|
||||
|
||||
Ocean’s tools enable people to privately & securely publish, exchange, and consume data.
|
||||
_Next: [Why Ocean?](why-ocean.md)_
|
||||
|
||||
{% hint style="info" %}
|
||||
If you're wondering which types of data can be monetized through Ocean Protocol, the answer is that virtually any kind of data can be sold via the platform! 📊🎶📸🎥💼🎫🌐 This includes AI data, ML models, music data, images, videos, trading data, tickets, and essentially anything that can be accessed online.
|
||||
{% endhint %}
|
||||
_Back: [Docs main](../README.md)_
|
||||
|
||||
To find out more about the amazing team behind Ocean, you can visit the [website](https://oceanprotocol.com/about-us/foundation).
|
||||
|
||||
Now that we've made you curious about our mission and how we're making a difference in the world, you won't want to miss this video featuring our co-founder, [Trent McConaghy](http://www.trent.st/). He'll share some fascinating insights into what we're doing and why it matters.
|
||||
|
||||
{% embed url="https://youtu.be/XN_PHg1K61w" fullWidth="false" %}
|
||||
A new data economy with power to the people - Trent McConaghy
|
||||
{% endembed %}
|
||||
|
||||
### Ocean Protocol Whitepaper
|
||||
|
||||
If you'd like to explore the details of the technology, feel free to dive into the [whitepaper](https://oceanprotocol.com/tech-whitepaper.pdf)! It's a comprehensive resource that explains all the technical details and the core concepts that drive Ocean Protocol. It's a great way to get a deeper understanding of what we're all about.
|
||||
|
||||
@ -1,33 +0,0 @@
|
||||
---
|
||||
description: Learn the Web3 concepts backing up Ocean Protocol tech
|
||||
---
|
||||
|
||||
# Basic Concepts
|
||||
|
||||
You'll need to know a thing or two about **Web3** to understand Ocean Protocol's tech... Let's get started with the basics 🧑🏫
|
||||
|
||||
<figure><img src="../.gitbook/assets/gif/drew-barrymore-notes.gif" alt=""><figcaption><p>Prepare yourself, my friend</p></figcaption></figure>
|
||||
|
||||
### Blockchain: The backbone of Ocean Protocol
|
||||
|
||||
Blockchain is a revolutionary technology that enables the decentralized nature of Ocean Protocol. At its core, blockchain is a **distributed ledger** that securely **records and verifies transactions across a network of computers**. It operates on the following key concepts that ensure trust and immutability:
|
||||
|
||||
* **Decentralization**: Blockchain eliminates the need for intermediaries by enabling a peer-to-peer network where transactions are validated collectively. This decentralized structure reduces reliance on centralized authorities, enhances transparency, and promotes a more inclusive data economy.
|
||||
* **Immutability**: Once a transaction is recorded on the blockchain, it becomes virtually impossible to alter or tamper with. The data is stored in blocks, which are cryptographically linked together, forming an unchangeable chain of information. Immutability ensures the integrity and reliability of data, providing a foundation of trust in the Ocean Protocol ecosystem. Furthermore, it enables reliable traceability of historical transactions.
|
||||
* **Consensus Mechanisms**: Blockchain networks employ consensus mechanisms to validate and agree upon the state of the ledger. These mechanisms ensure that all participants validate transactions without relying on a central authority, crucially maintaining a reliable view of the blockchain's history. The consensus mechanisms make it difficult for malicious actors to manipulate the blockchain's history or conduct fraudulent transactions. Popular consensus mechanisms include Proof of Work (PoW) and Proof of Stake (PoS).
|
||||
|
||||
Ocean Protocol harnesses the power of blockchain to facilitate secure and auditable data exchange. This ensures that data transactions are transparent, verifiable, and tamper-proof. Here's how blockchain is utilized in the Ocean Protocol ecosystem:
|
||||
|
||||
* **Data Asset Representation**: Data assets in Ocean Protocol are represented as non-fungible tokens (NFTs) on the blockchain. NFTs provide a unique identifier for each data asset, allowing for seamless tracking, ownership verification, and access control. Through NFTs and datatokens, data assets become easily tradable and interoperable within the Ocean ecosystem.
|
||||
* **Smart Contracts**: Ocean Protocol utilizes smart contracts to automate and enforce the terms of data exchange. Smart contracts act as self-executing agreements that facilitate the transfer of data assets between parties based on predefined conditions - they are the exact mechanisms of decentralization. This enables cyber-secure data transactions and eliminates the need for intermediaries.
|
||||
* **Tamper-Proof Audit Trail**: Every data transaction on Ocean Protocol is recorded on the blockchain, creating an immutable and tamper-proof audit trail. This ensures the transparency and traceability of data usage, providing data scientists with a verifiable record of the data transaction history. Data scientists can query addresses of data transfers on-chain to understand data usage.
|
||||
|
||||
By integrating blockchain technology, Ocean Protocol establishes a trusted infrastructure for data exchange. It empowers individuals and organizations to securely share, monetize, and leverage data assets while maintaining control and privacy.
|
||||
|
||||
### **OCEAN: Empowering Data Ownership and Monetization**
|
||||
|
||||
OCEAN (**OCEAN**) are the native cryptocurrency of the Ocean Protocol ecosystem. They serve as the medium of exchange for data services, enabling data owners, consumers, and service providers to participate in the data economy. Here's how OCEAN are used within the ecosystem:
|
||||
|
||||
1. **Data Ownership**: OCEAN empowers data owners by providing them with control over their data assets. Through the use of smart contracts, data owners can define access permissions, usage rights, and pricing terms for their data. By holding and staking OCEAN, data owners can exercise even greater control over their data assets.
|
||||
2. **Data Monetization and Consumption**: OCEAN facilitate seamless and secure transactions between data providers and consumers, fostering a thriving new data economy. Data owners can set a price in OCEAN for consumers to access and utilize their data. This creates opportunities for unlocking value from siloed or otherwise unused data.
|
||||
3. **Stake for veOCEAN and Curate Datasets**: Through the Data Farming initiative, you are incentivized to lock OCEAN for [veOCEAN](../data-farming/passivedf.md). By staking your OCEAN, you not only support the growth and sustainability of the ecosystem but also earn a share of data asset sales 💰. The Data Farming initiative offers participants a unique opportunity to earn [rewards](../data-farming/README.md) while making a meaningful impact in the data marketplace.
|
||||
118
discover/benefits.md
Normal file
118
discover/benefits.md
Normal file
@ -0,0 +1,118 @@
|
||||
---
|
||||
description:
|
||||
---
|
||||
|
||||
# What can you do with Ocean?
|
||||
|
||||
This page shows things you can do with Ocean...
|
||||
- As a builder
|
||||
- As a data scientist
|
||||
- As an OCEAN holder
|
||||
- Become an Ocean ambassador
|
||||
|
||||
Let's explore each...
|
||||
|
||||
## What builders can do
|
||||
|
||||
<div align="center"><figure><img src="../.gitbook/assets/general/dapps.png" width="75%"></figure></div>
|
||||
|
||||
<details>
|
||||
|
||||
<summary><mark style="color:black;">Build Your Token-gated AI dApp</mark></summary>
|
||||
|
||||
Monetize by making your dApp token-gated. Users no longer have to use credit cards or manage OAuth credentials. Rather, they buy & spend ERC20 datatokens to access your dApp content.
|
||||
|
||||
Go further yet: rather than storing user profile data on your centralized server -- which exposes you to liability -- have it on-chain encrypted by the user's wallet, and just-in-time decrypt for the app.
|
||||
|
||||
</details>
|
||||
|
||||
|
||||
<details>
|
||||
|
||||
<summary><mark style="color:black;">Build Your Token-gated REST API</mark></summary>
|
||||
|
||||
Focus on the backend: make a Web3-native REST API. Like the token-gated dApps, consumers of the REST API buy access with crypto, not credit cards.
|
||||
|
||||
</details>
|
||||
|
||||
|
||||
<details>
|
||||
|
||||
<summary><mark style="color:black;">Build Your Data Market</mark></summary>
|
||||
|
||||
Build a decentralized data marketplace by [forking Ocean Market code](../developers/build-a-marketplace/) to quickly get something good, or by building up from Ocean components for a more custom look.
|
||||
|
||||
</details>
|
||||
|
||||
To dive deeper, please go to [Developers page](../developers/README.md).
|
||||
|
||||
|
||||
## What data scientists can do
|
||||
|
||||
<div align="center">
|
||||
<figure><img src="../.gitbook/assets/predictoor/predictoor_ui_crop.png"></figure>
|
||||
</div>
|
||||
|
||||
<details>
|
||||
|
||||
<summary><mark style="color:black;">Use Ocean in Python</mark></summary>
|
||||
|
||||
The **[ocean.py](../data-scientists/ocean.py/README.md)** library is built for the key environment of data scientists: Python. Use it to earn $ from your data, share your data, get more data from others, and see provenance of data usage.
|
||||
|
||||
</details>
|
||||
|
||||
|
||||
<details>
|
||||
|
||||
<summary><mark style="color:black;">Do crypto price predictions</mark></summary>
|
||||
|
||||
With [Ocean Predictoor](../predictoor/README.md), you submit predictions for the future price of BTC, ETH etc, and earn. The more accurate your predictions, the more $ you can earn.
|
||||
|
||||
</details>
|
||||
|
||||
|
||||
<details>
|
||||
|
||||
<summary><mark style="color:black;">Compete in a Data Challenge</mark></summary>
|
||||
|
||||
Ocean regularly offer [data science challenges](../data-scientists/join-a-data-challenge) on real-world problems. Showcase your skills, and earn $ prizes.
|
||||
|
||||
</details>
|
||||
|
||||
To dive deeper, please go to [Data Scientists page](../data-scientists/README.md).
|
||||
|
||||
|
||||
## What OCEAN holders can do
|
||||
|
||||
<details>
|
||||
|
||||
<summary><mark style="color:black;">Earn Rewards via Data Farming</mark></summary>
|
||||
|
||||
Ocean's [Data Farming](../data-farming/README.md) incentives program enables OCEAN holders to earn by locking OCEAN, and curating data.
|
||||
|
||||
</details>
|
||||
|
||||
## Become an Ocean Ambassador
|
||||
|
||||
|
||||
<details>
|
||||
<summary><mark style="color:black;">Become an Ambassador</mark></summary>
|
||||
|
||||
As an ambassador, you are an advocate for the protocol, promoting its vision and mission. By sharing your knowledge and enthusiasm, you can educate others about the benefits of Ocean Protocol, inspiring them to join the ecosystem. As part of a global community of like-minded individuals, you gain access to exclusive resources, networking opportunities, and collaborations that further enhance your expertise in the data economy. Of course, the Ocean Protocol Ambassador Program rewards contributors with weekly bounties and discretionary grants for growing the Ocean Protocol communtiy worldwide.
|
||||
|
||||
Follow the steps below to become an ambassador:
|
||||
|
||||
To become a member of the Ambassador Program, follow these steps:
|
||||
1. Join Ocean Protocol's [Discord](https://discord.com/invite/TnXjkR5) server
|
||||
2. Join the Discord channel called #treasure-hunter.
|
||||
3. Access the application form: "[Apply](https://discord.com/channels/612953348487905282/1133478278531911790) to use this channel."
|
||||
4. Answer the questions in the application form.
|
||||
5. Once you've completed the application process, you can start earning experience points (XP) by actively engaging in discussions on various topics related to the Ocean Protocol.
|
||||
</details>
|
||||
|
||||
|
||||
----
|
||||
|
||||
_Next: [OCEAN: The Ocean token](ocean-token.md)_
|
||||
|
||||
_Back: [What is Ocean?](what-is-ocean.md)_
|
||||
@ -1,155 +0,0 @@
|
||||
---
|
||||
description: What is Ocean Protocol?
|
||||
---
|
||||
|
||||
# Explore
|
||||
|
||||
Ocean Protocol is a **decentralized data exchange protocol** that aims to unlock the value of data and enable secure and privacy-preserving on-chain data sharing and monetization ⛓️ It provides a framework for building data-centric applications that facilitate the exchange of data assets while ensuring data privacy, security, and compliance.
|
||||
|
||||
Ocean Protocol is used for a variety of purposes, including:
|
||||
|
||||
1. **Data Sharing**: Ocean Protocol allows individuals and organizations to share data securely and privately, enabling data owners to monetize their data assets while maintaining control over their data.
|
||||
2. **Data Monetization**: Data owners can monetize their data by offering it for sale or by providing data services through compute-to-data (C2D) capabilities. Data consumers can access and utilize data assets.
|
||||
3. **Decentralized Data Marketplaces**: Ocean Protocol facilitates the creation of decentralized data marketplaces where data providers can list their data assets and data consumers can discover and access them. These marketplaces operate on a peer-to-peer basis, eliminating the need for intermediaries and providing more efficient and transparent data transactions.
|
||||
4. **AI Development**: Ocean Protocol supports the development of AI models by providing access to diverse and high-quality datasets. Data scientists and AI developers can leverage these datasets to train and improve their models, leading to more accurate and robust AI systems.
|
||||
5. **Access control:** Ocean Protocol incorporates token-gating mechanisms that grant or restrict access to specific data assets based on predefined criteria, ensuring controlled and regulated data sharing within the ecosystem.
|
||||
|
||||
By leveraging **blockchain technology** and **smart contracts**, Ocean Protocol offers **open-source tools** to securely publish [NFTs](../developers/contracts/data-nfts.md) of your data and algorithms to seamlessly collaborate, trade, and innovate with others.
|
||||
|
||||
<figure><img src="../.gitbook/assets/general/explore_ocean.png" alt=""><figcaption><p>A vast ocean of data awaits you...</p></figcaption></figure>
|
||||
|
||||
Get a glimpse into some of the things you can do with Ocean Protocol. The opportunities with the protocol to leverage an "Ocean of data" are great and ever-evolving. Together, we'll dive deeper and uncover even more ways to harness the power of decentralized data.
|
||||
|
||||
<details>
|
||||
|
||||
<summary><mark style="color:purple;">Build Your dApp</mark><br><br><strong>Building a</strong> <a href="https://oceanprotocol.com/templates"><strong>dApp</strong></a> <strong>using Ocean Protocol can be a great way to bring next generation data sharing tools to your users. By utilizing Ocean's technology stack, you will leverage Web3 technological advantages that distinguish your application from others and can tap into a robust network of Ocean core data engineers/AI scientists supporting dApp developers.</strong></summary>
|
||||
|
||||
When building a dApp on top of Ocean Protocol, you gain access to a wide range of features and functionalities:
|
||||
|
||||
1. **Data access and discovery**: Utilize Ocean's data marketplace infrastructure to access diverse and valuable data sets. Leverage the data discovery mechanisms to help users find relevant data assets for their applications.
|
||||
2. **Data interoperability**: Seamlessly integrate and interact with various data sources using Ocean's standardized data representation formats. Ensure compatibility and easy data integration within your dApp.
|
||||
3. **Data privacy and security**: Leverage the cryptographic capabilities of Ocean Protocol to ensure privacy and security of sensitive data. Implement access controls, encryption, and secure data-sharing mechanisms within your dApp.
|
||||
4. **Provenance and transparency**: Leverage the transparency and immutability of the blockchain to establish data provenance. Build trust among users by providing an auditable record of data sources, usage, and transactions.
|
||||
5. **Tokenized incentives**: Utilize datatokens (ERC20) within your dApp to incentivize data providers and consumers. Design token economies that align with the specific requirements of your application, encouraging participation and value creation.
|
||||
6. **Community participation**: Leverage the community-driven nature of Ocean Protocol to foster collaboration, feedback, and innovation. Engage with the Ocean community to share ideas, contribute to the ecosystem, and gather insights to enhance your dApp.
|
||||
|
||||
These are a few examples of what can be built on top of Ocean.
|
||||
|
||||
1. [Ocean Waves](https://waves.oceanprotocol.com/) - Decentralized music [marketplace](https://github.com/oceanprotocol/waves)
|
||||
2. [Ocean Market](https://market.oceanprotocol.com) - Decentralized data [marketplace](https://github.com/oceanprotocol/market)
|
||||
3. [Autobot](https://autobotocean.com/) - Tokengated [data farming](https://df.oceandao.org/) intelligence app
|
||||
4. [Ocean token-gating](https://tokengate.oceanprotocol.com/) - Tokengated [content](https://github.com/oceanprotocol/token-gating-template)
|
||||
5. [Acentrik Market](https://market.acentrik.io/) - Enterprise decentralized data marketplace
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary><mark style="color:orange;">Build Your Data Marketplace</mark><br><br>With Ocean Protocol, you have the flexibility to create and launch your own data marketplace tailored to your specific requirements. Utilize the protocol's infrastructure and tools to establish a platform where data providers and consumers can connect and transact.</summary>
|
||||
|
||||
You can choose from two options:
|
||||
|
||||
1. **Fork the** [**Ocean Marketplace**](https://github.com/oceanprotocol/market) **and customize it**: You have the ability to fork the existing [Ocean Marketplace](https://github.com/oceanprotocol/market) codebase and customize it according to your needs. This allows you to leverage the foundational infrastructure and functionality already built by Ocean Protocol while tailoring the user interface, features, and branding to align with your marketplace vision. Follow this [tutorial](../developers/build-a-marketplace/) to learn how to do it.
|
||||
2. **Build your marketplace with Ocean components**: Alternatively, you can build your data marketplace from scratch using Ocean Protocol's modular components. Ocean provides a comprehensive set of building blocks, such as the [**Aquarius**](https://github.com/oceanprotocol/aquarius), [**Provider**](https://github.com/oceanprotocol/provider), Ocean [contracts](https://github.com/oceanprotocol/contracts), and Ocean libraries ([**ocean.js**](https://github.com/oceanprotocol/ocean.js) & [**ocean.py**](https://github.com/oceanprotocol/ocean.py)), which you can integrate into your own marketplace development. This empowers you to create a unique and customized data marketplace experience while leveraging the underlying capabilities and standards provided by Ocean Protocol.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary><mark style="color:blue;"><strong>Tokengate Your dApp or Content</strong></mark><br><br>Are you interested in token gating your dApp or content using an Ocean data NFT? We offer you all the code and support that you need to make this happen.</summary>
|
||||
|
||||
Feel free to fork the [Ocean token-gating template](https://github.com/oceanprotocol/token-gating-template) code and customize it to start building your dApp from scratch. If you already have an existing dApp of yours, then you can also modify it simply to use an Ocean data NFT.
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary><mark style="color:green;">Buy or Sell Data</mark><br><br>Users have the possibility to publish, purchase, and sell data within the Ocean ecosystem. Data is tokenized in the form of interoperable <a href="https://github.com/ethereum/EIPs/blob/master/EIPS/eip-721.md">ERC721</a> data NFTs and <a href="https://github.com/ethereum/EIPs/blob/7f4f0377730f5fc266824084188cc17cf246932e/EIPS/eip-20.md">ERC20</a> datatokens. The platform acts as a decentralized exchange (DEX) specifically designed for data transactions. Every action, including publishing, purchasing, and consuming data, is securely recorded on the blockchain, creating a tamper-proof audit trail.</summary>
|
||||
|
||||
For data scientists and AI practitioners, Ocean presents opportunities such as increased access to a broader range of data, including private data, crypto-secured provenance for data and AI training, and potential income streams from selling and curating data.
|
||||
|
||||
To showcase these capabilities, Ocean developed a demonstrator marketplace known as the [Ocean Market](https://market.oceanprotocol.com/).
|
||||
|
||||
The following guides will help you get started with buying and selling data:
|
||||
|
||||
* [Publish an NFT](../user-guides/publish-data-nfts.md)
|
||||
* [Download an NFT](../user-guides/buy-data-nfts.md)
|
||||
* [Host Assets](../user-guides/asset-hosting/README.md)
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary><mark style="color:blue;">Manage datatokens and data NFTs for use in DeFi</mark><br><br>Ocean makes it easy to publish data services (deploy ERC721 data NFTs and ERC20 datatokens), and to consume data services (spend datatokens). Crypto wallets, exchanges, and DAOs become data wallets, exchanges, and DAOs.</summary>
|
||||
|
||||
Use Ocean [JavaScript](../developers/ocean.js/README.md) or [Python](../data-scientists/ocean.py/README.md) drivers to manage data NFTs and datatokens:
|
||||
|
||||
Ocean-based apps make data assets on-ramps and off-ramps easy for end users. Ocean smart contracts and libraries make this easy for developers. The data itself does not need to be on-chain, just the access control.
|
||||
|
||||
Data NFTs are ERC721 tokens representing the unique asset and datatokens are ERC20 tokens to access data services. Each data service gets its own data NFT and one or more type of datatokens.
|
||||
|
||||
To access the dataset, you send 1.0 datatokens to the data provider (running Ocean Provider). To give access to someone else, send them 1.0 datatokens. That's it.
|
||||
|
||||
Since datatokens are ERC20, and live on Ethereum mainnet, there's a whole ecosystem to leverage.
|
||||
|
||||
* _Publish and access data services:_ downloadable files or compute-to-data. Use Ocean to deploy a new [ERC721](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-721.md) and [ERC20](https://github.com/ethereum/EIPs/blob/7f4f0377730f5fc266824084188cc17cf246932e/EIPS/eip-20.md) datatoken contract for each data service, then mint datatokens.
|
||||
* _Transfer datatokens_ to another owner (or approve & transferFrom).
|
||||
* _And more._ Use ERC20 support in [web3.js](https://web3js.readthedocs.io/), [web3.py](https://web3py.readthedocs.io/en/stable/examples.html#working-with-an-erc20-token-contract) and Solidity to connect datatokens with crypto wallets and other DeFi services.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary><a href="https://medium.com/p/477b3decad51#7922"><mark style="color:orange;">Run Your Own Provider</mark></a><br><br>You have the option to generate revenue by running your own <a href="../developers/provider/">provider</a>. It has come to our attention that many of you have not pursued this opportunity, primarily due to the lack of compelling incentives.</summary>
|
||||
|
||||
If you're not familiar with it, the Ocean [Provider](../developers/provider/README.md) serves as the proxy service responsible for encrypting/decrypting data and streaming it to the consumer. It also verifies user access privileges for specific data assets or services. It plays a vital role in the Ocean architecture.
|
||||
|
||||
Fees are now paid to the individual or organization running the provider when a user downloads a data asset. The download fees are set based on the cost per MB, and there is also a provider fee for compute jobs, which is priced per minute.
|
||||
|
||||
Both the download and compute fees can be set to any absolute amount, and you have the flexibility to choose the token in which you want to receive these fees. They do not have to be in the same currency used in the marketplace. For instance, the provider fee could be a fixed rate of 5 USDT per 1000 MB of data downloaded, and this fee will remain fixed in USDT even if the marketplace uses a different currency.
|
||||
|
||||
Furthermore, provider fees are not restricted to data consumption; they can also be utilized to charge for compute resources. For example, a provider can charge a fixed fee of 15 DAI to reserve compute resources for one hour. This presents an advantage for both the user and the provider host. Users can now reserve the appropriate amount of computing resources according to their requirements. For provider hosts, this creates an additional income opportunity.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary><mark style="color:purple;">Earn Rewards</mark><br><br>The <a href="../data-farming/README.md">Data Farming</a> initiative is a key feature of Ocean Protocol that empowers participants to earn <a href="../data-farming/">rewards</a> while contributing to a decentralized data economy. By staking OCEAN and actively participating in data markets, users play a vital role in enhancing the availability and accessibility of valuable data assets</summary>
|
||||
|
||||
Through the Data Farming initiative, you are incentivized to lock OCEAN for [veOCEAN](../data-farming/README.md). By staking your tokens, you not only support the growth and sustainability of the ecosystem but also earn a share of the generated incentives💰. The Data Farming initiative offers participants a unique opportunity to earn [rewards](../data-farming/README.md) while making a meaningful impact in the data marketplace.
|
||||
|
||||
Participating in the Data Farming initiative demonstrates a commitment to the principles of **fairness**, **transparency**, and **collaboration** that underpin Ocean Protocol. It allows you to actively engage with the ecosystem, promoting innovation, and driving the evolution of the decentralized data economy.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary><mark style="color:red;">Data Challenges</mark><br><br>Ocean <a href="https://oceanprotocol.com/challenges">Data Challenges</a> offer you a unique opportunity to showcase your skills and creativity in the world of data. These organized events and competitions encourage <a href="../data-scientists/">data scientists</a>, researchers, and developers like yourself to explore and innovate using Ocean Protocol.</summary>
|
||||
|
||||
By participating in Ocean Data Challenges, you can tackle real-world problems, leverage data assets, and utilize the technologies within the Ocean ecosystem. Not only do you have the chance to compete for recognition and prizes, but you also contribute to driving innovation, fostering collaboration, and making a positive impact in the data space.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary><mark style="color:blue;">Become an Ambassador</mark><br><br>Becoming an <a href="https://oceanambassadors.community/">Ocean Ambassador</a> presents a unique opportunity to actively contribute to the growth and adoption of Ocean Protocol while being at the forefront of the decentralized data revolution.</summary>
|
||||
|
||||
As an Ocean Ambassador, you become an advocate for the protocol, promoting its vision of democratizing data and empowering individuals. By sharing your knowledge and enthusiasm, you can educate others about the benefits and potential of Ocean Protocol, inspiring them to join the ecosystem. As part of a global community of like-minded individuals, you gain access to exclusive resources, networking opportunities, and collaborations that further enhance your expertise in the data economy. As an Ambassador, you play a vital role in shaping the future of data by driving awareness, fostering innovation, and helping to build a more open and equitable data ecosystem. Of course, the Ocean Protocol Ambassador Program rewards contributors with weekly bounties and discretionary grants for growing the Ocean Protocol communtiy worldwide.
|
||||
|
||||
Follow the steps below to become an ambassador:
|
||||
|
||||
To become a member of the Ambassador Program, follow these steps:
|
||||
1. Join Ocean Protocol's [Discord](https://discord.com/invite/TnXjkR5) server
|
||||
2. Join the Discord channel called #treasure-hunter.
|
||||
3. Access the application form: "[Apply](https://discord.com/channels/612953348487905282/1133478278531911790) to use this channel."
|
||||
4. Answer the questions in the application form.
|
||||
5. Once you've completed the application process, you can start earning experience points (XP) by actively engaging in discussions on various topics related to the Ocean Protocol.
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary><mark style="color:green;">Contribute to Ocean Code Development</mark><br><br>Make a positive impact in the Web3 data economy by contributing to <a href="https://github.com/oceanprotocol">Ocean's open source code</a> on Github! From feature requests to pull requests, contributions of all kinds are appreciated.</summary>
|
||||
|
||||
To begin, [visit the Ocean Github page](https://github.com/oceanprotocol) where you can see the repos and contributors. If you're going to contribute code to a repo, then we ask that you fork the code first, make your changes, and then create a pull request for us to review. If you are reporting an issue, then please first search the existing issues to see if it is documented yet. If not, then please open a new issue by describe your problem as best as possible and include screenshots.
|
||||
We also welcome you to join the [Discord developer community](https://discord.gg/TnXjkR5) where you can get rapid, practical advice on using Ocean tech but also get to know Ocean core team more personally!
|
||||
</details>
|
||||
|
||||
This is just the beginning of what Ocean Protocol has to offer. Join us as we explore, innovate, and push the boundaries of what's possible with decentralized data. Together, we can shape a future where data is accessible, secure and empowers individuals and organizations alike. Let's dive in and discover the endless possibilities of Ocean Protocol :ocean:
|
||||
@ -9,7 +9,7 @@ Have some questions about Ocean Protocol?
|
||||
|
||||
Hopefully, you'll find the answers here! If not then please don't hesitate to reach out to us on [discord](https://discord.gg/TnXjkR5) - there are no stupid questions!
|
||||
|
||||
### General
|
||||
## General
|
||||
|
||||
<details>
|
||||
<summary>How is Ocean Protocol related to AI?</summary>
|
||||
@ -61,7 +61,7 @@ To be fully decentralized means no single point of control, at any level of the
|
||||
</details>
|
||||
|
||||
|
||||
### About OCEAN
|
||||
## About OCEAN
|
||||
|
||||
<details>
|
||||
<summary>How is OCEAN used? How does it capture value?</summary>
|
||||
@ -123,7 +123,7 @@ For each consume transaction, the Ocean community gets a small fee. This happens
|
||||
</details>
|
||||
|
||||
|
||||
### Grants, challenges, and ecosystem
|
||||
## Grants, challenges, and ecosystem
|
||||
|
||||
<details>
|
||||
<summary>Is Acentrik from Mercedes Benz built on top of Ocean?</summary>
|
||||
@ -153,7 +153,7 @@ There are a wide host of technical, business, and cultural barriers to overcome
|
||||
</details>
|
||||
|
||||
|
||||
### Data security
|
||||
## Data security
|
||||
|
||||
|
||||
<details>
|
||||
@ -172,7 +172,7 @@ This issue is similar to what any digital distribution platform faces. For insta
|
||||
</details>
|
||||
|
||||
|
||||
### Data marketplaces & Ocean Market
|
||||
## Data marketplaces & Ocean Market
|
||||
|
||||
<details>
|
||||
<summary>What is a decentralized data marketplace?</summary>
|
||||
@ -201,7 +201,7 @@ Ocean Market is a showcase for the practical application of Ocean, showing other
|
||||
Fees are generated Ocean Market from Ocean Market that head to Ocean community. The earlier Q&A on revenue has details.
|
||||
</details>
|
||||
|
||||
### Contacting Ocean core team
|
||||
## Contacting Ocean core team
|
||||
|
||||
<details>
|
||||
<summary>Who is the right person to talk to regarding a marketing proposal or collaboration?</summary>
|
||||
@ -209,3 +209,11 @@ Fees are generated Ocean Market from Ocean Market that head to Ocean community.
|
||||
For collaborations, please fill in this [form](https://docs.google.com/forms/d/e/1FAIpQLSdBz7cblsz5yuOKMVoPVfK0Pp1Xuqjwner1kCkRibIIbYMe-w/viewform).
|
||||
One member of our team will reach out to you 🤝
|
||||
</details>
|
||||
|
||||
|
||||
----
|
||||
|
||||
_Next: [Glossary](glossary.md)_
|
||||
|
||||
_Back: [Bridges](networks/bridges.md)_
|
||||
|
||||
|
||||
@ -1,17 +1,15 @@
|
||||
---
|
||||
description: >-
|
||||
A comprehensive list of key terms, concepts, and acronyms used in the Ocean
|
||||
Protocol ecosystem
|
||||
Key terms, concepts, and acronyms used in Ocean
|
||||
---
|
||||
|
||||
# Glossary
|
||||
|
||||
### Ocean Protocol Concepts
|
||||
## Ocean Protocol Concepts
|
||||
|
||||
<details>
|
||||
|
||||
<summary>Ocean Protocol</summary>
|
||||
|
||||
Ocean Protocol is a decentralized data exchange protocol that enables individuals and organizations to share, sell, and consume data in a secure, transparent, and privacy-preserving manner. The protocol is designed to address the current challenges in data sharing, such as data silos, lack of interoperability, and data privacy concerns. Ocean Protocol uses blockchain technology, smart contracts, and cryptographic techniques to create a network where data providers can offer their data assets for sale, data consumers can purchase and access the data, and developers can build data-driven applications and services on top of the protocol.
|
||||
|
||||
</details>
|
||||
@ -28,7 +26,7 @@ The Ocean Protocol's token (OCEAN) is a utility token used in the Ocean Protocol
|
||||
|
||||
<summary>Data Consume Volume (DCV)</summary>
|
||||
|
||||
The data consume value (DCV) is a key metric that refers to the amount of $ spent to buy data assets where the data assets are subsequently consumed.
|
||||
The data consume value (DCV) is a key metric that refers to the amount of $ spent over a time period, to buy data assets where the data assets are subsequently consumed.
|
||||
|
||||
</details>
|
||||
|
||||
@ -36,49 +34,7 @@ The data consume value (DCV) is a key metric that refers to the amount of $ spen
|
||||
|
||||
<summary>Transaction Volume (TV)</summary>
|
||||
|
||||
The transaction value is a key metric that refers to the value of transactions within the ecosystem.
|
||||
|
||||
Transaction volume(TV) is often used interchangeably with data consume volume (DCV). DCV is a more refined metric that excludes activities like wash trading. DCV measures the actual consumption or processing of data within the protocol, which is a more accurate measure of the value generated by the ecosystem.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary><strong>Base IP</strong></summary>
|
||||
|
||||
**Base IP** means the artifact being copyrighted. Represented by the {ERC721 address, tokenId} from the publish transactions.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary><strong>Base IP holder</strong></summary>
|
||||
|
||||
**Base IP holder** means the holder of the Base IP. Represented as the actor that did the initial "publish" action.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary><strong>Sub-licensee</strong></summary>
|
||||
|
||||
**Sub-licensee** is the holder of the sub-license. Represented as the entity that controls address ERC721.\_owners\[tokenId=x].
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary><strong>To Publish</strong></summary>
|
||||
|
||||
Claim copyright or exclusive base license.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary><strong>To Sub-license</strong></summary>
|
||||
|
||||
Transfer one (of many) sub-licenses to new licensee: ERC20.transfer(to=licensee, value=1.0).
|
||||
The transaction value is a key metric that refers to the number of blockchain transactions done over a time period.
|
||||
|
||||
</details>
|
||||
|
||||
@ -151,50 +107,50 @@ When a user allocates veOCEAN to Ocean Market projects, then weekly OCEAN reward
|
||||
|
||||
</details>
|
||||
|
||||
## Intellectual Property (IP) Concepts
|
||||
|
||||
<details>
|
||||
|
||||
<summary>Challenge DF</summary>
|
||||
<summary><strong>Base IP</strong></summary>
|
||||
|
||||
When users submit accurate predictions for the price of Ethereum to the [Challenge DF program](https://df.oceandao.org/challenge-df), they have a chance to win OCEAN rewards by being in the top 3 submissions based on predicted value accuracy.
|
||||
|
||||
These rewards are classified as [Challenge DF](../data-farming/README.md) rewards since they require active participation in the challenge. Rewards can be claimed every Thursday on the [Rewards page](https://df.oceandao.org/rewards).
|
||||
**Base IP** means the artifact being copyrighted. Represented by the {ERC721 address, tokenId} from the publish transactions.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary>H2O</summary>
|
||||
<summary><strong>Base IP holder</strong></summary>
|
||||
|
||||
[H2O](https://www.h2odata.xyz/) is a decentralized protocol that introduced the first non-pegged stable asset, $H2O. Initially, it is backed by OCEAN but there are plans to be backed by other data tokens.
|
||||
|
||||
The H2O non-pegged stable asset is a friendly fork of RAI. Whereas RAI uses ether (ETH) as its asset for collateral, H2O uses OCEAN. The price of H2O is managed by an algorithm that rebalances to bring the redemption price close to the market price and participants are incentivized to aid in this process. Traditional stable assets are pegged to a price such as 1 USD. In contrast, RAI (and soon H2O) are free-floating but typically settle around a price; for RAI this has been \~$3.
|
||||
**Base IP holder** means the holder of the Base IP. Represented as the actor that did the initial "publish" action.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary>$POSEIDON</summary>
|
||||
<summary><strong>Sub-licensee</strong></summary>
|
||||
|
||||
The [POSEIDON token](https://docs.h2odata.xyz/protocol-overview/poseidon-mechanics) is the governance token of the H2O protocol. With the following function inside the protocol:
|
||||
|
||||
* Ungovernance: once governance minimization is finalized, POSEIDON holders will be able to remove control from any remaining components in H2O or, if needed, continue to manage components that may be challenging to ungovern (such as oracles or any other component interacting with other protocols).
|
||||
**Sub-licensee** is the holder of the sub-license. Represented as the entity that controls address ERC721.\_owners\[tokenId=x].
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary>$psdnOcean</summary>
|
||||
<summary><strong>To Publish</strong></summary>
|
||||
|
||||
[psdnOCEAN](https://docs.h2odata.xyz/protocol-overview/psdnocean-veocean-liquid-staking) is the liquid staking wrapper for veOCEAN.
|
||||
Claim copyright or exclusive base license.
|
||||
|
||||
* Convert OCEAN to psdnOCEAN with a 1:1 ratio.
|
||||
* Gain access to a liquid asset and receive a share of the revenue of veOCEAN.
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary><strong>To Sub-license</strong></summary>
|
||||
|
||||
Transfer one (of many) sub-licenses to new licensee: ERC20.transfer(to=licensee, value=1.0).
|
||||
|
||||
</details>
|
||||
|
||||
|
||||
|
||||
### Web3 Fundamentals
|
||||
## Web3 Fundamentals
|
||||
|
||||
<details>
|
||||
|
||||
@ -362,9 +318,9 @@ A term used in the cryptocurrency and blockchain space to encourage developers a
|
||||
|
||||
</details>
|
||||
|
||||
###
|
||||
##
|
||||
|
||||
### Decentralized Finance (DeFi) fundamentals
|
||||
## Decentralized Finance (DeFi) fundamentals
|
||||
|
||||
<details>
|
||||
|
||||
@ -446,7 +402,7 @@ A strategy in which investors provide liquidity to a DeFi protocol in exchange f
|
||||
|
||||
</details>
|
||||
|
||||
### Data Science Terminology
|
||||
## Data Science Terminology
|
||||
|
||||
<details>
|
||||
|
||||
@ -465,4 +421,14 @@ Machine learning is a subfield of artificial intelligence (AI) that involves tea
|
||||
</details>
|
||||
|
||||
|
||||
----
|
||||
|
||||
|
||||
Congrats! You've completed this quick introduction to Ocean.
|
||||
|
||||
_Next: Jump to [Docs main](../README.md) and click on your interest._
|
||||
|
||||
_Back: [FAQ](faq.md)_
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,119 +1,236 @@
|
||||
---
|
||||
title: Supported Networks
|
||||
title:
|
||||
description: All the public networks the Ocean Protocol contracts are deployed to.
|
||||
---
|
||||
|
||||
# Networks
|
||||
|
||||
Ocean Protocol contracts are deployed on multiple public networks. You can always find the most up-to-date deployment addresses for all individual contracts in the [address.json](https://github.com/oceanprotocol/contracts/blob/v4main/addresses/address.json).
|
||||
Ocean Protocol's smart contracts and [OCEAN](../ocean-token.md) are deployed on multiple public networks: several production chains, and several testnets too.
|
||||
|
||||
In each network, whether it's the Ethereum mainnet, a testnet, or the Polygon/Matic network, you'll need ETH or Matic to pay for gas and OCEAN for certain actions on the Ocean Protocol network. The Ethereum mainnet and the Polygon network are both live networks and the tokens on these networks have real value. However, the tokens on the test networks are not of real value and are only used for testing purposes. You can obtain testnet ETH and OCEAN from faucets, which are services that provide small amounts of tokens for free.
|
||||
The file [`address.json`](https://github.com/oceanprotocol/contracts/blob/v4main/addresses/address.json) holds up-to-date deployment addresses for all Ocean contracts.
|
||||
|
||||
### Ethereum Mainnet
|
||||
On tokens:
|
||||
- You need the network's native token to pay for gas to make transactions: ETH for Ethereum mainnet, MATIC for Polygon, etc. You typically get these from exchanges.
|
||||
- You may get OCEAN from an exchange, and bridge it as needed.
|
||||
- For testnets, you'll need "fake" native tokens to pay for gas, and "fake" OCEAN. Typically, you get these from faucets.
|
||||
- Below, we give token-related instructions, for each network.
|
||||
|
||||
The Ethereum mainnet is a production network, which means that it is a live and operational network that handles real transactions and has actual economic value. To connect to the Ethereum mainnet using a wallet such as MetaMask, you can click on the network name dropdown and select Ethereum mainnet from the list of available networks.
|
||||
## Networks Summary
|
||||
|
||||
<table data-header-hidden><thead><tr><th width="100">Gas Token</th><th>ETH(Native token)</th></tr></thead><tbody><tr><td>OCEAN</td><td><a href="https://etherscan.io/token/0x967da4048cD07aB37855c090aAF366e4ce1b9F48">0x967da4048cD07aB37855c090aAF366e4ce1b9F48</a></td></tr><tr><td>Explorer</td><td><a href="https://etherscan.io">https://etherscan.io</a></td></tr></tbody></table>
|
||||
Here are the networks that Ocean is deployed to.
|
||||
|
||||
### Polygon Mainnet
|
||||
**Production Networks:**
|
||||
- Ethereum mainnet
|
||||
- Polygon mainnet
|
||||
- Oasis Sapphire mainnet
|
||||
- BNB Smart Chain
|
||||
- Energy Web Chain
|
||||
- Optimism (OP) Mainnet
|
||||
- Moonriver
|
||||
|
||||
Ocean Protocol is also deployed to Polygon Mainnet, which is another production network. The native token of Polygon Mainnet is MATIC. If you cannot find Polygon Mainnet as a predefined network in your wallet, you can manually connect to it by following Polygon's [guide](https://wiki.polygon.technology/docs/develop/metamask/config-polygon-on-metamask/#add-the-polygon-network-manually), which provides step-by-step instructions for connecting to Polygon Mainnet.
|
||||
**Test Networks:**
|
||||
- Görli
|
||||
- Sepolia
|
||||
- Mumbai
|
||||
- Oasis Sapphire testnet
|
||||
- Optimism (OP) Sepolia
|
||||
|
||||
<table data-header-hidden><thead><tr><th width="100">Gas Token</th><th>Matic(Native token)</th></tr></thead><tbody><tr><td>OCEAN</td><td><a href="https://polygonscan.com/token/0x282d8efce846a88b159800bd4130ad77443fa1a1">0x282d8efCe846A88B159800bd4130ad77443Fa1A1</a></td></tr><tr><td>Explorer</td><td><a href="https://polygonscan.com">https://polygonscan.com</a></td></tr></tbody></table>
|
||||
The rest of this doc gives details for each network. You can skip it until you need the reference information.
|
||||
|
||||
**Bridge**
|
||||
## Production Networks
|
||||
|
||||
Check out the Polygon Bridge [guide](bridges.md) to learn how you can deposit, withdraw and send tokens.
|
||||
### Production: Ethereum Mainnet
|
||||
|
||||
### Oasis Sapphire Mainnet
|
||||
<table data-header-hidden>
|
||||
<tbody>
|
||||
<tr><td>Native token</td><td>ETH</td></tr>
|
||||
<tr><td>OCEAN address</td><td><a href="https://etherscan.io/token/0x967da4048cD07aB37855c090aAF366e4ce1b9F48">0x967da4048cD07aB37855c090aAF366e4ce1b9F48</a></td></tr>
|
||||
<tr><td>Explorer</td><td><a href="https://etherscan.io">https://etherscan.io</a></td></tr>
|
||||
</tbody>
|
||||
|
||||
Ocean Protocol is also deployed to Oasis Sapphire Mainnet, which is a production network that Ocean Protocol uses for [Predictoor](https://predictoor.ai). Ocean Protocol does do not currently support ocean.js, ocean.py, or Ocean Market on Oasis Sapphire. The native token of Oasis Sapphire is ROSE. If you cannot find Oasis Sapphire Mainnet as a predefined network in your wallet, you can manually connect to it by entering the following information during the import process: Network Name: `Oasis Sapphire`, RPC URL: `https://sapphire.oasis.io`, Chain ID: `23294`, Token: `ROSE`.
|
||||
</table>
|
||||
|
||||
<table data-header-hidden><thead><tr><th width="100">Gas Token</th><th>ROSE(Native token)</th></tr></thead><tbody><tr><td>OCEAN</td><td><a href="https://explorer.oasis.io/mainnet/sapphire/token/0x39d22B78A7651A76Ffbde2aaAB5FD92666Aca520">0x39d22B78A7651A76Ffbde2aaAB5FD92666Aca520</a></td></tr><tr><td>Explorer</td><td><a href="https://explorer.oasis.io/mainnet/sapphire/">https://explorer.oasis.io/mainnet/sapphire/</a></td></tr></tbody></table>
|
||||
|
||||
**Bridge**
|
||||
|
||||
Check out our Celer Bridge [guide](https://github.com/oceanprotocol/pdr-backend/blob/main/READMEs/get-ocean-on-sapphire.md#2-transfer-ocean-to-sapphire-mainnet-via-celer) to learn how you can bridge your OCEAN tokens from Ethereum Mainnet to Oasis Sapphire Mainnet.
|
||||
|
||||
### Oasis Sapphire Testnet
|
||||
|
||||
Ocean Protocol is also deployed to Oasis Sapphire Testnet, which is a test network that Ocean Protocol uses for [Predictoor](https://predictoor.ai). Ocean Protocol does do not currently support ocean.js, ocean.py, or Ocean Market on Oasis Sapphire. The native token of Oasis Sapphire is ROSE. If you cannot find Oasis Sapphire Testnet as a predefined network in your wallet, you can manually connect to it by entering the following information during the import process: Network Name: `Oasis Sapphire Testnet`, RPC URL: `https://testnet.sapphire.oasis.dev`, Chain ID: `23295`, Token: `ROSE`.
|
||||
|
||||
<table data-header-hidden><thead><tr><th width="100">Gas Token</th><th>ROSE(Native token)</th></tr></thead><tbody><tr><td>OCEAN</td><td><a href="https://explorer.oasis.io/testnet/sapphire/address/0x973e69303259B0c2543a38665122b773D28405fB">0x973e69303259B0c2543a38665122b773D28405fB</a></td></tr><tr><td>Explorer</td><td><a href="https://explorer.oasis.io/testnet/sapphire/">https://explorer.oasis.io/testnet/sapphire/</a></td></tr></tbody></table>
|
||||
|
||||
**Get (fake) OCEAN on Sapphire Testnet**
|
||||
|
||||
Check out our [guide](https://github.com/oceanprotocol/pdr-backend/blob/main/READMEs/testnet-faucet.md#get-fake-ocean-on-sapphire-testnet) for how to get fake OCEAN tokens on Sapphire Testnet.
|
||||
|
||||
Check out our [guide](https://github.com/oceanprotocol/pdr-backend/blob/main/READMEs/testnet-faucet.md#get-fake-rose-on-sapphire-testnet) for how to get fake ROSE tokens on Oasis Sapphire Testnet.
|
||||
|
||||
### BNB Smart Chain
|
||||
|
||||
Ocean Protocol is also deployed to BNB Smart Chain, which is another production network. The native token of the BNB Smart Chain is BNB, which is the token of the Binance exchange. If BNB Smart Chain is not listed as a predefined network in your wallet, you can manually connect to it by following Binance's [guide](https://academy.binance.com/en/articles/connecting-metamask-to-binance-smart-chain), which provides detailed instructions on how to connect to BNB Smart Chain.
|
||||
|
||||
<table data-header-hidden><thead><tr><th width="100">Gas Token</th><th>BSC BNB(Native token)</th></tr></thead><tbody><tr><td>OCEAN</td><td><a href="https://bscscan.com/token/0xdce07662ca8ebc241316a15b611c89711414dd1a">0xdce07662ca8ebc241316a15b611c89711414dd1a</a></td></tr><tr><td>Explorer</td><td><a href="https://bscscan.com/">https://bscscan.com/</a></td></tr></tbody></table>
|
||||
|
||||
**Bridge**
|
||||
|
||||
Check out the BSC Bridge [guide](bridges.md#bnb-smart-chain-bridge) to learn how you can deposit, withdraw and send tokens.
|
||||
|
||||
### Energy Web Chain
|
||||
|
||||
Ocean Protocol is also deployed to [Energy Web Chain](https://energy-web-foundation.gitbook.io/energy-web/technology/trust-layer-energy-web-chain), which is another production network. The native token of the Energy Web Chain is EWT. If you cannot find Energy Web Chain as a predefined network in your wallet, you can manually connect to it by following this [guide](https://energy-web-foundation.gitbook.io/energy-web/how-tos-and-tutorials/connect-to-energy-web-chain-main-network-with-metamash).
|
||||
|
||||
<table data-header-hidden><thead><tr><th width="100">Gas Token</th><th>Energy Web Chain EWT(Native token)</th></tr></thead><tbody><tr><td>OCEAN</td><td><a href="https://explorer.energyweb.org/token/0x593122aae80a6fc3183b2ac0c4ab3336debee528">0x593122aae80a6fc3183b2ac0c4ab3336debee528</a></td></tr><tr><td>Explorer</td><td><a href="https://explorer.energyweb.org/">https://explorer.energyweb.org/</a></td></tr></tbody></table>
|
||||
|
||||
**Bridge**
|
||||
|
||||
To bridge assets between Energy Web Chain and Ethereum mainnet, you can use [this](https://bridge.carbonswap.exchange/) bridge.
|
||||
|
||||
### OP Mainnet(Optimism)
|
||||
|
||||
Ocean Protocol is also deployed to OP Mainnet (Optimism), which is another production network. The native token of Optimism is ETH, which needs to be bridged from Ethereum Mainnet. If you cannot find Optimism as a predefined network in your wallet, you can manually connect to it by following OP's [guide](https://community.optimism.io/docs/useful-tools/networks/#op-mainnet), which provides step-by-step instructions for connecting to OP Mainnet.
|
||||
|
||||
<table data-header-hidden><thead><tr><th width="100">Gas Token</th><th>ETH</th></tr></thead><tbody><tr><td>OCEAN</td><td><a href="https://optimistic.etherscan.io/address/0x2561aa2bB1d2Eb6629EDd7b0938d7679B8b49f9E">0x2561aa2bB1d2Eb6629EDd7b0938d7679B8b49f9E</a></td></tr><tr><td>Explorer</td><td><a href="https://optimistic.etherscan.io">https://optimistic.etherscan.io</a></td></tr></tbody></table>
|
||||
|
||||
**Bridge**
|
||||
|
||||
Check out the OP Bridge [guide](https://https://app.optimism.io/bridge/deposit) to deposit, withdraw and send tokens.
|
||||
|
||||
### Moonriver
|
||||
|
||||
Ocean Protocol is also deployed to [Moonriver](https://docs.moonbeam.network/builders/get-started/networks/moonriver/), which is another production network. The native token of Moonriver is MOVR. If Moonriver is not listed as a predefined network in your wallet, you can manually connect to it by following this [guide](https://docs.moonbeam.network/builders/get-started/networks/moonriver/#connect-metamask).
|
||||
|
||||
<table data-header-hidden><thead><tr><th width="100">Gas Token</th><th>Moonriver MOVR(Native token)</th></tr></thead><tbody><tr><td>OCEAN</td><td><a href="https://blockscout.moonriver.moonbeam.network/token/0x99C409E5f62E4bd2AC142f17caFb6810B8F0BAAE/token-transfers">0x99C409E5f62E4bd2AC142f17caFb6810B8F0BAAE</a></td></tr><tr><td>Explorer</td><td><a href="https://blockscout.moonriver.moonbeam.network">https://blockscout.moonriver.moonbeam.network</a></td></tr></tbody></table>
|
||||
|
||||
**Bridge**
|
||||
|
||||
To bridge assets between Moonriver and Ethereum mainnet, you can use [this](https://anyswap.exchange/#/bridge) bridge.
|
||||
|
||||
### Görli
|
||||
|
||||
Ocean Protocol is deployed on the Görli test network, which is used for testing and experimentation. Tokens on Görli do not hold real economic value, as it is a non-production network. To connect to Görli using a wallet like MetaMask, simply click on the network name dropdown and select _Goerli_ from the list of available networks.
|
||||
|
||||
<table data-header-hidden><thead><tr><th width="100">Gas Token</th><th>Görli ETH(Native token)</th></tr></thead><tbody><tr><td>Görli ETH</td><td><a href="https://goerlifaucet.com/">Faucet</a>. You may find others by <a href="https://www.google.com/search?q=goerli+ether+faucet%5C&oq=goerli+ether+faucet">searching</a>.</td></tr><tr><td>Görli OCEAN</td><td><a href="https://faucet.goerli.oceanprotocol.com">Faucet</a></td></tr><tr><td>OCEAN</td><td><a href="https://goerli.etherscan.io/address/0xcfdda22c9837ae76e0faa845354f33c62e03653a">0xCfDdA22C9837aE76E0faA845354f33C62E03653a</a></td></tr><tr><td>Explorer</td><td><a href="https://blockscout.moonriver.moonbeam.network">https://blockscout.moonriver.moonbeam.network</a></td></tr></tbody></table>
|
||||
|
||||
### Mumbai
|
||||
|
||||
Ocean Protocol is deployed on the Mumbai test network Matic / Polygon, which is designed for testing and experimentation purposes. Tokens in Mumbai do not hold any real economic value, as it is not a production network. To connect to Mumbai using a wallet like MetaMask, you can select "Görli" from the network dropdown list.
|
||||
|
||||
If Mumbai is not listed as a predefined network in your wallet, you can connect to it manually by following [Matic's guide](https://wiki.polygon.technology/docs/develop/metamask/config-polygon-on-metamask/).
|
||||
|
||||
<table data-header-hidden><thead><tr><th width="100"></th><th>Mumbai MATIC(Native token)</th></tr></thead><tbody><tr><td>Mumbai MATIC</td><td><a href="https://faucet.matic.network/">Faucet</a>. You may find others by <a href="https://www.google.com/search?q=mumbai+faucet">searching</a>.</td></tr><tr><td>Mumbai OCEAN</td><td><a href="https://faucet.mumbai.oceanprotocol.com/">Faucet</a></td></tr><tr><td>OCEAN</td><td><a href="https://mumbai.polygonscan.com/token/0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8">0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8</a></td></tr><tr><td>Explorer</td><td><a href="https://mumbai.polygonscan.com">https://mumbai.polygonscan.com</a></td></tr></tbody></table>
|
||||
|
||||
### Sepolia
|
||||
|
||||
Ocean Protocol is deployed on the Sepolia test network, which is designed for testing and experimentation purposes. Tokens in Sepolia do not hold any real economic value, as it is not a production network. To connect to Sepolia using a wallet like MetaMask, you can select "Sepolia" from the network dropdown list(enable "Show test networks").
|
||||
|
||||
<table data-header-hidden><thead><tr><th width="100">Gas Token</th><th>SepoliaETH (Native token)</th></tr></thead><tbody><tr><td>SepoliaETH</td><td><a href="https://sepoliafaucet.com/">Faucet</a></td></tr><tr><td>Sepolia OCEAN</td><td><a href="https://faucet.sepolia.oceanprotocol.com/">Faucet</a></td></tr><tr><td>OCEAN</td><td><a href="https://sepolia.etherscan.io/address/0x1B083D8584dd3e6Ff37d04a6e7e82b5F622f3985">0x1B083D8584dd3e6Ff37d04a6e7e82b5F622f3985</a></td></tr><tr><td>Explorer</td><td><a href="https://sepolia.etherscan.io/">https://sepolia.etherscan.io/</a></td></tr></tbody></table>
|
||||
**Wallet.** To connect to Ethereum mainnet with e.g. MetaMask, click on the network name dropdown and select "Ethereum mainnet" from the list.
|
||||
|
||||
|
||||
### OP Sepolia(Optimism)
|
||||
### Production: Polygon Mainnet
|
||||
|
||||
Ocean Protocol is deployed on the OP Sepolia test network, which is designed for testing and experimentation purposes. Tokens in Sepolia do not hold any real economic value, as it is not a production network. If OP Sepolia is not listed as a predefined network in your wallet, you can manually connect to it by following OP's [guide](https://community.optimism.io/docs/useful-tools/networks/#op-sepolia), which provides detailed instructions on how to connect to OP Seploia.
|
||||
<table data-header-hidden>
|
||||
<tbody>
|
||||
<tr><td>Native token</td><td>MATIC</td></tr>
|
||||
<tr><td>OCEAN address</td><td><a href="https://polygonscan.com/token/0x282d8efce846a88b159800bd4130ad77443fa1a1">0x282d8efCe846A88B159800bd4130ad77443Fa1A1</a></td></tr>
|
||||
<tr><td>Explorer</td><td><a href="https://polygonscan.com">https://polygonscan.com</a></td></tr>
|
||||
</tbody>
|
||||
|
||||
<table data-header-hidden><thead><tr><th width="100">Gas Token</th><th>Sepolia ETH</th></tr></thead><tbody><tr><td>OP Sepolia Faucet</td><td><a href="https://faucet.quicknode.com/optimism/sepolia">Faucet</a></td></tr><tr><td>OP Sepolia OCEAN</td><td><a href="https://faucet.op-sepolia.oceanprotocol.com/">Faucet</a></td></tr><tr><td>OCEAN</td><td><a href="https://sepolia-optimism.etherscan.io/address/0xf26c6c93f9f1d725e149d95f8e7b2334a406ad10">0xf26c6C93f9f1d725e149d95f8E7B2334a406aD10</a></td></tr><tr><td>Explorer</td><td><a href="https://sepolia-optimism.etherscan.io/">https://sepolia-optimism.etherscan.io</a></td></tr></tbody></table>
|
||||
</table>
|
||||
|
||||
**Bridge**
|
||||
**Wallet.** If you can't find Polygon Mainnet as a predefined network, follow [Polygon's guide](https://wiki.polygon.technology/docs/develop/metamask/config-polygon-on-metamask/#add-the-polygon-network-manually).
|
||||
|
||||
**Bridge.** Check out the Polygon Bridge [guide](bridges.md) to learn how you can deposit, withdraw and send tokens.
|
||||
|
||||
### Production: Oasis Sapphire Mainnet
|
||||
|
||||
[Ocean Predictoor](../predictoor/README.md) is deployed on Oasis Sapphire mainnet for its ability to keep EVM transactions private. This deployment does do not currently support ocean.js, ocean.py, or Ocean Market.
|
||||
|
||||
<table data-header-hidden>
|
||||
<tbody>
|
||||
<tr><td>Native token</td></td><td>ROSE</td></tr>
|
||||
<tr><td>OCEAN address</td><td><a href="https://explorer.oasis.io/mainnet/sapphire/token/0x39d22B78A7651A76Ffbde2aaAB5FD92666Aca520">0x39d22B78A7651A76Ffbde2aaAB5FD92666Aca520</a></td></tr>
|
||||
<tr><td>Explorer</td><td><a href="https://explorer.oasis.io/mainnet/sapphire/">https://explorer.oasis.io/mainnet/sapphire</a></td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
**Wallet.** If you cannot find Oasis Sapphire Mainnet as a predefined network, fyou can manually connect by entering the following during import: Network Name: `Oasis Sapphire`, RPC URL: `https://sapphire.oasis.io`, Chain ID: `23294`, Token: `ROSE`. For further info, see [Oasis tokens docs](https://docs.oasis.io/general/manage-tokens/).
|
||||
|
||||
**Bridge.** Use [Celer](https://cbridge.celer.network/1/23294/OCEAN) to bridge OCEAN from Ethereum mainnet to Oasis Sapphire mainnet.
|
||||
|
||||
### Production: BNB Smart Chain
|
||||
|
||||
<table data-header-hidden>
|
||||
<tbody>
|
||||
<tr><td>Native token</td></td><td>BSC BNB</td></tr>
|
||||
<tr><td>OCEAN address</td><td><a href="https://bscscan.com/token/0xdce07662ca8ebc241316a15b611c89711414dd1a">0xdce07662ca8ebc241316a15b611c89711414dd1a</a></td></tr>
|
||||
<tr><td>Explorer</td><td><a href="https://bscscan.com/">https://bscscan.com/</a></td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
This is one of the [Binance](https://binance.com)-spawned chains. BNB is the token of Binance.
|
||||
|
||||
**Wallet.** If BNB Smart Chain is not listed as a predefined network in your wallet, see [Binance's Guide](https://academy.binance.com/en/articles/connecting-metamask-to-binance-smart-chain) to manually connect.
|
||||
|
||||
**Bridge.** Our [BNB Smart Chain Bridge Guide](bridges.md#bnb-smart-chain-bridge) describes how to get OCEAN to BNB Smart Chain.
|
||||
|
||||
### Production: Energy Web Chain (EWC)
|
||||
|
||||
<table data-header-hidden>
|
||||
<tbody>
|
||||
<tr><td>Native token</td></td><td>Energy Web Chain EWT</td></tr>
|
||||
<tr><td>OCEAN address</td><td><a href="https://explorer.energyweb.org/token/0x593122aae80a6fc3183b2ac0c4ab3336debee528">0x593122aae80a6fc3183b2ac0c4ab3336debee528</a></td></tr>
|
||||
<tr><td>Explorer</td><td><a href="https://explorer.energyweb.org/">https://explorer.energyweb.org/</a></td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
This is the chain for [Energy Web Foundation](https://www.energyweb.org/).
|
||||
|
||||
**Wallet.** If you cannot find Energy Web Chain as a predefined network in your wallet, you can manually connect to it by following this [guide](https://energy-web-foundation.gitbook.io/energy-web/how-tos-and-tutorials/connect-to-energy-web-chain-main-network-with-metamash).
|
||||
|
||||
**Bridge.** To bridge assets between Ethereum Mainnet and Energy Web Chain and Ethereum mainnet, you can use [Carbonswap bridge](https://bridge.carbonswap.exchange/).
|
||||
|
||||
### Production: Optimism (OP) Mainnet
|
||||
|
||||
<table data-header-hidden>
|
||||
<tbody>
|
||||
<tr><td>Native token</td></td><td>ETH</td></tr>
|
||||
<tr><td>OCEAN address</td><td><a href="https://optimistic.etherscan.io/address/0x2561aa2bB1d2Eb6629EDd7b0938d7679B8b49f9E">0x2561aa2bB1d2Eb6629EDd7b0938d7679B8b49f9E</a></td></tr>
|
||||
<tr><td>Explorer</td><td><a href="https://optimistic.etherscan.io">https://optimistic.etherscan.io</a></td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
**Wallet.** If you cannot find Optimism as a predefined network in your wallet, you can manually connect to with [this OP guide](https://community.optimism.io/docs/useful-tools/networks/#op-mainnet).
|
||||
|
||||
**Bridge.** Follow the [OP Bridge guide](https://https://app.optimism.io/bridge/deposit) to deposit, withdraw and send tokens.
|
||||
|
||||
### Production: Moonriver
|
||||
|
||||
<table data-header-hidden>
|
||||
<tbody>
|
||||
<tr><td>Native token</td></td><td>Moonriver MOVR</td></tr>
|
||||
<tr><td>OCEAN address</td><td><a href="https://blockscout.moonriver.moonbeam.network/token/0x99C409E5f62E4bd2AC142f17caFb6810B8F0BAAE/token-transfers">0x99C409E5f62E4bd2AC142f17caFb6810B8F0BAAE</a></td></tr>
|
||||
<tr><td>Explorer</td><td><a href="https://blockscout.moonriver.moonbeam.network">https://blockscout.moonriver.moonbeam.network</a></td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
[Moonriver](https://moonbeam.network/networks/moonriver/) is an EVM-based parachain of Kusama.
|
||||
|
||||
**Wallet.** If Moonriver is not listed as a predefined network in your wallet, you can manually connect to it by following [Moonriver's guide](https://docs.moonbeam.network/builders/get-started/networks/moonriver/#connect-metamask).
|
||||
|
||||
**Bridge.** To bridge assets between Moonriver and Ethereum mainnet, you can use [the Anyswap Bridge](https://anyswap.exchange/#/bridge).
|
||||
|
||||
|
||||
## Test Networks
|
||||
|
||||
Unlike production networks, tokens on test networks do not hold real economic value.
|
||||
|
||||
### Testnet: Görli
|
||||
|
||||
<table data-header-hidden>
|
||||
<tbody>
|
||||
<tr><td>Native token</td></td><td>Görli (fake) ETH</td></tr>
|
||||
<tr><td>Native token faucet</td><td><a href="https://goerlifaucet.com/">Here</a></td></tr>
|
||||
<tr><td>OCEAN address</td><td><a href="https://goerli.etherscan.io/address/0xcfdda22c9837ae76e0faa845354f33c62e03653a">0xCfDdA22C9837aE76E0faA845354f33C62E03653a</a></td></tr>
|
||||
<tr><td>OCEAN faucet</td><td><a href="https://faucet.goerli.oceanprotocol.com">Here</a></td></tr>
|
||||
<tr><td>Explorer</td><td>https://goerli.etherscan.io</a></td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
**Wallet.** To connect with e.g. MetaMask, click on the network name dropdown and select _Goerli_ from the list of available networks.
|
||||
|
||||
### Testnet: Sepolia
|
||||
|
||||
<table data-header-hidden>
|
||||
<tbody>
|
||||
<tr><td>Native token</td></td><td>Sepolia (fake) ETH </td></tr>
|
||||
<tr><td>Native token faucet</td><td><a href="https://sepoliafaucet.com/">Here</a></td></tr>
|
||||
<tr><td>OCEAN address</td><td><a href="https://sepolia.etherscan.io/address/0x1B083D8584dd3e6Ff37d04a6e7e82b5F622f3985">0x1B083D8584dd3e6Ff37d04a6e7e82b5F622f3985</a></td></tr>
|
||||
<tr><td>OCEAN faucet</td><td><a href="https://faucet.sepolia.oceanprotocol.com/">Here</a></td></tr>
|
||||
<tr><td>Explorer</td><td><a href="https://sepolia.etherscan.io/">https://sepolia.etherscan.io</a></td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
**Wallet.** To connect with e.g. MetaMask, select "Sepolia" from the network dropdown list(enable "Show test networks").
|
||||
|
||||
|
||||
### Testnet: Mumbai
|
||||
|
||||
<table data-header-hidden>
|
||||
<tbody>
|
||||
<tr><td>Native token</td><td>Mumbai (fake) MATIC</td></tr>
|
||||
<tr><td>Native token faucet</td><td><a href="https://faucet.matic.network/">Here</a></td></tr>
|
||||
<tr><td>OCEAN address</td><td><a href="https://mumbai.polygonscan.com/token/0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8">0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8</a></td></tr>
|
||||
<tr><td>OCEAN faucet</td><td><a href="https://faucet.mumbai.oceanprotocol.com/">Here</a></td></tr>
|
||||
<tr><td>Explorer</td><td><a href="https://mumbai.polygonscan.com">https://mumbai.polygonscan.com</a></td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
**Wallet.** To connect with e.g. MetaMask, select "Görli" from the network dropdown list. If it's not listed as a predefined network, follow [Polygon's guide](https://wiki.polygon.technology/docs/develop/metamask/config-polygon-on-metamask/).
|
||||
|
||||
|
||||
### Testnet: Oasis Sapphire Testnet
|
||||
|
||||
[Ocean Predictoor](../predictoor/README.md) is deployed on Oasis Sapphire testnet. This deployment does do not currently support ocean.js, ocean.py, or Ocean Market.
|
||||
|
||||
|
||||
<table data-header-hidden>
|
||||
<tbody>
|
||||
<tr><td>Native token</td><td>(fake) ROSE</td></tr>
|
||||
<tr><td>Native token faucet</td><td><a href="https://github.com/oceanprotocol/pdr-backend/blob/main/READMEs/testnet-faucet.md#get-fake-rose-on-sapphire-testnet">Here</a></td></tr>
|
||||
<tr><td>OCEAN address</td><td><a href="https://explorer.oasis.io/testnet/sapphire/address/0x973e69303259B0c2543a38665122b773D28405fB">0x973e69303259B0c2543a38665122b773D28405fB</a></td></tr>
|
||||
<tr><td>OCEAN faucet</td><td><a href="https://github.com/oceanprotocol/pdr-backend/blob/main/READMEs/testnet-faucet.md#get-fake-ocean-on-sapphire-testnet">Here</a></td></tr>
|
||||
<tr><td>Explorer</td><td><a href="https://explorer.oasis.io/testnet/sapphire/">https://explorer.oasis.io/testnet/sapphire</a></td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
**Wallet.** If you cannot find Oasis Sapphire Testnet as a predefined network, you can manually connect to it by entering the following during import: Network Name: `Oasis Sapphire Testnet`, RPC URL: `https://testnet.sapphire.oasis.dev`, Chain ID: `23295`, Token: `ROSE`. For further info, see [Oasis tokens docs](https://docs.oasis.io/general/manage-tokens/).
|
||||
|
||||
|
||||
### Testnet: Optimism (OP) Sepolia
|
||||
|
||||
<table data-header-hidden>
|
||||
<tbody>
|
||||
<tr><td>Native token</td></td><td>Sepolia (fake) ETH</td></tr>
|
||||
<tr><td>Native token faucet</td><td><a href="https://faucet.quicknode.com/optimism/sepolia">Here</a></td></tr>
|
||||
<tr><td>OCEAN address</td><td><a href="https://sepolia-optimism.etherscan.io/address/0xf26c6c93f9f1d725e149d95f8e7b2334a406ad10">0xf26c6C93f9f1d725e149d95f8E7B2334a406aD10</a></td></tr>
|
||||
<tr><td>OCEAN faucet</td><td><a href="https://faucet.op-sepolia.oceanprotocol.com/">Here</a></td></tr>
|
||||
<tr><td>Explorer</td><td><a href="https://sepolia-optimism.etherscan.io/">https://sepolia-optimism.etherscan.io</a></td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
**Wallet.** If OP Sepolia is not listed as a predefined network, follow [OP's Guide](https://community.optimism.io/docs/useful-tools/networks/#op-sepolia).
|
||||
|
||||
----
|
||||
|
||||
_Next: [Bridges](bridges.md)_
|
||||
|
||||
_Back: [OCEAN: the Ocean token](../ocean-token.md)_
|
||||
|
||||
Check out the OP Bridge [guide](https://https://app.optimism.io/bridge/deposit) to deposit, withdraw and send tokens.
|
||||
|
||||
@ -5,17 +5,17 @@ description: Transfer tokens between two blockchain networks.
|
||||
|
||||
# Bridges
|
||||
|
||||
A bridge is a mechanism that connects two or more separate blockchain networks, enabling communication and interoperability between them. Bridges can be designed to facilitate the transfer of assets, data, or messages between different blockchain networks that may operate on different protocols, and consensus mechanisms, or have different native currencies.
|
||||
This page covers bridges of OCEAN from Ethereum mainnet to...
|
||||
- BNB Smart Chain
|
||||
- Polygon
|
||||
|
||||
We suggest using the following solutions to transfer OCEAN between Ethereum mainnet and Polygon or BSC.
|
||||
For other bridges and networks, see the [Networks page](README.md).
|
||||
|
||||
## Celer Bridge
|
||||
The rest of this doc gives bridging details. You can skip it until you need the reference information.
|
||||
|
||||
To transfer OCEAN to and from the Oasis Sapphire Mainnet, we recommend using the [Celer Bridge](https://cbridge.celer.network/1/23294/OCEAN). No bridge is needed for transfering OCEAN to the Oasis Sapphire Testnet because Ocean Protocol offers a [faucet](https://faucet.sapphire.oceanprotocol.com/) for OCEAN on Oasis Sapphire Testnet. Note that Ocean Protocol supports Oasis Sapphire networks for [Predictoor](https://predictoor.ai) development, and does not currently support Oasis Sapphire for ocean.js, ocean.py, or Ocean Market.
|
||||
### BNB Smart Chain Bridge
|
||||
|
||||
## BNB Smart Chain Bridge
|
||||
|
||||
To transfer OCEAN to and from the BNB Smart Chain, we recommend using the [Binance Bridge](https://www.bnbchain.org/en/bridge). BSC offers various options such as withdrawing crypto from [Binance](https://www.binance.com/en) and utilizing the [Binance Bridge](https://www.bnbchain.org/en/bridge). You can refer to the Binance Academy article "[How to Get Started with BSC](https://academy.binance.com/en/articles/how-to-get-started-with-binance-smart-chain-bsc)" for more information.
|
||||
To transfer OCEAN to and from the BNB Smart Chain, we recommend using [Binance Bridge](https://www.bnbchain.org/en/bridge). BSC offers various options such as withdrawing crypto from [Binance](https://www.binance.com/en) and utilizing the [Binance Bridge](https://www.bnbchain.org/en/bridge). You can refer to the Binance Academy article "[How to Get Started with BSC](https://academy.binance.com/en/articles/how-to-get-started-with-binance-smart-chain-bsc)" for more information.
|
||||
|
||||
{% hint style="warning" %}
|
||||
In case you opt for an alternative bridge option and intend to transfer tokens to Binance, it is **crucial** to ensure that the contract address you are sending the tokens to is correct.
|
||||
@ -23,7 +23,7 @@ In case you opt for an alternative bridge option and intend to transfer tokens t
|
||||
<img src="../../.gitbook/assets/wallet/binance-receive.png" alt="Binance deposit" data-size="original">
|
||||
{% endhint %}
|
||||
|
||||
## Polygon (ex Matic) Bridge
|
||||
### Polygon (ex Matic) Bridge
|
||||
|
||||
The Polygon Network (previously known as Matic) offers a [bridge](https://wallet.polygon.technology/bridge/), which lets you easily transfer digital assets between Ethereum and Polygon blockchains and a dedicated [wallet](https://wallet.polygon.technology/) designed for this purpose, which can be linked to your account through Metamask or other compatible wallets.
|
||||
|
||||
@ -81,3 +81,11 @@ Alternatively, you can manually configure the network on Metamask by using the f
|
||||
| Currency Symbol | `MATIC` |
|
||||
| Block Explorer URL | [`https://polygonscan.com`](https://polygonscan.com) |
|
||||
|
||||
|
||||
|
||||
----
|
||||
|
||||
_Next: [FAQ](../faq.md)_
|
||||
|
||||
_Back: [Networks](README.md)_
|
||||
|
||||
|
||||
@ -1,31 +0,0 @@
|
||||
# Ocean 101
|
||||
|
||||
<figure><img src="../.gitbook/assets/gif/giphy.gif" alt=""><figcaption><p>Let's see how it works</p></figcaption></figure>
|
||||
|
||||
## How Does Ocean Work?
|
||||
|
||||
Ocean Protocol utilizes a combination of blockchain technology, decentralized networks, and cryptographic techniques to facilitate secure and privacy-preserving data sharing. Here's an overview of how Ocean works:
|
||||
|
||||
1. **Asset Registration**: Data providers register their data assets on the Ocean blockchain, providing metadata that describes the asset, its usage terms, and pricing information. This metadata is stored on-chain and can be accessed by potential data consumers.
|
||||
2. **Discovery and Access Control**: Data consumers can discover available data assets through decentralized metadata services like Aquarius. Access control mechanisms, such as smart contracts, verify the consumer's permissions and handle the transfer of data access tokens.
|
||||
3. **Secure Data Exchange**: When a data consumer purchases access to a data asset, the asset's metadata, and access instructions are encrypted by the data provider using the Provider service. The encrypted asset is then securely transferred to the consumer, who can decrypt and utilize it without revealing the asset's URL.
|
||||
4. [**Compute-to-Data**](../developers/compute-to-data/README.md) **(C2D)**: Ocean Protocol supports C2D capabilities, allowing data consumers to perform computations on data assets without direct access to the underlying data. The compute operations are executed in a secure and controlled environment, ensuring data privacy and compliance.
|
||||
5. **Incentives and Governance**: Ocean Protocol incorporates tokenomics and a governance framework to incentivize participants and ensure the sustainability and evolution of the ecosystem. Participants can earn and stake OCEAN for veOCEAN, curate data, contribute to the network and participate in governance decisions.
|
||||
|
||||
Ocean Protocol also combines advanced technologies and web components to create a robust and efficient data ecosystem.
|
||||
|
||||
<figure><img src="../.gitbook/assets/architecture/Ocean101.png" alt=""><figcaption><p>Ocean architectural overview </p></figcaption></figure>
|
||||
|
||||
Powerful libraries such as [Ocean.js](../developers/ocean.js/README.md) (JavaScript) and [Ocean.py](../data-scientists/ocean.py/README.md) (Python) facilitate seamless integration and interaction with the protocol, offering a wide range of functionalities.
|
||||
|
||||
Ocean Protocol incorporates middleware components that enhance efficiency and streamline interactions. Components such as [Aquarius](../developers/aquarius/README.md) act as a metadata cache, improving search efficiency by caching on-chain data into Elasticsearch while [Provider](../developers/provider/README.md) plays a crucial role in various ecosystem operations, assisting in asset downloading, handling encryption of [Decentralized Data Objects](../developers/ddo-specification.md) (DDOs), and facilitating communication with the operator-service for Compute-to-Data jobs. And finally, the [Subgraph](../developers/subgraph/README.md), an off-chain service leveraging GraphQL, offers efficient access to information related to datatokens, users, and balances.
|
||||
|
||||
These libraries and middleware components contribute to efficient data discovery and secure interactions within the Ocean Protocol ecosystem.
|
||||
|
||||
By leveraging these tools and technologies, developers can harness the power of decentralized data while creating innovative applications and unlocking the true value of data assets.
|
||||
|
||||
<figure><img src="../.gitbook/assets/architecture/decentralized_exchanges_marketplaces.png" alt=""><figcaption><p>Build dApps with Ocean</p></figcaption></figure>
|
||||
|
||||
Ocean Protocol gives people and organizations the power to unleash the true value of their data. With its decentralized marketplaces, rock-solid data-sharing technologies, and privacy protection measures, Ocean Protocol opens the door for collaboration, sparks innovation, and encourages responsible and ethical data usage.
|
||||
|
||||
It's all about making data work for everyone in a fair and transparent data economy.
|
||||
134
discover/ocean-token.md
Normal file
134
discover/ocean-token.md
Normal file
@ -0,0 +1,134 @@
|
||||
---
|
||||
description:
|
||||
---
|
||||
|
||||
# OCEAN: The Ocean Token
|
||||
|
||||
OCEAN is a utility token. It's used to stake on data for curation, buy & sell data, and more. Its supply is disbursed over time to drive near-term growth and long-term sustainability.
|
||||
|
||||
**Contents:**
|
||||
- Getting and storing OCEAN
|
||||
- Staking OCEAN
|
||||
- OCEAN supply
|
||||
- Token design
|
||||
- OCEAN addresses
|
||||
|
||||
<div align="center"><figure><img src="../.gitbook/assets/general/purchase-and-compute_and_ocean-network.png" width="60%"></figure></div>
|
||||
|
||||
|
||||
## Getting and Storing OCEAN
|
||||
|
||||
OCEAN is available on most leading CEXes and DEXes. The [Ocean Token page at oceanprotocol.com](https://oceanprotocol.com/about-us/ocean-token) has details.
|
||||
|
||||
The [Wallets User Guide](../user-guides/wallets/README.md) here in Ocean docs shows how to set up wallets and store OCEAN.
|
||||
|
||||
## Staking OCEAN
|
||||
|
||||
You can lock OCEAN and earn rewards via [Ocean Data Farming](../data-farming/README.md).
|
||||
|
||||
## OCEAN supply
|
||||
|
||||
Total # tokens: 1.41B. All tokens are minted; all control is [revoked](https://blog.oceanprotocol.com/control-over-the-ocean-contract-to-be-revoked-soon-overview-6c5b15be2db).
|
||||
|
||||
OCEAN supply is divided as follows:
|
||||
|
||||
- 51% (719.1M OCEAN) - to Data Farming and incentives programs. Distributed via vesting: burn-in period then 4-year half-life. For details, see section 5.1 "OCEAN Emissions Schedule" of [Data Farming Main](https://blog.oceanprotocol.com/ocean-data-farming-main-is-here-49c99602419e#5a8f).
|
||||
- 15% (211.5M OCEAN) - to Ocean community (grants, more) and foundation operations.
|
||||
- 10% (141.0M OCEAN) - to the founding company, and in turn to its investors, employees & operations
|
||||
- 24% (338.4M OCEAN) - to token acquirors. This completed in early 2019. All acquiror vesting is complete as well.
|
||||
|
||||
## OCEAN Token Design
|
||||
|
||||
The system-level design of the OCEAN token is based on [The Web3 Sustainability Loop](https://blog.oceanprotocol.com/the-web3-sustainability-loop-b2a4097a36e), a general design pattern. The Ocean-specific version of this design is described in [section (7) of that same article](https://blog.oceanprotocol.com/the-web3-sustainability-loop-b2a4097a36e#e0f6).
|
||||
|
||||
This design gives flexibility to adapt the Ocean products for traction and growth. The flexibility is due to the goal to "drive network revenue", subject to the constraints of the mission & values of Ocean Protocol.
|
||||
|
||||
In the design, a % of revenue is used to buy back & burn OCEAN. The remaining % drives growth.
|
||||
|
||||
<div align="center"><figure><img src="../.gitbook/assets/general/whirlpool.png" width="60%"></figure></div>
|
||||
|
||||
|
||||
## OCEAN addresses
|
||||
|
||||
The "root" OCEAN token is deployed on Ethereum mainnet with address [`0x967da4048cd07ab37855c090aaf366e4ce1b9f48`](https://etherscan.io/token/0x967da4048cd07ab37855c090aaf366e4ce1b9f48).
|
||||
|
||||
The OCEAN token has bridges to several [other chains](networks/README.md). It has a unique address on each chain.
|
||||
|
||||
<details>
|
||||
|
||||
<summary><mark style="color:black;"><i>OCEAN address per chain: (expand me)</i></mark></summary>
|
||||
|
||||
<table data-full-width="false">
|
||||
<thead>
|
||||
<tr>
|
||||
<th width="161">Network name</th>
|
||||
<th width="444">Contract Address</th>
|
||||
<th width="105">Symbol</th>
|
||||
<th>Decimals</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><strong>Mainnet</strong></td>
|
||||
<td>0x967da4048cD07aB37855c090aAF366e4ce1b9F48</td>
|
||||
<td>OCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Polygon</strong><br><strong>(ex Matic)</strong></td>
|
||||
<td>0x282d8efCe846A88B159800bd4130ad77443Fa1A1</td>
|
||||
<td>mOCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>BNB</strong><br><strong>BNB Smart Chain</strong></td>
|
||||
<td>0xdce07662ca8ebc241316a15b611c89711414dd1a</td>
|
||||
<td>OCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Oasis Sapphire</strong></td>
|
||||
<td>0x39d22B78A7651A76Ffbde2aaAB5FD92666Aca520</td>
|
||||
<td>OCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Optimism</strong></td>
|
||||
<td>0xf26c6c93f9f1d725e149d95f8e7b2334a406ad10</td>
|
||||
<td>OCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Görli</strong></td>
|
||||
<td>0xCfDdA22C9837aE76E0faA845354f33C62E03653a</td>
|
||||
<td>OCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Mumbai</strong></td>
|
||||
<td>0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8</td>
|
||||
<td>OCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Sepolia</strong></td>
|
||||
<td>0x1B083D8584dd3e6Ff37d04a6e7e82b5F622f3985</td>
|
||||
<td>OCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Oasis Sapphire Testnet</strong></td>
|
||||
<td>0x973e69303259B0c2543a38665122b773D28405fB</td>
|
||||
<td>OCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
</details>
|
||||
|
||||
----
|
||||
|
||||
_Next: [Networks](networks/README.md)_
|
||||
|
||||
_Back: [What can you do with Ocean?](benefits.md)_
|
||||
@ -1,103 +0,0 @@
|
||||
---
|
||||
description: >-
|
||||
How to use a crypto wallet to check your OCEAN balance and send OCEAN
|
||||
Tokens to others
|
||||
---
|
||||
|
||||
# Manage Your OCEAN
|
||||
|
||||
If you don't see any OCEAN in your crypto wallet software 🔎 (e.g. MetaMask or MyEtherWallet), don't worry! It might not know how to manage OCEAN yet.
|
||||
|
||||
### Token Information
|
||||
|
||||
Almost all ERC-20 wallets require these values for adding a custom token:
|
||||
|
||||
<table data-full-width="false">
|
||||
<thead>
|
||||
<tr>
|
||||
<th width="161">Network name</th>
|
||||
<th width="444">Contract Address</th>
|
||||
<th width="105">Symbol</th>
|
||||
<th>Decimals</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><strong>Mainnet</strong></td>
|
||||
<td>0x967da4048cD07aB37855c090aAF366e4ce1b9F48</td>
|
||||
<td>OCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Polygon</strong><br><strong>(ex Matic)</strong></td>
|
||||
<td>0x282d8efCe846A88B159800bd4130ad77443Fa1A1</td>
|
||||
<td>mOCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>BNB</strong><br><strong>BNB Smart Chain</strong></td>
|
||||
<td>0xdce07662ca8ebc241316a15b611c89711414dd1a</td>
|
||||
<td>OCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Oasis Sapphire</strong></td>
|
||||
<td>0x39d22B78A7651A76Ffbde2aaAB5FD92666Aca520</td>
|
||||
<td>OCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Optimism</strong></td>
|
||||
<td>0xf26c6c93f9f1d725e149d95f8e7b2334a406ad10</td>
|
||||
<td>OCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Görli</strong></td>
|
||||
<td>0xCfDdA22C9837aE76E0faA845354f33C62E03653a</td>
|
||||
<td>OCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Mumbai</strong></td>
|
||||
<td>0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8</td>
|
||||
<td>OCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Sepolia</strong></td>
|
||||
<td>0x1B083D8584dd3e6Ff37d04a6e7e82b5F622f3985</td>
|
||||
<td>OCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Oasis Sapphire Testnet</strong></td>
|
||||
<td>0x973e69303259B0c2543a38665122b773D28405fB</td>
|
||||
<td>OCEAN</td>
|
||||
<td>18</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
The [token page](https://oceanprotocol.com/token) at oceanprotocol.com has further details.
|
||||
|
||||
### MetaMask
|
||||
|
||||
1. Make sure MetaMask is connected to the Ethereum Mainnet.
|
||||
2. Select the account you want to manage.
|
||||
3. Scroll down until the `Import Tokens` link is visible, then click on it.
|
||||
4. Click on `Custom Tokens`.
|
||||
5. Paste the OCEAN contract address listed above into the _Token Contract Address_ field. The other two fields should auto-fill. If not, add `OCEAN` for the symbol and `18` for the precision.
|
||||
6. Click `Add custom token`.
|
||||
7. Click `Import Tokens`.
|
||||
|
||||
If you prefer visual demonstrations, we have prepared a visual demo that illustrates the steps mentioned above.
|
||||
|
||||
{% embed url="https://app.arcade.software/share/yHiKKN336QGdAkhTlsIh" fullWidth="false" %}
|
||||
{% endembed %}
|
||||
|
||||
MetaMask should now show your OCEAN balance, and when you're looking at that, there should be a `Send` button to send OCEAN to others. For help with that, see [the MetaMask docs about how to send tokens](https://metamask.zendesk.com/hc/en-us/articles/360015488931-How-to-Send-Tokens).
|
||||
|
||||
### Other Wallet Software
|
||||
|
||||
Do a web search to find out how to add a custom ERC-20 token to the wallet software you're using.
|
||||
71
discover/what-is-ocean.md
Normal file
71
discover/what-is-ocean.md
Normal file
@ -0,0 +1,71 @@
|
||||
---
|
||||
description:
|
||||
---
|
||||
|
||||
<div align="center"><figure><img src="../.gitbook/assets/discover/wait.png" width="60%"></figure></div>
|
||||
|
||||
## What is Ocean?
|
||||
|
||||
Ocean is a decentralized data exchange protocol.
|
||||
|
||||
AI lives on data; Ocean facilitates it.
|
||||
|
||||
Ocean has two specific parts:
|
||||
- A live tech stack. At the core is **Datatokens** and **Compute-to-Data**
|
||||
- A lively community. This includes **builders, data scientists, OCEAN holders**, and **Ocean Ambassadors**. Ocean's community is active on **social media**.
|
||||
|
||||
Let's drill into each.
|
||||
|
||||
## Tech: Ocean data NFTs and datatokens
|
||||
|
||||
These enable decentralized access control, via token-gating. Key principles:
|
||||
|
||||
- Publish data services as ERC721 data NFTs and ERC20 datatokens
|
||||
- You can access the dataset / data service if you hold 1.0 datatokens
|
||||
- Consuming data services = spending datatokens
|
||||
|
||||
Crypto wallets, exchanges, and DAOs become _data_ wallets, exchanges, and DAOs.
|
||||
|
||||
<div align="center">
|
||||
<figure><img src="../.gitbook/assets/discover/onramp-offramp.png"><br><figcaption>Data NFTs & datatokens are an on-ramp and off-ramp for data assets into DeFi</figcaption></figure>
|
||||
</div>
|
||||
|
||||
Data can be on Azure or AWS, Filecoin or Arweave, REST APIs or smart contract feeds. Data may be raw AI training data, feature vectors, trained models, even AI model predictions, or non-AI data.
|
||||
|
||||
## Tech: Ocean Compute-to-Data
|
||||
|
||||
This enables one buy & sell private data, while preserving privacy
|
||||
- Private data is valuable: using it can improve research and business outcomes. But concerns over privacy and control make it hard to access.
|
||||
- Compute-to-Data (C2D) grants access run compute against the data, _on the same premises of the data_. Only the results are visible to the consumer. The data never leaves the premises. Decentralized blockchain technology does the handshaking.
|
||||
- C2D enables people to sell private data while preserving privacy, as an opportunity for companies to monetize their data assets.
|
||||
- C2D can also be used for data sharing in science or technology contexts, with lower liability risk, because the data doesn't move.
|
||||
|
||||
<div align="center">
|
||||
<figure><img src="../.gitbook/assets/discover/c2d-mental-model.png" width="75%"><br><figcaption>Compute-to-Data flow</figcaption></figure>
|
||||
</div>
|
||||
|
||||
## Community: Ocean Ecosystem
|
||||
|
||||
Ocean has a lively [ecosystem](https://oceanprotocol.com/explore/ecosystem) of dapps grown over years, built by enthusiastic developers.
|
||||
|
||||
<div align="center"><figure><img src="../.gitbook/assets/discover/builders.png" width="50%"></figure></div>
|
||||
|
||||
The Ocean ecosystem also contains many data scientists and OCEAN holders, excited about the future of AI & data. You can find them doing predictions, data challenges, Data Farming, and more.
|
||||
|
||||
## Community: Ocean Ambassadors
|
||||
|
||||
Ocean has an excellent [community of ambassadors](https://oceanprotocol.com/explore/community). Anyone can join.
|
||||
|
||||
<div align="center"><figure><img src="../.gitbook/assets/discover/ambassadors.png" width="50%"></figure></div>
|
||||
|
||||
## Community: Social Media
|
||||
|
||||
Follow Ocean on [Twitter](https://twitter.com/OceanProtocol) or [Telegram](https://t.me/oceanprotocol_community) to keep up to date. Chat directly with the Ocean community on [Discord](https://discord.gg/TnXjkR5). Or, track Ocean progress directly on [GitHub](https://github.com/oceanprotocol).
|
||||
|
||||
Finally, the [Ocean blog](https://blog.oceanprotocol.com/) has regular updates.
|
||||
|
||||
----
|
||||
|
||||
_Next: [What can you do with Ocean?](benefits.md)_
|
||||
|
||||
_Back: [Why Ocean?](why-ocean.md)_
|
||||
17
discover/why-ocean.md
Normal file
17
discover/why-ocean.md
Normal file
@ -0,0 +1,17 @@
|
||||
---
|
||||
description:
|
||||
---
|
||||
|
||||
### Why Ocean?
|
||||
|
||||
Ocean was founded to level the playing field for AI and data.
|
||||
|
||||
{% embed url="https://youtu.be/4P72ZelkEpQ" %}
|
||||
|
||||
To dive deeper, see [this blog](https://blog.oceanprotocol.com/from-ai-to-blockchain-to-data-meet-ocean-f210ff460465) or [this video](https://youtu.be/XN_PHg1K61w).
|
||||
|
||||
----
|
||||
|
||||
_Next: [What is Ocean?](what-is-ocean.md)_
|
||||
|
||||
_Back: [Discover Ocean: main](README.md)_
|
||||
@ -28,7 +28,11 @@ Ocean Predictoor provides on-chain "prediction feeds" on whether ETH, BTC, etc w
|
||||
|
||||
Finally, join us on [**Discord**](https://discord.gg/TnXjkR5) to chat with other predictoors, traders, or devs in the Predictoor ecosystem.
|
||||
|
||||
## Next step
|
||||
|
||||
If you're going through docs sequentially: next is [Introduction](pdr-intro.md).
|
||||
----
|
||||
|
||||
_Next: [Introduction](pdr-intro.md)_
|
||||
|
||||
_Back: [Docs main](../README.md)_
|
||||
|
||||
|
||||
|
||||
@ -83,7 +83,9 @@ The implementation is in templates/ERC20Template3.sol at at [Ocean’s contracts
|
||||
|
||||
**- Predictoor behavior.** Each datatoken contract has additional methods specific to Predictoor: submitting predictions, submitting truevals, computing aggregated predictions, etc.
|
||||
|
||||
----
|
||||
|
||||
## Next step
|
||||
_Next: [How to earn](pdr-earn.md)_
|
||||
|
||||
_Back: [Introduction](pdr-intro.md)_
|
||||
|
||||
If you're going through docs sequentially: next is [How to earn](pdr-earn.md).
|
||||
|
||||
@ -64,12 +64,13 @@ The image below has the same experimental setup, but for BTC/USDT pair. The size
|
||||
|
||||
<figure><img src="../.gitbook/assets/predictoor/simulated_returns_btc_usdt.png" alt=""><figcaption>Simulated returns vs time of BTC/USDT trading on Binance. Trade size has little impact.</figcaption></figure>
|
||||
|
||||
----
|
||||
|
||||
## Next step
|
||||
_Next: [Parameters](pdr-parameters.md)_
|
||||
|
||||
If you're going through docs sequentially: next is [Parameters](pdr-parameters.md).
|
||||
_Back: [Architecture](pdr-architecture.md)_
|
||||
|
||||
Or to drill into earning further:
|
||||
_Or, drill into earning further:_
|
||||
- [Pdr-backend repo](https://github.com/oceanprotocol/pdr-backend) - how to run bots, specifically
|
||||
- [Predictoor Data Farming](../data-farming/predictoordf.md) - baseline sales $ for running predictoor bots
|
||||
|
||||
|
||||
@ -158,6 +158,9 @@ Predictoor needs to leverage a privacy-preserving EVM chain which is in producti
|
||||
</details>
|
||||
|
||||
|
||||
## Next step
|
||||
----
|
||||
|
||||
_Next: [Further Resources](pdr-resources.md)_
|
||||
|
||||
_Back: [Parameters](pdr-parameters.md)_
|
||||
|
||||
If you're going through docs sequentially: next is [Further Resources](pdr-resources.md).
|
||||
|
||||
@ -33,8 +33,8 @@ Alas, accurate predictions are *hard*. Worse, typical prediction feeds have no a
|
||||
<figure><img src="../.gitbook/assets/predictoor/predictoor_ui.png" alt=""><figcaption>Screenshot from predictoor.ai</figcaption></figure>
|
||||
|
||||
|
||||
## Next step
|
||||
|
||||
If you're going through docs sequentially: next is [Architecture](pdr-architecture.md).
|
||||
----
|
||||
|
||||
_Next: [Architecture](pdr-architecture.md)_
|
||||
|
||||
_Back: [Predictoor Docs main](README.md)_
|
||||
|
||||
@ -32,6 +32,9 @@ The price to subscribe to one feed for 24 hours is 3.00 OCEAN. This includes all
|
||||
Pricing is subject to change based on learnings, and feedback from community.
|
||||
|
||||
|
||||
## Next step
|
||||
----
|
||||
|
||||
_Next: [FAQ](pdr-faq.md)_
|
||||
|
||||
_Back: [How to earn](pdr-earn.md)_
|
||||
|
||||
If you're going through docs sequentially: next is [FAQ](pdr-faq.md).
|
||||
|
||||
@ -14,10 +14,11 @@ For thoroughness:
|
||||
- All blog posts & media: ["Ocean Predictoor Series"](https://blog.oceanprotocol.com/ocean-predictoor-series-6a9122754a4d)
|
||||
- Webapp code is at [pdr-web](https://github.com/oceanprotocol/pdr-web/) repo
|
||||
|
||||
## Next step
|
||||
----
|
||||
|
||||
Congrats, you've gone through all the Predictoor docs!
|
||||
|
||||
Follow-up links:
|
||||
- Go earn! Start at [how to earn](pdr-earn.md)
|
||||
- [Predictoor docs Homepage](README.md)
|
||||
_Next: Go earn! Start at [how to earn](pdr-earn.md). Or, go to [Predictoor docs homepage](README.md)_
|
||||
|
||||
_Back: [FAQ](pdr-faq.md)_
|
||||
|
||||
|
||||
@ -10,9 +10,45 @@ coverY: 0
|
||||
|
||||
<figure><img src="../.gitbook/assets/gif/follow-instructions.gif" alt="" width="375"><figcaption></figcaption></figure>
|
||||
|
||||
### Tokenize & sell your data
|
||||
These are guides to use Ocean, with no coding needed.
|
||||
|
||||
Buy, mint, and sell NFTs using the Ocean Market following the guides below.
|
||||
**Contents:**
|
||||
- Basic concepts
|
||||
- Using wallets
|
||||
- Using Ocean Market
|
||||
- C2D in Ocean Market
|
||||
- Host assets
|
||||
|
||||
Let's dive in!
|
||||
|
||||
## Basic concepts
|
||||
|
||||
For blockchain beginners
|
||||
|
||||
{% content-ref url="basic-concepts.md" %}
|
||||
[basic-concepts.md](basic-concepts.md)
|
||||
{% endcontent-ref %}
|
||||
|
||||
## Using wallets
|
||||
|
||||
{% content-ref url="wallets/README.md" %}
|
||||
[wallets/README.md.md](wallets/README.md)
|
||||
{% endcontent-ref %}
|
||||
|
||||
{% content-ref url="wallets/metamask-setup.md" %}
|
||||
[wallets/metamask-setup.md](wallets/metamask-setup.md)
|
||||
{% endcontent-ref %}
|
||||
|
||||
{% content-ref url="wallets-and-ocean.md" %}
|
||||
[wallets-and-ocean.md](wallets-and-ocean.md)
|
||||
{% endcontent-ref %}
|
||||
|
||||
|
||||
## Using Ocean Market
|
||||
|
||||
{% content-ref url="using-ocean-market.md" %}
|
||||
[using-ocean-market.md](using-ocean-market.md)
|
||||
{% endcontent-ref %}
|
||||
|
||||
{% content-ref url="publish-data-nfts.md" %}
|
||||
[publish-data-nfts.md](publish-data-nfts.md)
|
||||
@ -22,27 +58,19 @@ Buy, mint, and sell NFTs using the Ocean Market following the guides below.
|
||||
[buy-data-nfts.md](buy-data-nfts.md)
|
||||
{% endcontent-ref %}
|
||||
|
||||
## C2D in Ocean Market
|
||||
|
||||
{% content-ref url="compute-to-data/" %}
|
||||
[compute-to-data](compute-to-data/README.md)
|
||||
{% endcontent-ref %}
|
||||
|
||||
## Host Assets
|
||||
|
||||
{% content-ref url="asset-hosting/" %}
|
||||
[asset-hosting](asset-hosting/README.md)
|
||||
{% endcontent-ref %}
|
||||
|
||||
{% content-ref url="using-ocean-market.md" %}
|
||||
[using-ocean-market.md](using-ocean-market.md)
|
||||
{% endcontent-ref %}
|
||||
|
||||
### Data Farming
|
||||
|
||||
Earn rewards by locking OCEAN, curating data assets, and more.
|
||||
|
||||
{% content-ref url="../data-farming/README.md" %}
|
||||
[../data-farming/README.md](../data-farming/README.md)
|
||||
{% endcontent-ref %}
|
||||
|
||||
### Antique Stuff 🏺
|
||||
## Antique Stuff 🏺
|
||||
|
||||
If you have OCEAN in old pools, this will help.
|
||||
|
||||
|
||||
25
user-guides/basic-concepts.md
Normal file
25
user-guides/basic-concepts.md
Normal file
@ -0,0 +1,25 @@
|
||||
---
|
||||
description: Learn the blockchain concepts behind Ocean
|
||||
---
|
||||
|
||||
# Basic Concepts
|
||||
|
||||
You'll need to know a thing or two about blockchains to understand Ocean Protocol's tech... Let's get started with the basics 🧑🏫
|
||||
|
||||
<figure><img src="../.gitbook/assets/gif/drew-barrymore-notes.gif" alt=""><figcaption><p>Prepare yourself, my friend</p></figcaption></figure>
|
||||
|
||||
### Blockchain: The backbone of Ocean
|
||||
|
||||
Blockchain is a revolutionary technology that enables the decentralized nature of Ocean. At its core, blockchain is a **distributed ledger** that securely **records and verifies transactions across a network of computers**. It operates on the following key concepts that ensure trust and immutability:
|
||||
|
||||
* **Decentralization**: Blockchain eliminates the need for intermediaries by enabling a peer-to-peer network where transactions are validated collectively. This decentralized structure reduces reliance on centralized authorities, enhances transparency, and promotes a more inclusive data economy.
|
||||
* **Immutability**: Once a transaction is recorded on the blockchain, it becomes virtually impossible to alter or tamper with. The data is stored in blocks, which are cryptographically linked together, forming an unchangeable chain of information. Immutability ensures the integrity and reliability of data, providing a foundation of trust in the Ocean ecosystem. Furthermore, it enables reliable traceability of historical transactions.
|
||||
* **Consensus Mechanisms**: Blockchain networks employ consensus mechanisms to validate and agree upon the state of the ledger. These mechanisms ensure that all participants validate transactions without relying on a central authority, crucially maintaining a reliable view of the blockchain's history. The consensus mechanisms make it difficult for malicious actors to manipulate the blockchain's history or conduct fraudulent transactions. Popular consensus mechanisms include Proof of Work (PoW) and Proof of Stake (PoS).
|
||||
|
||||
Ocean harnesses the power of blockchain to facilitate secure and auditable data exchange. This ensures that data transactions are transparent, verifiable, and tamper-proof. Here's how Ocean uses blockchains:
|
||||
|
||||
* **Data Asset Representation**: Data assets in Ocean are represented as non-fungible tokens (NFTs) on the blockchain. NFTs provide a unique identifier for each data asset, allowing for seamless tracking, ownership verification, and access control. Through NFTs and datatokens, data assets become easily tradable and interoperable within the Ocean ecosystem.
|
||||
* **Smart Contracts**: Ocean uses smart contracts to automate and enforce the terms of data exchange. Smart contracts act as self-executing agreements that facilitate the transfer of data assets between parties based on predefined conditions - they are the exact mechanisms of decentralization. This enables cyber-secure data transactions and eliminates the need for intermediaries.
|
||||
* **Tamper-Proof Audit Trail**: Every data transaction on Ocean is recorded on the blockchain, creating an immutable and tamper-proof audit trail. This ensures the transparency and traceability of data usage, providing data scientists with a verifiable record of the data transaction history. Data scientists can query addresses of data transfers on-chain to understand data usage.
|
||||
|
||||
By integrating blockchain technology, Ocean establishes a trusted infrastructure for data exchange. It empowers individuals and organizations to securely share, monetize, and leverage data assets while maintaining control and privacy.
|
||||
35
user-guides/wallets/wallets-and-ocean.md
Normal file
35
user-guides/wallets/wallets-and-ocean.md
Normal file
@ -0,0 +1,35 @@
|
||||
---
|
||||
description: >-
|
||||
How to use a crypto wallet to check your OCEAN balance and send OCEAN
|
||||
Tokens to others
|
||||
---
|
||||
|
||||
# Manage Your OCEAN
|
||||
|
||||
If you don't see any OCEAN in your crypto wallet software 🔎 (e.g. MetaMask or MyEtherWallet), don't worry! It might not know how to manage OCEAN yet.
|
||||
|
||||
For an ERC-20 wallet to see OCEAN, the wallet typically needs to have OCEAN's address added as a custom token.
|
||||
- The [OCEAN docs page](../discover/ocean-token.md) has the OCEAN address for each network.
|
||||
- Then, use that information for the wallet instructions below.
|
||||
|
||||
|
||||
### MetaMask
|
||||
|
||||
1. Make sure MetaMask is connected to the Ethereum Mainnet.
|
||||
2. Select the account you want to manage.
|
||||
3. Scroll down until the `Import Tokens` link is visible, then click on it.
|
||||
4. Click on `Custom Tokens`.
|
||||
5. Paste the OCEAN contract address listed above into the _Token Contract Address_ field. The other two fields should auto-fill. If not, add `OCEAN` for the symbol and `18` for the precision.
|
||||
6. Click `Add custom token`.
|
||||
7. Click `Import Tokens`.
|
||||
|
||||
If you prefer visual demonstrations, we have prepared a visual demo that illustrates the steps mentioned above.
|
||||
|
||||
{% embed url="https://app.arcade.software/share/yHiKKN336QGdAkhTlsIh" fullWidth="false" %}
|
||||
{% endembed %}
|
||||
|
||||
MetaMask should now show your OCEAN balance, and when you're looking at that, there should be a `Send` button to send OCEAN to others. For help with that, see [the MetaMask docs about how to send tokens](https://metamask.zendesk.com/hc/en-us/articles/360015488931-How-to-Send-Tokens).
|
||||
|
||||
### Other Wallet Software
|
||||
|
||||
Do a web search to find out how to add a custom ERC-20 token to the wallet software you're using.
|
||||
Loading…
Reference in New Issue
Block a user