GITBOOK-263: change request with no subject merged in GitBook
This commit is contained in:
Veronica Manuel
gitbook-bot
parent
ab5c3609d6
commit
6d17a61659
Binary file not shown.
|
After Width: | Height: | Size: 116 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 49 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 91 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 60 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 45 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 74 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 35 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 1.4 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 77 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 77 KiB |
|
|
@ -27,7 +27,7 @@
|
|||
* [How to Data Farm](user-guides/how-to-data-farm.md)
|
||||
* [Claim OCEAN Rewards](user-guides/claim-ocean-rewards.md)
|
||||
* [Liquidity Pools \[deprecated\]](user-guides/remove-liquidity-using-etherscan.md)
|
||||
* [👨💻 Developers](developers/README.md)
|
||||
* [👨💻 👨💻 Developers](developers/README.md)
|
||||
* [Architecture Overview](developers/architecture.md)
|
||||
* [Data NFTs and Datatokens](developers/datanft-and-datatoken.md)
|
||||
* [Roles](developers/roles.md)
|
||||
|
|
|
|||
|
|
@ -10,9 +10,7 @@ A method for retrieving all information about the asset using a unique identifie
|
|||
* **Purpose**: This endpoint is used to fetch the Decentralized Document (DDO) of a particular asset. A DDO is a detailed information package about a specific asset, including its ID, metadata, and other necessary data.
|
||||
* **Parameters**: The `<did>` in the URL is a placeholder for the DID, a unique identifier for the asset you want to retrieve the DDO for.
|
||||
|
||||
| Name | Description | Type | Within | Required |
|
||||
| ----- | ---------------- | ------ | ------ | -------- |
|
||||
| `did` | DID of the asset | string | path | true |
|
||||
<table><thead><tr><th width="100">Name</th><th>Description</th><th width="100">Type</th><th width="100">Within</th><th>Required</th></tr></thead><tbody><tr><td><code>did</code></td><td>DID of the asset</td><td>string</td><td>path</td><td>true</td></tr></tbody></table>
|
||||
|
||||
Here are some typical responses you might receive from the API:
|
||||
|
||||
|
|
@ -53,9 +51,7 @@ Here are some typical responses you might receive from the API:
|
|||
|
||||
#### Parameters
|
||||
|
||||
| Name | Description | Type | Within | Required |
|
||||
| ----- | ---------------- | ------ | ------ | -------- |
|
||||
| `did` | DID of the asset | string | path | true |
|
||||
<table><thead><tr><th width="100">Name</th><th>Description</th><th width="100">Type</th><th width="100">Within</th><th>Required</th></tr></thead><tbody><tr><td><code>did</code></td><td>DID of the asset</td><td>string</td><td>path</td><td>true</td></tr></tbody></table>
|
||||
|
||||
#### Curl Example
|
||||
|
||||
|
|
@ -92,9 +88,7 @@ Here are some typical responses you might receive from the API:
|
|||
|
||||
#### Parameters
|
||||
|
||||
| Name | Description | Type | Within | Required |
|
||||
| --------- | ------------------ | ---- | ------ | -------- |
|
||||
| `didList` | list of asset DIDs | list | body | true |
|
||||
<table><thead><tr><th>Name</th><th>Description</th><th width="100">Type</th><th width="100">Within</th><th>Required</th></tr></thead><tbody><tr><td><code>didList</code></td><td>list of asset DIDs</td><td>list</td><td>body</td><td>true</td></tr></tbody></table>
|
||||
|
||||
#### Curl Example
|
||||
|
||||
|
|
@ -241,10 +235,7 @@ Used to manually initiate the process of DDO caching based on a transaction ID.
|
|||
* **Purpose**: This endpoint is used to manually trigger the caching process of a DDO (Decentralized Identifier Document). This process is initiated based on a specific transaction ID, which should include either MetadataCreated or MetadataUpdated events. This can be particularly useful in situations where immediate caching of metadata changes is required.
|
||||
* **Parameters**: The parameters for this endpoint are provided in the body of the POST request as a valid JSON object. This includes the transaction ID and log index that is associated with the metadata event.
|
||||
|
||||
| Name | Description | Type | Within | Required |
|
||||
| --------------- | ------------------------------------ | ------ | ------ | -------- |
|
||||
| `transactionId` | DID of the asset | string | path | true |
|
||||
| `logIndex` | custom log index for the transaction | int | path | false |
|
||||
<table><thead><tr><th>Name</th><th>Description</th><th width="100">Type</th><th width="100">Within</th><th>Required</th></tr></thead><tbody><tr><td><code>transactionId</code></td><td>DID of the asset</td><td>string</td><td>path</td><td>true</td></tr><tr><td><code>logIndex</code></td><td>custom log index for the transaction</td><td>int</td><td>path</td><td>false</td></tr></tbody></table>
|
||||
|
||||
Here are some typical responses you might receive from the API:
|
||||
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ Ocean provides convenient methods to list ERC20 datatokens for sale, with fixed-
|
|||
|
||||
### High-Level Behavior
|
||||
|
||||
|
||||
.png>)
|
||||
|
||||
Here's an example.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ description: >-
|
|||
NFTs
|
||||
---
|
||||
|
||||
# Get data NFT Information
|
||||
# Get data NFT information
|
||||
|
||||
Now that you are familiar with the process of retrieving a list of data NFTs 😎, let's explore how to obtain more specific details about a particular NFT through querying. By utilizing the knowledge you have gained, you can customize your GraphQL query to include additional parameters such as the NFT's metadata, creator information, template, or any other relevant data points. This will enable you to delve deeper into the intricacies of a specific NFT and gain a comprehensive understanding of its attributes. With this newfound capability, you can unlock valuable insights and make informed decisions based on the specific details retrieved. So, let's dive into the fascinating world of querying and unravel the unique characteristics of individual data NFTs.
|
||||
|
||||
|
|
@ -12,7 +12,7 @@ Now that you are familiar with the process of retrieving a list of data NFTs
|
|||
|
||||
The result of the following GraphQL query returns the information about a particular data NFT. In this example, `0x1c161d721e6d99f58d47f709cdc77025056c544c`.
|
||||
|
||||
_PS: In this example, the query is executed on the Ocean subgraph deployed on the mainnet. If you want to change the network, please refer to_ [_this table_](../ocean-subgraph/#ocean-subgraph-deployments)_._
|
||||
_PS: In this example, the query is executed on the Ocean subgraph deployed on the mainnet. If you want to change the network, please refer to_ [_this table_](broken-reference)_._
|
||||
|
||||
{% tabs %}
|
||||
{% tab title="Javascript" %}
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ To fetch detailed information about a specific datatoken, you can utilize the po
|
|||
|
||||
The result of the following GraphQL query returns the information about a particular datatoken. Here, `0x122d10d543bc600967b4db0f45f80cb1ddee43eb` is the address of the datatoken.
|
||||
|
||||
_PS: In this example, the query is executed on the Ocean subgraph deployed on the mainnet. If you want to change the network, please refer to_ [_this table_](../ocean-subgraph/#ocean-subgraph-deployments)_._
|
||||
_PS: In this example, the query is executed on the Ocean subgraph deployed on the mainnet. If you want to change the network, please refer to_ [_this table_](broken-reference)_._
|
||||
|
||||
{% tabs %}
|
||||
{% tab title="Javascript" %}
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ There are several options available to see this query in action. Below, you will
|
|||
2. Execute the query in Python by following the code snippet.
|
||||
3. Execute the query in JavaScript by clicking on the "Run" button of the Javascript tab.
|
||||
|
||||
_PS: In these examples, the query is executed on the Ocean subgraph deployed on the mainnet. If you want to change the network, please refer to_ [_this table_](../ocean-subgraph/#ocean-subgraph-deployments)_._
|
||||
_PS: In these examples, the query is executed on the Ocean subgraph deployed on the mainnet. If you want to change the network, please refer to_ [_this table_](broken-reference)_._
|
||||
|
||||
{% tabs %}
|
||||
{% tab title="Javascript" %}
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ With your newfound knowledge of fetching data NFTs and retrieving the associated
|
|||
|
||||
|
||||
|
||||
_PS: In this example, the query is executed on the Ocean subgraph deployed on the mainnet. If you want to change the network, please refer to_ [_this table_](../ocean-subgraph/#ocean-subgraph-deployments)_._
|
||||
_PS: In this example, the query is executed on the Ocean subgraph deployed on the mainnet. If you want to change the network, please refer to_ [_this table_](broken-reference)_._
|
||||
|
||||
{% tabs %}
|
||||
{% tab title="Javascript" %}
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ Having gained knowledge about fetching lists of data NFTs and datatokens and ext
|
|||
|
||||
|
||||
|
||||
_PS: In this example, the query is executed on the Ocean subgraph deployed on the mainnet. If you want to change the network, please refer to_ [_this table_](../ocean-subgraph/#ocean-subgraph-deployments)_._
|
||||
_PS: In this example, the query is executed on the Ocean subgraph deployed on the mainnet. If you want to change the network, please refer to_ [_this table_](broken-reference)_._
|
||||
|
||||
{% tabs %}
|
||||
{% tab title="Javascript" %}
|
||||
|
|
|
|||
|
|
@ -13,19 +13,13 @@ In each network, whether it's the Ethereum mainnet, a testnet, or the Polygon/Ma
|
|||
|
||||
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.
|
||||
|
||||
| Gas Token | Mainnet ETH (Native token) |
|
||||
| ----------- | ------------------------------------------------------------------------------------------------------------------- |
|
||||
| OCEAN Token | [0x967da4048cD07aB37855c090aAF366e4ce1b9F48](https://etherscan.io/token/0x967da4048cD07aB37855c090aAF366e4ce1b9F48) |
|
||||
| Explorer | [https://etherscan.io](https://etherscan.io) |
|
||||
<table><thead><tr><th width="186">Gas Token</th><th>Mainnet ETH (Native token)</th></tr></thead><tbody><tr><td>OCEAN Token</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>
|
||||
|
||||
### Polygon Mainnet
|
||||
|
||||
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.
|
||||
|
||||
| Gas Token | Matic(Native token) |
|
||||
| --------- | ---------------------------------------------------------------------------------------------------------------------- |
|
||||
| OCEAN | [0x282d8efCe846A88B159800bd4130ad77443Fa1A1](https://polygonscan.com/token/0x282d8efce846a88b159800bd4130ad77443fa1a1) |
|
||||
| Explorer | [https://polygonscan.com](https://polygonscan.com) |
|
||||
<table><thead><tr><th width="198">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>
|
||||
|
||||
**Bridge**
|
||||
|
||||
|
|
@ -35,10 +29,7 @@ Check our Polygon Bridge [guide](bridges.md) to learn how you can deposit, withd
|
|||
|
||||
Ocean Protocol is also deployed to Binance Smart Chain (BSC), which is another production network. The native token of the Binance Smart Chain is BNB, which is the token of the Binance exchange. If Binance 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 Binance Smart Chain.
|
||||
|
||||
| Gas Token | BSC BNB(Native token) |
|
||||
| --------- | ------------------------------------------------------------------------------------------------------------------ |
|
||||
| OCEAN | [0xdce07662ca8ebc241316a15b611c89711414dd1a](https://bscscan.com/token/0xdce07662ca8ebc241316a15b611c89711414dd1a) |
|
||||
| Explorer | [https://bscscan.com/](https://bscscan.com/) |
|
||||
<table><thead><tr><th width="205">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**
|
||||
|
||||
|
|
@ -48,10 +39,7 @@ Check our BSC Bridge [guide](bridges.md#binance-smart-chain-bsc-bridge) to learn
|
|||
|
||||
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).
|
||||
|
||||
| Gas Token | Energy Web Chain EWT(Native token) |
|
||||
| --------- | ----------------------------------------------------------------------------------------------------------------------------- |
|
||||
| OCEAN | [0x593122aae80a6fc3183b2ac0c4ab3336debee528](https://explorer.energyweb.org/token/0x593122aae80a6fc3183b2ac0c4ab3336debee528) |
|
||||
| Explorer | [https://explorer.energyweb.org/](https://explorer.energyweb.org/) |
|
||||
<table><thead><tr><th width="206">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**
|
||||
|
||||
|
|
@ -61,10 +49,7 @@ To bridge assets between Energy Web Chain and Ethereum mainnet, you can use [thi
|
|||
|
||||
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).
|
||||
|
||||
| Gas Token | Moonriver MOVR(Native token) |
|
||||
| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| OCEAN | [0x99C409E5f62E4bd2AC142f17caFb6810B8F0BAAE](https://blockscout.moonriver.moonbeam.network/token/0x99C409E5f62E4bd2AC142f17caFb6810B8F0BAAE/token-transfers) |
|
||||
| Explorer | [https://blockscout.moonriver.moonbeam.network](https://blockscout.moonriver.moonbeam.network) |
|
||||
<table><thead><tr><th width="206">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**
|
||||
|
||||
|
|
@ -74,12 +59,7 @@ To bridge assets between Moonriver and Ethereum mainnet, you can use [this](http
|
|||
|
||||
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.
|
||||
|
||||
| Gas Token | Görli ETH(Native token) |
|
||||
| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Görli ETH | [Faucet](https://goerlifaucet.com/). You may find others by [searching](https://www.google.com/search?q=goerli+ether+faucet%5C\&oq=goerli+ether+faucet). |
|
||||
| OCEAN | [0xCfDdA22C9837aE76E0faA845354f33C62E03653a](https://goerli.etherscan.io/address/0xcfdda22c9837ae76e0faa845354f33c62e03653a) |
|
||||
| Görli OCEAN | [Faucet](https://faucet.goerli.oceanprotocol.com) |
|
||||
| Explorer | [https://blockscout.moonriver.moonbeam.network](https://blockscout.moonriver.moonbeam.network) |
|
||||
<table><thead><tr><th width="207">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>OCEAN</td><td><a href="https://goerli.etherscan.io/address/0xcfdda22c9837ae76e0faa845354f33c62e03653a">0xCfDdA22C9837aE76E0faA845354f33C62E03653a</a></td></tr><tr><td>Görli OCEAN</td><td><a href="https://faucet.goerli.oceanprotocol.com">Faucet</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
|
||||
|
||||
|
|
@ -87,10 +67,5 @@ Ocean Protocol is deployed on the Mumbai test network Matic / Polygon, which is
|
|||
|
||||
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/).
|
||||
|
||||
| Gas Token | Mumbai MATIC(Native token) |
|
||||
| ------------ | ----------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Mumbai MATIC | [Faucet](https://faucet.matic.network/). You may find others by [searching](https://www.google.com/search?q=mumbai+faucet). |
|
||||
| OCEAN | [0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8](https://mumbai.polygonscan.com/token/0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8) |
|
||||
| Mumbai OCEAN | [Faucet](https://faucet.mumbai.oceanprotocol.com/) |
|
||||
| Explorer | [https://mumbai.polygonscan.com](https://mumbai.polygonscan.com) |
|
||||
<table><thead><tr><th width="216">Gas Token</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>OCEAN</td><td><a href="https://mumbai.polygonscan.com/token/0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8">0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8</a></td></tr><tr><td>Mumbai OCEAN</td><td><a href="https://faucet.mumbai.oceanprotocol.com/">Faucet</a></td></tr><tr><td>Explorer</td><td><a href="https://mumbai.polygonscan.com">https://mumbai.polygonscan.com</a></td></tr></tbody></table>
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ If you don't see any Ocean Tokens in your crypto wallet software (e.g. MetaMask
|
|||
|
||||
Almost all ERC-20 wallets require these values for adding a custom token:
|
||||
|
||||
<table data-full-width="true"><thead><tr><th>Network name</th><th>Contract Address</th><th>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>BSC</strong><br><strong>Binance Smart Chain</strong></td><td>0xdce07662ca8ebc241316a15b611c89711414dd1a</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></tbody></table>
|
||||
<table data-full-width="true"><thead><tr><th width="160">Network name</th><th width="446">Contract Address</th><th width="106">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>BSC</strong><br><strong>Binance Smart Chain</strong></td><td>0xdce07662ca8ebc241316a15b611c89711414dd1a</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></tbody></table>
|
||||
|
||||
The [OCEAN Token page](https://oceanprotocol.com/token) at oceanprotocol.com has further details.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ description: Fundamental knowledge of using ERC-20 crypto wallets.
|
|||
|
||||
Ocean Protocol users require an ERC-20 compatible wallet to manage their OCEAN and ETH tokens. In this guide, we will provide some recommendations for different wallet options.
|
||||
|
||||
<figure><img src="../.gitbook/assets/gif/whats-a-wallet.gif" alt=""><figcaption></figcaption></figure>
|
||||
<figure><img src="../.gitbook/assets/gif/whats-a-wallet (1).gif" alt=""><figcaption></figcaption></figure>
|
||||
|
||||
### What is a wallet?
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ Select Ubuntu OS and choose a plan. The required CPU, Memory depends on the numb
|
|||
|
||||
Also, select the region where you want Aquarius to be hosted and a root password.
|
||||
|
||||
.png>)
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,7 @@
|
|||
---
|
||||
description: User guides
|
||||
description: >-
|
||||
The definitive guides on how to do almost anything you want with Ocean
|
||||
Protocol tech!
|
||||
cover: ../.gitbook/assets/cover/user_guides.png
|
||||
coverY: 0
|
||||
---
|
||||
|
|
|
|||
|
|
@ -18,41 +18,41 @@ Create an account on [Azure](https://azure.microsoft.com/en-us/). Users might al
|
|||
|
||||
Go to the Azure portal: https://portal.azure.com/#home and select `Storage accounts` as shown below.
|
||||
|
||||
|
||||
.png>)
|
||||
|
||||
**Create a new storage account**
|
||||
|
||||
.png>)
|
||||
|
||||
|
||||
**Fill in the details**
|
||||
|
||||
|
||||
.png>)
|
||||
|
||||
**Storage account created**
|
||||
|
||||
.png>)
|
||||
|
||||
|
||||
**Step 2 - Create a blob container**
|
||||
|
||||
|
||||
.png>)
|
||||
|
||||
**Step 3 - Upload a file**
|
||||
|
||||
.png>)
|
||||
|
||||
|
||||
**Step 4 - Share the file**
|
||||
|
||||
**Select the file to be published and click Generate SAS**
|
||||
|
||||
|
||||
.png>)
|
||||
|
||||
**Configure the SAS details and click `Generate SAS token and URL`**
|
||||
|
||||
.png>)
|
||||
|
||||
|
||||
**Copy the generated link**
|
||||
|
||||
.png>)
|
||||
|
||||
|
||||
**Step 5 - Publish the asset using the generated link**
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ description: How to publish a data NFT with C2D configurations
|
|||
|
||||
# Publish a C2D Data NFT
|
||||
|
||||
<figure><img src="../../.gitbook/assets/talk-data-to-me.gif" alt="" width="375"><figcaption></figcaption></figure>
|
||||
<figure><img src="../../.gitbook/assets/gif/talk-data-to-me.gif" alt="" width="375"><figcaption></figcaption></figure>
|
||||
|
||||
#### Step 1 - Navigate to the Ocean Market
|
||||
|
||||
|
|
@ -78,7 +78,7 @@ description: How to publish a data NFT with C2D configurations
|
|||
|
||||
#### Congratulations! You have fully finished the C2D flow. Check your work by verifying that your algorithm appears on the data NFT's page, like in the following example:
|
||||
|
||||
<figure><img src="../../.gitbook/assets/c2d/double-check-work (1).png" alt="" width="375"><figcaption><p>Your algorithm should appear now on the data NFT's page!</p></figcaption></figure>
|
||||
<figure><img src="../../.gitbook/assets/c2d/double-check-work.png" alt="" width="375"><figcaption><p>Your algorithm should appear now on the data NFT's page!</p></figcaption></figure>
|
||||
|
||||
If you would like to run the compute job, then simply click the radio button to the left of the algorithm's name and click Buy Compute Job.
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ Liquidity pools and dynamic pricing used to be supported in previous versions of
|
|||
|
||||
4\. Go to field `20. balanceOf` and insert your ETH address. This will retrieve your pool share token balance in wei.
|
||||
|
||||
<figure><img src="../.gitbook/assets/liquidity/remove-liquidity-2 (1).png" alt=""><figcaption><p>Balance Of</p></figcaption></figure>
|
||||
<figure><img src="../.gitbook/assets/liquidity/remove-liquidity-2 (1) (1).png" alt=""><figcaption><p>Balance Of</p></figcaption></figure>
|
||||
|
||||
5\. Copy this number as later you will use it as the `poolAmountIn` parameter.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue