Merge pull request #1081 from oceanprotocol/issue-1068-remove-liquidity-page
Add a page on removing liquidity using etherscan
This commit is contained in:
Akshay
GitHub
commit
beb0f1b078
Binary file not shown.
|
Before Width: | Height: | Size: 75 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 37 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 186 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 236 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 127 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 77 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 69 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 260 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 126 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 224 KiB |
|
|
@ -10,7 +10,7 @@
|
|||
* [Data NFTs and Datatokens](core-concepts/datanft-and-datatoken.md)
|
||||
* [Roles](core-concepts/roles.md)
|
||||
* [Networks](core-concepts/networks.md)
|
||||
* [Bridges](building-with-ocean/bridges.md)
|
||||
* [Bridges](core-concepts/networks/bridges.md)
|
||||
* [Fees](core-concepts/fees.md)
|
||||
* [Asset pricing](core-concepts/asset-pricing.md)
|
||||
* [DID & DDO](core-concepts/did-ddo.md)
|
||||
|
|
@ -18,6 +18,7 @@
|
|||
* [Publish a data asset](using-ocean-market/marketplace-publish-data-asset.md)
|
||||
* [Download a data asset](using-ocean-market/marketplace-download-data-asset.md)
|
||||
* [Publishing with hosting services](building-with-ocean/asset-hosting.md)
|
||||
* [Liquidity Pools [deprecated]](using-ocean-market/remove-liquidity-using-etherscan.md)
|
||||
* [Building with Ocean](building-with-ocean/README.md)
|
||||
* [Build a Marketplace](building-with-ocean/build-a-marketplace/README.md)
|
||||
* [Forking Ocean Market](building-with-ocean/build-a-marketplace/forking-ocean-market.md)
|
||||
|
|
@ -42,4 +43,3 @@
|
|||
* [API references](api-references/README.md)
|
||||
* [Aquarius REST API](api-references/aquarius-rest-api.md)
|
||||
* [Provider REST API](api-references/provider-rest-api.md)
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Publish assets using hosting services
|
|||
description: Tutorial to publish assets using hosting services like Google Drive and Azure.
|
||||
---
|
||||
|
||||
# Publish assets using hosting services
|
||||
# Publishing with hosting services
|
||||
|
||||
### Overview
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
title: Forking Ocean Market
|
||||
description: Forking and customizing Ocean Market (Frontend)
|
||||
featuredImage: images/creatures/mantaray/mantaray-full@2x.png
|
||||
description: Forking and customizing Ocean Market (Frontend)
|
||||
---
|
||||
|
||||
# 🐟 Forking and customizing Ocean Market
|
||||
# Build a Marketplace
|
||||
|
||||
## Outcome
|
||||
|
||||
|
|
@ -20,10 +20,9 @@ Using Ocean Market is already a big improvement on the alternatives that are out
|
|||
|
||||
The tutorial covers:
|
||||
|
||||
- Forking and running Ocean Market locally
|
||||
- Customising your fork of Ocean market
|
||||
- Quick deployment of Ocean Market
|
||||
|
||||
* Forking and running Ocean Market locally
|
||||
* Customising your fork of Ocean market
|
||||
* Quick deployment of Ocean Market
|
||||
|
||||
## Preparation
|
||||
|
||||
|
|
@ -31,20 +30,14 @@ The tutorial covers:
|
|||
|
||||
If you’re completely unfamiliar with Ocean Market or web3 applications in general, you will benefit from reading these guides first:
|
||||
|
||||
- To use your clone of Ocean Market, you’ll need a [wallet](https://docs.oceanprotocol.com/tutorials/wallets/). We recommend [getting set up with metamask](https://docs.oceanprotocol.com/tutorials/metamask-setup/).
|
||||
|
||||
- You’ll also need some [Ocean tokens on a testnet](https://docs.oceanprotocol.com/tutorials/wallets-and-ocean-tokens/) to use your marketplace.
|
||||
|
||||
- When you have the testnet tokens, have a go at [publishing a data asset](https://docs.oceanprotocol.com/tutorials/marketplace-publish-data-asset/) on Ocean Market.
|
||||
|
||||
- Run through the process of [consuming a data asset](https://docs.oceanprotocol.com/tutorials/marketplace-consume-data-asset/) on Ocean Market.
|
||||
* To use your clone of Ocean Market, you’ll need a [wallet](https://docs.oceanprotocol.com/tutorials/wallets/). We recommend [getting set up with metamask](https://docs.oceanprotocol.com/tutorials/metamask-setup/).
|
||||
* You’ll also need some [Ocean tokens on a testnet](https://docs.oceanprotocol.com/tutorials/wallets-and-ocean-tokens/) to use your marketplace.
|
||||
* When you have the testnet tokens, have a go at [publishing a data asset](https://docs.oceanprotocol.com/tutorials/marketplace-publish-data-asset/) on Ocean Market.
|
||||
* Run through the process of [consuming a data asset](https://docs.oceanprotocol.com/tutorials/marketplace-consume-data-asset/) on Ocean Market.
|
||||
|
||||
**Required Prerequisites**
|
||||
|
||||
- Git. Instructions for installing Git can be found [here](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git).
|
||||
|
||||
- Node.js can be downloaded from [here](https://nodejs.org/en/download/) (we’re using version 16 in this guide)
|
||||
|
||||
- A decent code editor, such as [Visual Studio Code](https://code.visualstudio.com/).
|
||||
|
||||
- You’ll need a Github account to fork Ocean market via [Github](https://github.com/).
|
||||
* Git. Instructions for installing Git can be found [here](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git).
|
||||
* Node.js can be downloaded from [here](https://nodejs.org/en/download/) (we’re using version 16 in this guide)
|
||||
* A decent code editor, such as [Visual Studio Code](https://code.visualstudio.com/).
|
||||
* You’ll need a Github account to fork Ocean market via [Github](https://github.com/).
|
||||
|
|
|
|||
|
|
@ -2,11 +2,11 @@
|
|||
title: Deployment of Ocean Market
|
||||
order: 3
|
||||
hideLanguageSelector: true
|
||||
description: Step by step guide to a quick deployment of Ocean Market
|
||||
featuredImage: images/creatures/mantaray/mantaray-full@2x.png
|
||||
description: Step by step guide to a quick deployment of Ocean Market
|
||||
---
|
||||
|
||||
# 🔰 Quick deployment of Ocean Market
|
||||
# Deploying your market
|
||||
|
||||
All that’s left is for you to host your data marketplace and start sharing it with your future users.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,24 +2,20 @@
|
|||
title: Forking Ocean Market
|
||||
order: 1
|
||||
hideLanguageSelector: true
|
||||
description: Forking and running Ocean Market locally.
|
||||
featuredImage: images/creatures/mantaray/mantaray-full@2x.png
|
||||
description: Forking and running Ocean Market locally.
|
||||
---
|
||||
|
||||
# Forking and running Ocean Market locally
|
||||
# Forking Ocean Market
|
||||
|
||||
One of the best use cases for Ocean is running your own marketplace and monetizing your digital assets. With Ocean you can sell your data directly to your customers with no third party in-between, no need to speak to data with data brokers. Ocean makes this all super easy for you with some pretty cool tech under the hood. Furthermore, an Ocean powered market isn't just limited to selling data, you can use it for selling any type of digital asset!
|
||||
|
||||
Using Ocean Market is already a big improvement on the alternatives that are out there, but it gets even better. Ocean Market is completely open-source and made freely available under the Apache 2 license. This means that you can fork Ocean Market and set up your own data marketplace in just a few steps. This guide will walk you through the process, you’ll be surprised how easy it is. No prior blockchain knowledge is required!
|
||||
|
||||
|
||||
- Fork Ocean Market
|
||||
|
||||
- Clone the market locally
|
||||
|
||||
- Install the dependencies
|
||||
|
||||
- Run your Market fork for the first time
|
||||
* Fork Ocean Market
|
||||
* Clone the market locally
|
||||
* Install the dependencies
|
||||
* Run your Market fork for the first time
|
||||
|
||||
## Fork Ocean Market
|
||||
|
||||
|
|
@ -51,12 +47,12 @@ npm start
|
|||
|
||||
The above command will build the development bundle and run it locally.
|
||||
|
||||
|
||||
|
||||
|
||||
Great news - your marketplace has successfully been built and is now running locally. Let’s check it out! Open your browser and navigate to http://localhost:8000/. You’ll see that you have a full-on clone of Ocean Market running locally. Give it a go and test out publishing and consuming assets - everything works!
|
||||
|
||||
That’s all that’s required to get a clone of Ocean market working. The whole process is made simple because your clone can happily use all the smart contracts and backend components that are maintained by Ocean Protocol Foundation.
|
||||
|
||||
|
||||
|
||||
|
||||
So you’ve got a fully functioning marketplace at this point, which is pretty cool. But it doesn’t really look like your marketplace. Right now, it’s still just a clone of Ocean Market - the same branding, name, logo, etc. The next few steps focus on personalizing your marketplace.
|
||||
|
|
|
|||
|
|
@ -22,13 +22,13 @@ Click on **`Create`** button and choose **`Droplets`** options from dropdown.
|
|||
|
||||
#### Configure droplet
|
||||
|
||||
Select Ubuntu OS and choose a plan. The required CPU, Memory depends on the number of requests Aquarius is expected to serve. 
|
||||
Select Ubuntu OS and choose a plan. The required CPU, Memory depends on the number of requests Aquarius is expected to serve.
|
||||
|
||||
.png>)
|
||||
|
||||
Also, select the region where you want Aquarius to be hosted and a root password.
|
||||
|
||||
.png>)
|
||||
.png>)
|
||||
|
||||
.png>)
|
||||
|
||||
|
|
@ -58,8 +58,7 @@ sudo apt-get update
|
|||
sudo apt-get install docker-compose-plugin
|
||||
```
|
||||
|
||||
Now that, the server is ready with all the required dependencies are installed for hosting Ocean Components, follow the instructions given in Component specific guide. 
|
||||
Now that, the server is ready with all the required dependencies are installed for hosting Ocean Components, follow the instructions given in Component specific guide.
|
||||
|
||||
* [Deploying Marketplace](deploying-marketplace.md)
|
||||
* [ Deploying Aquarius ](deploying-aquarius.md)
|
||||
|
||||
* [Deploying Aquarius](deploying-aquarius.md)
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ Once someone has generated datatokens, they can be used in any ERC20 exchange, c
|
|||
|
||||
The marketplaces are decentralized (no single owner or controller), and non-custodial (only the data owner holds the keys for the datatokens).
|
||||
|
||||
Ocean Market supports fixed pricing or free pricing. For more detials on pricing schema refer [this guide](./asset-pricing.md).
|
||||
Ocean Market supports fixed pricing or free pricing. For more detials on pricing schema refer [this guide](asset-pricing.md).
|
||||
|
||||
Complementary to Ocean Market, Ocean has reference code to ease building **third-party data marketplaces**, such as for logistics ([dexFreight data marketplace](https://blog.oceanprotocol.com/dexfreight-ocean-protocol-partner-to-enable-transportation-logistics-companies-to-monetize-data-7aa839195ac)) or mobility ([Daimler](https://blog.oceanprotocol.com/ocean-protocol-delivers-proof-of-concept-for-daimler-ag-in-collaboration-with-daimler-south-east-564aa7d959ca)).
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ The DDO is stored on-chain as part of the NFT contract and stored in encrypted f
|
|||
|
||||
Here is the flow:
|
||||
|
||||
|
||||
.png>)
|
||||
|
||||
<details>
|
||||
|
||||
|
|
@ -309,6 +309,8 @@ An asset with a service of `type` `compute` has the following additional attribu
|
|||
| `boolean` | **✓** | If `true`, any passed raw text will be allowed to run. Useful for an algorithm drag & drop use case, but increases risk of data escape through malicious user input. Should be `false` by default in all implementations. |
|
||||
| Type | Required | Description |
|
||||
| `boolean` | **✓** | If `true`, any passed raw text will be allowed to run. Useful for an algorithm drag & drop use case, but increases risk of data escape through malicious user input. Should be `false` by default in all implementations. |
|
||||
| Type | Required | Description |
|
||||
| `boolean` | **✓** | If `true`, any passed raw text will be allowed to run. Useful for an algorithm drag & drop use case, but increases risk of data escape through malicious user input. Should be `false` by default in all implementations. |
|
||||
| <p><strong><code>allowNetworkAccess</code></strong></p><table><thead><tr><th>Type</th><th>Required</th><th>Description</th></tr></thead><tbody><tr><td><code>boolean</code></td><td><strong>✓</strong></td><td>If <code>true</code>, the algorithm job will have network access.</td></tr></tbody></table> | | |
|
||||
| Type | Required | Description |
|
||||
| `boolean` | **✓** | If `true`, the algorithm job will have network access. |
|
||||
|
|
@ -318,6 +320,8 @@ An asset with a service of `type` `compute` has the following additional attribu
|
|||
| `boolean` | **✓** | If `true`, the algorithm job will have network access. |
|
||||
| Type | Required | Description |
|
||||
| `boolean` | **✓** | If `true`, the algorithm job will have network access. |
|
||||
| Type | Required | Description |
|
||||
| `boolean` | **✓** | If `true`, the algorithm job will have network access. |
|
||||
| <p><strong><code>publisherTrustedAlgorithmPublishers</code></strong></p><table><thead><tr><th>Type</th><th>Required</th><th>Description</th></tr></thead><tbody><tr><td>Array of <code>string</code></td><td><strong>✓</strong></td><td>If not defined, then any published algorithm is allowed. If empty array, then no algorithm is allowed. If not empty any algo published by the defined publishers is allowed.</td></tr></tbody></table> | | |
|
||||
| Type | Required | Description |
|
||||
| Array of `string` | **✓** | If not defined, then any published algorithm is allowed. If empty array, then no algorithm is allowed. If not empty any algo published by the defined publishers is allowed. |
|
||||
|
|
@ -327,6 +331,8 @@ An asset with a service of `type` `compute` has the following additional attribu
|
|||
| Array of `string` | **✓** | If not defined, then any published algorithm is allowed. If empty array, then no algorithm is allowed. If not empty any algo published by the defined publishers is allowed. |
|
||||
| Type | Required | Description |
|
||||
| Array of `string` | **✓** | If not defined, then any published algorithm is allowed. If empty array, then no algorithm is allowed. If not empty any algo published by the defined publishers is allowed. |
|
||||
| Type | Required | Description |
|
||||
| Array of `string` | **✓** | If not defined, then any published algorithm is allowed. If empty array, then no algorithm is allowed. If not empty any algo published by the defined publishers is allowed. |
|
||||
| <p><strong><code>publisherTrustedAlgorithms</code></strong></p><table><thead><tr><th>Type</th><th>Required</th><th>Description</th></tr></thead><tbody><tr><td>Array of <code>publisherTrustedAlgorithms</code></td><td><strong>✓</strong></td><td>If not defined, then any published algorithm is allowed. If empty array, then no algorithm is allowed. Otherwise only the algorithms defined in the array are allowed. (see below).</td></tr></tbody></table> | | |
|
||||
| Type | Required | Description |
|
||||
| Array of `publisherTrustedAlgorithms` | **✓** | If not defined, then any published algorithm is allowed. If empty array, then no algorithm is allowed. Otherwise only the algorithms defined in the array are allowed. (see below). |
|
||||
|
|
@ -336,6 +342,8 @@ An asset with a service of `type` `compute` has the following additional attribu
|
|||
| Array of `publisherTrustedAlgorithms` | **✓** | If not defined, then any published algorithm is allowed. If empty array, then no algorithm is allowed. Otherwise only the algorithms defined in the array are allowed. (see below). |
|
||||
| Type | Required | Description |
|
||||
| Array of `publisherTrustedAlgorithms` | **✓** | If not defined, then any published algorithm is allowed. If empty array, then no algorithm is allowed. Otherwise only the algorithms defined in the array are allowed. (see below). |
|
||||
| Type | Required | Description |
|
||||
| Array of `publisherTrustedAlgorithms` | **✓** | If not defined, then any published algorithm is allowed. If empty array, then no algorithm is allowed. Otherwise only the algorithms defined in the array are allowed. (see below). |
|
||||
|
||||
The `publisherTrustedAlgorithms` is an array of objects with the following structure:
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ description: >-
|
|||
additional core components deployed to them.
|
||||
---
|
||||
|
||||
# Supported Networks
|
||||
# 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).
|
||||
|
||||
|
|
@ -55,7 +55,7 @@ Ocean is deployed to Polygon Mainnet, another production network. Polygon’s na
|
|||
|
||||
**Bridge**
|
||||
|
||||
Check our Polygon Bridge [guide](../building-with-ocean/polygon-bridge.md) to learn how you can deposit, withdraw and send tokens.
|
||||
Check our Polygon Bridge [guide](broken-reference) to learn how you can deposit, withdraw and send tokens.
|
||||
|
||||
### Binance Smart Chain
|
||||
|
||||
|
|
@ -81,7 +81,7 @@ If you don’t find BSC as a predefined network in your wallet, you can connect
|
|||
|
||||
**Bridge**
|
||||
|
||||
Check our BSC Bridge [guide](../building-with-ocean/bsc-bridge.md) to learn how you can deposit, withdraw and send tokens.
|
||||
Check our BSC Bridge [guide](broken-reference) to learn how you can deposit, withdraw and send tokens.
|
||||
|
||||
### Energy Web Chain
|
||||
|
||||
|
|
|
|||
|
|
@ -1,12 +1,12 @@
|
|||
---
|
||||
title: FAQs
|
||||
description: Frequently Asked Questions about Ocean Protocol
|
||||
order: 5
|
||||
hideLanguageSelector: true
|
||||
featuredImage: images/creatures/mantaray/mantaray-full@2x.png
|
||||
description: Frequently Asked Questions about Ocean Protocol
|
||||
---
|
||||
|
||||
# ❓ Frequently Asked Questions
|
||||
# FAQ
|
||||
|
||||
Have some questions about Ocean Protocol?
|
||||
|
||||
|
|
@ -15,14 +15,16 @@ Hopefully you'll find the answers here! If not then please don't hesitate to rea
|
|||
### General Questions
|
||||
|
||||
<details>
|
||||
<summary>What is a decentralized data marketplace?</summary>
|
||||
|
||||
<summary>What is a decentralized data marketplace?</summary>
|
||||
|
||||
A data marketplace allows providers to publish data and buyers to consume data. Unlike centralized data marketplaces, decentralized ones give users more control over their data, algorithms and analytics by minimizing custodianship and providing transparent and immutable records of every transaction. With features such as Compute-to-Data (C2D), data and algorithms can be ingested into secure Docker containers where escapes avoided, protecting both the data and algorithms.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>What is needed to use a decentralized marketplace?</summary>
|
||||
|
||||
<summary>What is needed to use a decentralized marketplace?</summary>
|
||||
|
||||
Users access decentralized marketplaces via Metamask. Metamask is an applet interface that manages unique IDs, generated and controlled fully by the user. These unique IDs (aka Ethereum address) are used to store digital assets such as cryptocurrency, datatokens, NFTs and other web3 native assets.
|
||||
|
||||
|
|
@ -33,49 +35,56 @@ Once a user has Metamask installed and an Ethereum address, they can register, c
|
|||
</details>
|
||||
|
||||
<details>
|
||||
<summary>How is Ocean different from other data marketplaces?</summary>
|
||||
|
||||
<summary>How is Ocean different from other data marketplaces?</summary>
|
||||
|
||||
Ocean Protocol is a decentralized data marketplace which gives users complete control of their data. The Ocean Protocol technology is built on smart contracts, decentralized computer scripts with no intermediary that are triggered by the users. The Ocean Market exposes the functionality of the smart contracts in a browser-friendly interface. Data providers and consumers can discover one another and transact in a peer-to-peer manner with the minimal amount of intermediary involvement.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>How do I price my data?</summary>
|
||||
|
||||
<summary>How do I price my data?</summary>
|
||||
|
||||
Ocean gives you two different options for pricing your data - fixed price or free. You need to decide what your dataset is worth and how you want to price it. You can change the price but you can’t change the price format (e.g. from fixed to free).
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>Is my data secure?</summary>
|
||||
|
||||
<summary>Is my data secure?</summary>
|
||||
|
||||
Yes. Ocean Protocol understands that some data is too sensitive to be shared — potentially due to GDPR or other reasons. For these types of datasets, we offer a unique service called compute-to-data. This enables you to monetise the dataset that sits behind a firewall without ever revealing the raw data to the consumer. For example, researchers and data scientists pay to run their algorithms on the data set and the computation is performed behind a firewall; all the researchers or data scientists receive is the results generated by their algorithm.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>Where is my data stored?</summary>
|
||||
|
||||
<summary>Where is my data stored?</summary>
|
||||
|
||||
Ocean does not provide data storage. Users have the choice to store their data on their own servers, cloud or decentralized storage. Users need only to provide a URL to the dataset, which is then encrypted as a means to protect the access to the dataset.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>How do I control who accesses my data?</summary>
|
||||
|
||||
<summary>How do I control who accesses my data?</summary>
|
||||
|
||||
Ocean provides tools for access control, fine grained permissions, passlisting and blocklisting addresses. Data and AI services can be shared under the conditions set by the owner of data. There is no central intermediary, which ensures no one can interfere with the transaction and both the publisher and user have transparency.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>Can I restrict who is able to access my dataset?</summary>
|
||||
|
||||
<summary>Can I restrict who is able to access my dataset?</summary>
|
||||
|
||||
Yes - Ocean has implemented fine grained permissions. This means that you can create allow and deny lists that restrict access from certain individuals or limit access to particular organizations.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>What is the reach of Ocean Market - how many data buyers can I sell to?</summary>
|
||||
|
||||
<summary>What is the reach of Ocean Market - how many data buyers can I sell to?</summary>
|
||||
|
||||
Hundreds of unique datasets are available that are sourced from private individuals, research institutions, commercial enterprises and government. Publishing data on Ocean offers data providers and algorithm owners an exciting new channel to connect with a rapidly growing community of Web3 enthusiasts and data science professionals around the world.
|
||||
|
||||
|
|
@ -84,35 +93,40 @@ Hundreds of unique datasets are available that are sourced from private individu
|
|||
### Technical Questions
|
||||
|
||||
<details>
|
||||
<summary>Why does Ocean Protocol use the Blockchain?</summary>
|
||||
|
||||
<summary>Why does Ocean Protocol use the Blockchain?</summary>
|
||||
|
||||
For both providers and consumers of data, blockchain is a superior substrate for building applications.Blockchain allows business logic to be instantiated in a network and triggered by the users, without intermediaries. This innovation promises lower transaction costs, higher security, more control, less errors and more transparency & auditability.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>The blockchain is public - does this mean that anyone can access my data?</summary>
|
||||
|
||||
<summary>The blockchain is public - does this mean that anyone can access my data?</summary>
|
||||
|
||||
No one is able to access data via the blockchain without purchasing access (with the datatoken) though the smart contract. Ocean smart contracts encrypt the URL to the dataset before it is published on the blockchain. This means that only the encrypted URL will be queryable in the public blockchain. Ocean technology facilitates data access to the consumer via a proxy (Ocean Provider) and the unencrypted url is never exposed.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>What is a smart contract and why is it relevant?</summary>
|
||||
|
||||
<summary>What is a smart contract and why is it relevant?</summary>
|
||||
|
||||
The blockchain can do more than just store information - it can also run code. A smart contract is an executable script that runs on the blockchain, with no intermediary and is fully transparent and auditable by anyone. In Ocean, smart contracts facilitate access to data and AI if the access conditions set out by the publisher are fulfilled.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>What is a datatoken?</summary>
|
||||
|
||||
<summary>What is a datatoken?</summary>
|
||||
|
||||
A datatoken is an access token to datasets and services published in the Ocean ecosystem. Datatokens can be purchased via the Ocean Market or on a decentralized crypto exchange. . If a consumer wishes to access a dataset, they must acquire the datatoken and then exchange the datatoken for access to the dataset.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>How do I acquire datatokens?</summary>
|
||||
|
||||
<summary>How do I acquire datatokens?</summary>
|
||||
|
||||
Datatokens can be acquired and traded in Ocean Market. There are several ways to acquire data tokens. Data publishers can acquire datatokens by publishing datasets and then receiving the generated datatokens.
|
||||
|
||||
|
|
@ -125,70 +139,80 @@ Datatokens can also be sent from anyone who holds a datatoken for a particular a
|
|||
### Data Selling Questions
|
||||
|
||||
<details>
|
||||
<summary>How are organizations leveraging data sharing?</summary>
|
||||
|
||||
<summary>How are organizations leveraging data sharing?</summary>
|
||||
|
||||
For the most part organizations are leveraging data sharing to benefit from data monetization, however increasingly organizations are also sharing data in order to boost their progress on sustainability goals. For example, data aggregated from vehicles can not only bring new revenue streams to automotive firms but can also be used to battle pollution.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>Does it pay to become a marketplace operator?</summary>
|
||||
|
||||
<summary>Does it pay to become a marketplace operator?</summary>
|
||||
|
||||
Yes. Marketplace operators benefit from earning commission on marketplace transactions related to data consumption. Ocean Market is primarily focussed on monetising data however it is also designed to handle the sale of any digital asset or service. As a result the total addressable market goes way beyond revenues from just selling data. Operating costs for an Ocean-powered marketplace are moderate and the base code is open source and available free of charge under the Apache 2 license.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>Why Publish?</summary>
|
||||
|
||||
<summary>Why Publish?</summary>
|
||||
|
||||
Publishing data, algorithms and other digital assets and services on an Ocean-powered marketplace offers numerous opportunities to earn on the future revenue streams connected to that data as well as build lucrative ecosystem that add value to the published asset. It also allows for the discovery and insights into new use cases and applications of the published asset.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>What about the price fluctuation of Ocean?</summary>
|
||||
|
||||
<summary>What about the price fluctuation of Ocean?</summary>
|
||||
|
||||
Price fluctuation is mitigated through the use of the Ocean backed stable coin H2O.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>Who pays for gas fees?</summary>
|
||||
|
||||
<summary>Who pays for gas fees?</summary>
|
||||
|
||||
Gas fees for marketplace transactions are paid by the user initiating the transaction (for publishing, consuming, etc).
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>Where do the docker containers run?</summary>
|
||||
|
||||
<summary>Where do the docker containers run?</summary>
|
||||
|
||||
Dockers containers can run anywhere. Ocean Market use a docker run by the Ocean Protocol Foundation OPF); limit: 1 CPU limit / 60 seconds max. NOTE: This means OPF technically has access to data. In the case of a forked Ocean-powered marketplace the owner of marketplace must set up computation environment. If individual users of the marketplace are concerned with security they should be prepared to host both the data and provide compute-to-data services on premise.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>Who pays for the computation?</summary>
|
||||
|
||||
<summary>Who pays for the computation?</summary>
|
||||
|
||||
The marketplace owner.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>What cryptocurrency do I need for transactions?</summary>
|
||||
|
||||
<summary>What cryptocurrency do I need for transactions?</summary>
|
||||
|
||||
The type if cryptocurrencies needed for transactions on the marketplace depends on which network(s) the marketplace is running (Ethereum, Polygon, EWT, BSC, Moonriver, etc.). Regardless of network, users will need to have Ocean tokens as well as the corresponding network token, which is used to pay for gas.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>Can I use the off the shelf CSS available in the repo?</summary>
|
||||
|
||||
<summary>Can I use the off the shelf CSS available in the repo?</summary>
|
||||
|
||||
Marketplace name, logo and typeface must be changed by the client. Slight modification would be enough for compliance. For more information consult the READ ME file on GitHub. https://github.com/oceanprotocol/market#-forking
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>What’s to come with Ocean this year?</summary>
|
||||
|
||||
<summary>What’s to come with Ocean this year?</summary>
|
||||
|
||||
Checkout our [roadmap](https://oceanprotocol.com/technology/roadmap) to see what's we are currently working on. If you are interested in tracking our progress towards these goals then take a look at our [github](https://github.com/oceanprotocol/).
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@
|
|||
* [Ocean Market](https://market.oceanprotocol.com/) enables publishers to monetize their data and/or algorithms through blockchain technology.
|
||||
* Consumers can purchase access to data, algorithms, compute services.
|
||||
|
||||
|
||||
|
||||
|
||||
The following guides will help you get started with buying and selling data:
|
||||
|
||||
|
|
@ -18,3 +18,7 @@ If you are new to web3 and blockchain technologies then we suggest you first rea
|
|||
* [Wallet Basics](building-with-ocean/wallets.md)
|
||||
* [Set Up MetaMask Wallet](orientation/metamask-setup.md)
|
||||
* [Manage Your OCEAN Tokens](building-with-ocean/wallets-and-ocean-tokens.md)
|
||||
|
||||
### Removing Liquidity
|
||||
|
||||
The AMM pools, and dynamic pricing schema are no longer available on the Ocean Market. Refer [this page](remove-liquidity-using-etherscan.md) on removing liquidity from the pool using Etherscan.
|
||||
|
|
|
|||
|
|
@ -0,0 +1,41 @@
|
|||
# Liquidity Pools \[deprecated]
|
||||
|
||||
In previous versions of Ocean liquidity pools and dynamic pricing were supported. These features have been deprecated and we now advise everyone to remove their liquidity from the remaining pools. It is no longer possible to do this via Ocean Market, so please follow this guide to remove your liquidity via etherscan.
|
||||
|
||||
## Remove liquidity using Etherscan
|
||||
|
||||
### Get your balance of pool share tokens
|
||||
|
||||
1. Go to the pool's Etherscan/Polygonscan page. You can find it by inspecting your transactions on your account's Etherscan page under _Erc20 Token Txns_.
|
||||
2. Click _View All_ and look for Ocean Pool Token (OPT) transfers. Those transactions always come from the pool contract, which you can click on.
|
||||
3. On the pool contract page, go to _Contract_ -> _Read Contract_.
|
||||
|
||||
.png>)
|
||||
|
||||
4\. Go to field `20. balanceOf` and insert your ETH address. This will retrieve your pool share token balance in wei.
|
||||
|
||||
|
||||
|
||||
5\. Copy this number as later you will use it as the `poolAmountIn` parameter.
|
||||
|
||||
6\. Go to field `55. totalSupply` to get the total amount of pool shares, in wei.
|
||||
|
||||
|
||||
|
||||
7\. Divide the number by 2 to get the maximum of pool shares you can send in one pool exit transaction. If your number retrieved in former step is bigger, you have to send multiple transactions.
|
||||
|
||||
8\. Go to _Contract_ -> _Write Contract_ and connect your wallet. Be sure to have your wallet connected to network of the pool.
|
||||
|
||||
|
||||
|
||||
9\. Go to the field `5. exitswapPoolAmountIn`
|
||||
|
||||
* For `poolAmountIn` add your pool shares in wei
|
||||
* For `minAmountOut` use anything, like `1`
|
||||
* Hit _Write_
|
||||
|
||||
|
||||
|
||||
10\. Confirm transaction in Metamask
|
||||
|
||||
|
||||
Loading…
Reference in New Issue