10 KiB
| title | description |
|---|---|
| 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 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.
The universal Aquarius Endpoint is https://aquarius.oceanprotocol.com.
Ethereum 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.
Tokens
- ETH:
- Native token to pay transaction fees
- Exchanges to purchase
- OCEAN:
Additional Components
| What | URL |
|---|---|
| Explorer | https://etherscan.io |
| Ocean Market | https://market.oceanprotocol.com |
| Provider | https://provider.mainnet.oceanprotocol.com |
| Subgraph | https://subgraph.mainnet.oceanprotocol.com |
Polygon Mainnet
Ocean is deployed to the Polygon 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 this guide and the parameters below.
| What | Value |
|---|---|
| Network Name | Matic Mainnet |
| RPC | https://rpc.polygon.oceanprotocol.com/ |
| Chain Id | 137 |
| Currency Symbol | MATIC |
| Block Explorer URL | https://explorer.matic.network/ |
Tokens
- MATIC:
- Native token to pay transaction fees
- Exchanges to purchase
- Polygon OCEAN:
Additional Components
| What | URL |
|---|---|
| Explorer | https://polygonscan.com/ |
| Ocean Market | Point wallet to Polygon network, at https://market.oceanprotocol.com |
| Provider | https://provider.polygon.oceanprotocol.com |
| Subgraph | https://subgraph.polygon.oceanprotocol.com |
Bridge
Check our Polygon Bridge guide 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.
If you don't find BSC as a predefined network in your wallet, you can connect to it manually via Binance's guide or Ocean's guide and the parameters below.
| What | Value |
|---|---|
| Network Name | Smart Chain |
| RPC | https://bsc-dataseed.binance.org/ |
| Chain Id | 56 |
| Currency Symbol | BNB |
| Block Explorer URL | https://bscscan.com |
Tokens
- BSC BNB:
- Native token to pay transaction fees
- Exchanges to purchase: typically binance.com
- BSC OCEAN:
Additional Components
| What | URL |
|---|---|
| Explorer | https://bscscan.com/ |
| Ocean Market | Point wallet to BSC network, at https://market.oceanprotocol.com |
| Provider | https://provider.bsc.oceanprotocol.com |
| Subgraph | https://subgraph.bsc.oceanprotocol.com |
Bridge
Check our BSC Bridge guide to learn how you can deposit, withdraw and send tokens.
Ropsten
Ropsten is a test network.
In MetaMask and other ERC20 wallets, click on the network name dropdown, then select Ropsten.
Tokens
- Ropsten ETH:
- Ropsten OCEAN:
Additional Components
| What | URL |
|---|---|
| Explorer | https://ropsten.etherscan.io |
| Ocean Market | Point wallet to Ropsten network, at https://market.oceanprotocol.com |
| Provider | https://provider.ropsten.oceanprotocol.com |
| Subgraph | https://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.
Tokens
- Rinkeby ETH:
- Rinkeby OCEAN:
Additional Components
| What | URL |
|---|---|
| Explorer | https://rinkeby.etherscan.io |
| Ocean Market | Point wallet to Rinkeby network, at https://market.oceanprotocol.com |
| Provider | https://provider.rinkeby.oceanprotocol.com |
| Subgraph | https://subgraph.rinkeby.oceanprotocol.com |
Mumbai
Mumbai is a test network tuned for Matic / Polygon.
If you don't find Mumbai as a predefined network in your wallet, you can connect to it manually via Matic's guide.
Tokens
- Mumbai MATIC:
- Mumbai OCEAN:
Additional Components
| What | URL |
|---|---|
| Explorer | https://mumbai.polygonscan.com |
| Ocean Market | Point wallet to Mumbai network, at https://market.oceanprotocol.com |
| Provider | https://provider.mumbai.oceanprotocol.com |
| Subgraph | https://subgraph.mumbai.oceanprotocol.com |
Local / Ganache
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.
Tokens
- Ganache ETH:
- 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.
Other
Some apps may need network_id and chain_id. Here's a list of values for major Ethereum networks.