diff --git a/.gitbook/assets/ethereum.png b/.gitbook/assets/ethereum.png new file mode 100644 index 00000000..644467ea Binary files /dev/null and b/.gitbook/assets/ethereum.png differ diff --git a/README.md b/README.md index 4cf6c80f..02f655b0 100644 --- a/README.md +++ b/README.md @@ -5,6 +5,6 @@ coverY: 0 layout: landing --- -# 🌊 Welcome +# 👋 Welcome
discover.mdLearn about Ocean Protocol's powerful data sharing capabilities and its potential to transform the way data is shared and monetized.discover.mdocean.png
tutorialsGet access to a wealth of tutorials and resources to help you get started with Ocean Protocol. Learn how to create and publish data assets, build data marketplaces, and more. Whether you're a beginner or an experienced user, there's something for everyone.tutorialstutorials.png
rewardsDiscover ways to earn rewards for contributing to the Ocean Protocol ecosystem. Explore bounty programs, grants, and other initiatives that can help you make an impact and earn recognition for your contributions.rewardsrewards.png
developersWhether you're building a dApp or integrating with the ecosystem, you'll find plenty of APIs, libraries, and other tools to help you get the job done.developersdevelopers.png
infrastructureLearn how to deploy your own components on the Ocean Protocol network. Discover how the platform leverages blockchain technology, decentralized storage, and other cutting-edge tools to enable secure and scalable data sharing.infrastructurebuilding-blocks.png
contributing.mdLearn how you can contribute to the growth and development of Ocean Protocol. Whether you're interested in community initiatives, open-source projects, or other opportunities, there are many ways to get involved and make a difference.contributing.mdcontribute.png
diff --git a/SUMMARY.md b/SUMMARY.md index 9a7924a5..6336f47e 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -2,10 +2,10 @@ * [👋 Welcome](README.md) * [🌊 Discover](discover/discover.md) + * [Networks](discover/networks.md) * [Wallet Basics](discover/wallets.md) * [Set Up MetaMask Wallet](discover/metamask-setup.md) * [Manage Your OCEAN Tokens](discover/wallets-and-ocean-tokens.md) - * [Networks](discover/networks.md) * [Bridges](discover/bridges.md) * [FAQ](discover/faq.md) * [📚 Tutorials](tutorials/README.md) @@ -50,6 +50,7 @@ * [C2D - User defined parameters](developers/core-concepts/user-defined-parameters.md) * [Aquarius REST API](developers/aquarius-rest-api.md) * [Provider REST API](developers/provider-rest-api.md) + * [Subgraph](developers/subgraph.md) * [🔨 Infrastructure](infrastructure/README.md) * [Setup a Server](infrastructure/setup-server.md) * [Deploying Marketplace](infrastructure/deploying-marketplace.md) diff --git a/developers/aquarius-rest-api.md b/developers/aquarius-rest-api.md index 6696b832..cee6a6cc 100644 --- a/developers/aquarius-rest-api.md +++ b/developers/aquarius-rest-api.md @@ -1,5 +1,7 @@ # Aquarius REST API +The universal Aquarius Endpoint is [`https://v4.aquarius.oceanprotocol.com`](https://v4.aquarius.oceanprotocol.com). + ## Assets ### **Get** `/api/aquarius/assets/ddo/` diff --git a/developers/provider-rest-api.md b/developers/provider-rest-api.md index 22178f1a..3c10391c 100644 --- a/developers/provider-rest-api.md +++ b/developers/provider-rest-api.md @@ -1,15 +1,15 @@ # Provider REST API +[https://v4.provider.oceanprotocol.com](https://v4.provider.oceanprotocol.com) + ## Ocean Provider Endpoints Specification This document specifies the endpoints for Ocean Provider to be implemented by the core developers. -If you want to see the provider URLs for our supported networks, kindly -check for `Provider` component on -this [page](https://docs.oceanprotocol.com/core-concepts/networks). +If you want to see the provider URLs for our supported networks, kindly check for `Provider` component on this [page](https://docs.oceanprotocol.com/core-concepts/networks). + +For inspecting the errors received from `Provider` and their reasons, please revise this [document](https://github.com/oceanprotocol/provider/blob/main/ocean\_provider/routes/README.md). -For inspecting the errors received from `Provider` and their reasons, please revise this -[document](https://github.com/oceanprotocol/provider/blob/main/ocean_provider/routes/README.md). ### nonce endpoint #### GET /api/services/nonce @@ -20,10 +20,7 @@ Parameters userAddress: String object containing a user's ethereum address ``` -Returns: Json object containing the last-used nonce value. -The nonce endpoint is just informative, use the current UTC timestamp as a nonce, -where required in other endpoints. - +Returns: Json object containing the last-used nonce value. The nonce endpoint is just informative, use the current UTC timestamp as a nonce, where required in other endpoints. Example: @@ -111,16 +108,17 @@ Retrieves Content-Type and Content-Length from the given URL or asset. Parameters For published assets: + ``` { did: String, DID of the dataset serviceId: String, ID of the service } ``` + For file objects,see https://docs.oceanprotocol.com/core-concepts/did-ddo#files -If checksum is requests, file size should be lower < MAX_CHECKSUM_LENGTH (see Provider ENVs) -If file is larger, checksum WILL NOT be computed. +If checksum is requests, file size should be lower < MAX\_CHECKSUM\_LENGTH (see Provider ENVs) If file is larger, checksum WILL NOT be computed. Returns: Json document file info object @@ -247,7 +245,6 @@ Response: } ``` - ### Compute endpoints All compute endpoints respond with an Array of status objects, each object describing a compute job info. @@ -559,13 +556,9 @@ Response: ### Authentication endpoints -Provider offers an alternative to signing each request, by allowing users to generate auth tokens. -The generated auth token can be used until its expiration in all supported requests. -Simply omit the signature parameter and add the AuthToken request header based on a created token. +Provider offers an alternative to signing each request, by allowing users to generate auth tokens. The generated auth token can be used until its expiration in all supported requests. Simply omit the signature parameter and add the AuthToken request header based on a created token. -Please note that if a signature parameter exists, it will take precedence over the AuthToken headers. -All routes that support a signature parameter support the replacement, with the exception of auth-related ones -(createAuthToken and deleteAuthToken need to be signed). +Please note that if a signature parameter exists, it will take precedence over the AuthToken headers. All routes that support a signature parameter support the replacement, with the exception of auth-related ones (createAuthToken and deleteAuthToken need to be signed). #### GET /api/services/createAuthToken @@ -582,14 +575,14 @@ signature: String object containg user signature (signed message) expiration: valid future UTC timestamp (required) ``` -Returns: -Created auth token. +Returns: Created auth token. Example: ``` GET /api/services/createAuthToken?address=&&nonce=&&expiration=&signature= ``` + Inside the angular brackets, the user should provide the valid values for the request. Response: @@ -598,7 +591,6 @@ Response: {"token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJleHAiOjE2NjAwNTMxMjksImFkZHJlc3MiOiIweEE3OGRlYjJGYTc5NDYzOTQ1QzI0Nzk5MTA3NUUyYTBlOThCYTdBMDkifQ.QaRqYeSYxZpnFayzPmUkj8TORHHJ_vRY-GL88ZBFM0o"} ``` - #### DELETE /api/services/deleteAuthToken Allows the user to delete an existing auth token before it naturally expires. @@ -614,15 +606,14 @@ signature: String object containg user signature (signed message) token: token to be expired ``` -Returns: -Success message if token is successfully deleted. -If the token is not found or already expired, returns an error message. +Returns: Success message if token is successfully deleted. If the token is not found or already expired, returns an error message. Example: ``` DELETE /api/services/deleteAuthToken?address=&&nonce=&&token=&signature= ``` + Inside the angular brackets, the user should provide the valid values for the request. Response: @@ -630,4 +621,3 @@ Response: ``` {"success": "Token has been deactivated."} ``` - diff --git a/developers/subgraph.md b/developers/subgraph.md new file mode 100644 index 00000000..6548e19b --- /dev/null +++ b/developers/subgraph.md @@ -0,0 +1,16 @@ +# Subgraph + +ETH: `https://v4.subgraph.mainnet.oceanprotocol.com` + +`Polygon: https://v4.subgraph.polygon.oceanprotocol.com/` + +`BSC: https://v4.subgraph.bsc.oceanprotocol.com` + +`EWC: https://v4.subgraph.energyweb.oceanprotocol.com` + +`Moonriver: https://v4.subgraph.moonriver.oceanprotocol.com` + +`goerli: https://v4.subgraph.goerli.oceanprotocol.com` + +`mumbai: https://v4.subgraph.mumbai.oceanprotocol.com` + diff --git a/discover/networks.md b/discover/networks.md index 2d9b5488..949c356d 100644 --- a/discover/networks.md +++ b/discover/networks.md @@ -1,83 +1,46 @@ --- title: Supported Networks -description: >- - All the public networks the Ocean Protocol contracts are deployed to, and - additional core components deployed to them. +description: All the public networks the Ocean Protocol contracts are deployed to. +cover: ../.gitbook/assets/landing/rewards.png +coverY: 0 --- # 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). -In each network, you’ll need ETH to pay for gas, and OCEAN for certain Ocean actions. Because the Ethereum mainnet is a network for production settings, ETH and OCEAN tokens have real value on there. The ETH and OCEAN tokens in each test network don’t have real value and are used for testing-purposes only. They can be obtained with _faucets_ to dole out ETH and OCEAN. - -The universal Aquarius Endpoint is [`https://v4.aquarius.oceanprotocol.com`](https://v4.aquarius.oceanprotocol.com). +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 tokens from faucets, which are services that provide small amounts of tokens for free. ### Ethereum Mainnet -Ethereum mainnet is a production network. In MetaMask and other ERC20 wallets, click on the network name dropdown, then select _Ethereum mainnet_. +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. -**Tokens** - -* Mainnet ETH: - * Native token to pay transaction fees -* Mainnet OCEAN: - * Address: [0x967da4048cD07aB37855c090aAF366e4ce1b9F48](https://etherscan.io/token/0x967da4048cD07aB37855c090aAF366e4ce1b9F48) - -**Additional Components** - -| What | URL | -| ------------ | --------------------------------------------------------------------------------- | -| Explorer | https://etherscan.io | -| Ocean Market | Point wallet to Ethereum Mainnet network, at https://v4.market.oceanprotocol.com/ | -| Provider | `https://v4.provider.mainnet.oceanprotocol.com` | -| Subgraph | `https://v4.subgraph.mainnet.oceanprotocol.com` | +| Gas Token | Mainnet ETH (Native token) | +| ----------- | -------------------------------------------------------------------------------------------------------------------- | +| OCEAN Token | [0x967da4048cD07aB37855c090aAF366e4ce1b9F48](https://etherscan.io/token/0x967da4048cD07aB37855c090aAF366e4ce1b9F48) | +| Explorer | [https://etherscan.io](https://etherscan.io) | ### Polygon Mainnet -Ocean is deployed to Polygon Mainnet, another production network. Polygon’s native token is MATIC. If you don’t find Polygon as a predefined network in your wallet, you can connect to it manually via Polygon's guide [here](https://docs.polygon.technology/docs/develop/metamask/config-polygon-on-metamask/#add-the-polygon-network-manually). +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. -**Tokens** - -* Matic: - * Native token to pay transaction fees -* Matic OCEAN: - * Address: [0x282d8efCe846A88B159800bd4130ad77443Fa1A1](https://polygonscan.com/token/0x282d8efce846a88b159800bd4130ad77443fa1a1) - -**Additional Components** - -| What | URL | -| ------------ | -------------------------------------------------------------------------------- | -| Explorer | https://polygonscan.com | -| Ocean Market | Point wallet to Ploygon Mainnet network, at https://v4.market.oceanprotocol.com/ | -| Provider | `https://v4.provider.polygon.oceanprotocol.com/` | -| Subgraph | `https://v4.subgraph.polygon.oceanprotocol.com/` | +| Gas Token | Matic(Native token) | +| --------- | ---------------------------------------------------------------------------------------------------------------------- | +| OCEAN | [0x282d8efCe846A88B159800bd4130ad77443Fa1A1](https://polygonscan.com/token/0x282d8efce846a88b159800bd4130ad77443fa1a1) | +| Explorer | [https://polygonscan.com](https://polygonscan.com) | **Bridge** -Check our Polygon Bridge [guide](../core-concepts/networks/bridges.md#polygon-ex-matic-bridge) to learn how you can deposit, withdraw and send tokens. +Check our Polygon Bridge [guide](bridges.md) to learn how you can deposit, withdraw and send tokens. ### Binance Smart Chain -Ocean is deployed to Binance Smart Chain (BSC), another production network. BSC’s native token is BNB - the Binance token. +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. -If you don’t find BSC as a predefined network in your wallet, you can connect to it manually via Binance’s guide [here](https://academy.binance.com/en/articles/connecting-metamask-to-binance-smart-chain). - -**Tokens** - -* BSC BNB: - * Native token to pay transaction fees. -* BSC OCEAN: - * Address: [0xdce07662ca8ebc241316a15b611c89711414dd1a](https://bscscan.com/token/0xdce07662ca8ebc241316a15b611c89711414dd1a) - -**Additional Components** - -| What | URL | -| ------------ | ------------------------------------------------------------------------------------ | -| Explorer | https://bscscan.com/ | -| Ocean Market | Point wallet to Binance Smart Chain network, at https://v4.market.oceanprotocol.com/ | -| Provider | `https://v4.provider.bsc.oceanprotocol.com` | -| Subgraph | `https://v4.subgraph.bsc.oceanprotocol.com` | +| Gas Token | BSC BNB(Native token) | +| --------- | ------------------------------------------------------------------------------------------------------------------ | +| OCEAN | [0xdce07662ca8ebc241316a15b611c89711414dd1a](https://bscscan.com/token/0xdce07662ca8ebc241316a15b611c89711414dd1a) | +| Explorer | [https://bscscan.com/](https://bscscan.com/) | **Bridge** @@ -85,104 +48,53 @@ Check our BSC Bridge [guide](../core-concepts/networks/bridges.md#binance-smart- ### Energy Web Chain -Ocean is deployed to [Energy Web Chain](https://energy-web-foundation.gitbook.io/energy-web/technology/the-stack/trust-layer-energy-web-chain), another production network. Energy Web’s native token is EWT. +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). -If you don’t find Energy Web Chain as a predefined network in your wallet, you can connect to it using the guide [here](https://energy-web-foundation.gitbook.io/energy-web/how-tos-and-tutorials/connect-to-energy-web-chain-main-network-with-metamash). - -**Tokens** - -* Energy Web Chain EWT: - * Native token to pay transaction fees. -* Energy Web Chain OCEAN: - * Address: [0x593122aae80a6fc3183b2ac0c4ab3336debee528](https://explorer.energyweb.org/token/0x593122aae80a6fc3183b2ac0c4ab3336debee528) - -**Additional Components** - -| What | URL | -| ------------ | --------------------------------------------------------------------------------- | -| Explorer | https://explorer.energyweb.org/ | -| Ocean Market | Point wallet to Energy Web Chain network, at https://v4.market.oceanprotocol.com/ | -| Provider | `https://v4.provider.energyweb.oceanprotocol.com/` | -| Subgraph | `https://v4.subgraph.energyweb.oceanprotocol.com` | +| 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/) | **Bridge** -Use the link [here](https://bridge.carbonswap.exchange) to bridge the assets between EWC and Ethereum mainnet. +To bridge assets between Energy Web Chain and Ethereum mainnet, you can use [this](https://bridge.carbonswap.exchange/) bridge. ### Moonriver -Ocean is deployed to [Moonriver](https://docs.moonbeam.network/builders/get-started/networks/moonriver/), another production network. Moonriver’s native token is MOVR. +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). -If you don’t find Moonriver as a predefined network in your wallet, you can connect to it using the guide [here](https://docs.moonbeam.network/builders/get-started/networks/moonriver/#connect-metamask). - -**Tokens** - -* Moonriver MOVR: - * Native token to pay transaction fees. -* Moonriver OCEAN: - * Address: [0x99C409E5f62E4bd2AC142f17caFb6810B8F0BAAE](https://blockscout.moonriver.moonbeam.network/token/0x99C409E5f62E4bd2AC142f17caFb6810B8F0BAAE/token-transfers) - -**Additional Components** - -| What | URL | -| ------------ | -------------------------------------------------------------------------- | -| Explorer | https://blockscout.moonriver.moonbeam.network | -| Ocean Market | Point wallet to Moonriver network, at https://v4.market.oceanprotocol.com/ | -| Provider | `https://v4.provider.moonriver.oceanprotocol.com` | -| Subgraph | `https://v4.subgraph.moonriver.oceanprotocol.com` | +| 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) | **Bridge** -Use [Anyswap](https://anyswap.exchange/#/bridge) to bridge between ETH Mainnet and Moonriver. +To bridge assets between Moonriver and Ethereum mainnet, you can use [this](https://anyswap.exchange/#/bridge) bridge. ### Görli -Görli is a test network. +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. -In MetaMask and other ERC20 wallets, click on the network name dropdown, then select _Goerli_. - -**Tokens** - -* Görli ETH: - * Native token to pay transaction fees - * [Faucet](https://goerlifaucet.com/). You may find others by [searching](https://www.google.com/search?q=goerli+ether+faucet%5C&oq=goerli+ether+faucet). -* Goerli OCEAN: - * Address: [0xCfDdA22C9837aE76E0faA845354f33C62E03653a](https://goerli.etherscan.io/address/0xcfdda22c9837ae76e0faa845354f33c62e03653a) - * [Faucet](https://faucet.goerli.oceanprotocol.com) - -**Additional Components** - -| What | URL | -| ------------ | -------------------------------------------------------------------- | -| Explorer | https://goerli.etherscan.io/ | -| Ocean Market | Point wallet to Görli network, at https://market.oceanprotocol.com | -| Provider | `https://v4.provider.goerli.oceanprotocol.com` | -| Subgraph | `https://v4.subgraph.goerli.oceanprotocol.com` | +| 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) | ### Mumbai -Mumbai is a test network tuned for Matic / Polygon. +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 you don't find Mumbai as a predefined network in your wallet, you can connect to it manually via [Matic's guide](https://docs.polygon.technology/docs/develop/metamask/config-polygon-on-metamask/). - -**Tokens** - -* Mumbai MATIC: - * Native token to pay transaction fees - * [Faucet](https://faucet.matic.network/). You may find others by [searching](https://www.google.com/search?q=mumbai+faucet). -* Mumbai OCEAN: - * Address: [0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8](https://mumbai.polygonscan.com/token/0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8) - * [Faucet](https://faucet.mumbai.oceanprotocol.com/) - -**Additional Components** - -| What | URL | -| ------------ | ------------------------------------------------------------------- | -| Explorer | https://mumbai.polygonscan.com | -| Ocean Market | Point wallet to Mumbai network, at https://market.oceanprotocol.com | -| Provider | `https://v4.provider.mumbai.oceanprotocol.com` | -| Subgraph | `https://v4.subgraph.mumbai.oceanprotocol.com` | +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) | ### Local / Ganache @@ -198,7 +110,7 @@ Alternatively, you can run Ganache independently. Install it according to [the G * Native token to pay transaction fees * By default, Ganache creates several Ethereum accounts at launch, gives each some ETH, and makes their private keys available in the logs. You can also instruct Ganache to give ETH to specific Ethereum addresses. * Ganache OCEAN: - * You can deploy an ERC20 token with label OCEAN. At a minimum, the token needs to be ERC20Detailed and ERC20Capped. You’ll see examples in the quickstarts for the Ocean JavaScript and Python drivers. + * You can deploy an ERC20 token with the label OCEAN. At a minimum, the token needs to be ERC20Detailed and ERC20Capped. You’ll see examples in the quickstarts for the Ocean JavaScript and Python drivers. ### Other