Supported Networks

All the public networks the Ocean Protocol contracts are deployed to, and additional core components deployed to them.

Ocean Protocol contracts are deployed on multiple public Ethereum networks. You can always find the most up-to-date deployment addresses for all individual contracts in the address.json artifact.

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.

Mainnet

The Ethereum Mainnet is Ocean’s production network.

MetaMask and other ERC20 wallets default to Ethereum mainnet, therefore your wallet is almost certainly pointing to Ethereum by default.

Get Tokens

Additional Components

WhatURL
Explorerhttps://etherscan.io
Ocean Markethttps://market.oceanprotocol.com
Providerhttps://provider.mainnet.oceanprotocol.com
Aquariushttps://aquarius.mainnet.oceanprotocol.com
Subgraphhttps://subgraph.mainnet.oceanprotocol.com

Ropsten

Ropsten is a test network.

In MetaMask and other ERC20 wallets, click on the network name dropdown, then select Ropsten.

Get Tokens

Additional Components

WhatURL
Explorerhttps://ropsten.etherscan.io
Ocean MarketPoint wallet to Ropsten network, at https://market.oceanprotocol.com
Providerhttps://provider.ropsten.oceanprotocol.com
Aquariushttps://aquarius.ropsten.oceanprotocol.com
Subgraphhttps://subgraph.ropsten.oceanprotocol.com

Rinkeby

Rinkeby is a test network.

In MetaMask and other ERC20 wallets, click on the network name dropdown, then select Rinkeby.

Get Tokens

Additional Components

WhatURL
Explorerhttps://rinkeby.etherscan.io
Ocean MarketPoint wallet to Rinkeby network, at https://market.oceanprotocol.com
Providerhttps://provider.rinkeby.oceanprotocol.com
Aquariushttps://aquarius.rinkeby.oceanprotocol.com
Subgraphhttps://subgraph.rinkeby.oceanprotocol.com

Local

The most straightforward way for local-only development is to use Barge, which runs Ganache, Aquarius, and Provider. It is used extensively by the Ocean core devs (with Ganache or Rinkeby) and for automated integration testing.

To connect to it from MetaMask, select the network called Localhost 8545.

Alternatively, you can run Ganache independently. Install it according to the Ganache docs. Then deploy Ocean contracts onto Ganache following docs in Ocean contracts repo. Ganache is at the RPC URL http://localhost:8545.

Get Tokens

  • ETH: 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.
  • 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.

Chain IDs

Some apps may need network_id and chain_id. Here’s a list of values for major Ethereum networks.