oceanprotocol/docs
1
0
Fork 0
mirror of https://github.com/oceanprotocol/docs.git synced 2024-11-02 08:20:22 +01:00
Code Releases Activity

Merge pull request #168 from oceanprotocol/add-testnet-details-to-testnets-page

Browse Source 
Update & add details to the "Testnets" page
This commit is contained in:
Troy McConaghy 2019-03-14 17:11:21 +01:00 committed by GitHub
commit 7bf10b8dd9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 75 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

89
content/concepts/testnets.md
View File

@ -1,29 +1,90 @@
---
title: Testnets
description: An overview of public testnets that you can test Ocean Protocol applications against.
description: An overview of public test networks that you can test Ocean Protocol applications against.
---
You can test an Ocean Protocol application (such as a marketplace) against some testnets that are maintained by the Ocean Protocol Foundation and others.
You can test an Ocean Protocol application (such as a marketplace) against the test networks (testnets) described below.
## Kovan Testnet
## The Kovan Testnet
The [Kovan Testnet](https://github.com/kovan-testnet/proposal) (or just "Kovan") is a public Ethereum testnet operated by members of the Ethereum community. The Ocean Protocol [keeper contracts](https://github.com/oceanprotocol/keeper-contracts) (smart contracts) are deployed there.
The [Kovan Testnet](https://github.com/kovan-testnet/proposal) (or just "Kovan") is a public Ethereum Testnet operated by members of the Ethereum community.
Moreover, there is a [Secret Store](/concepts/components/#secret-store) operated by the Ocean Protocol Foundation which is connected to the Kovan Testnet.
Most Ethereum wallets and libraries know how to connect to the Kovan Testnet. If you're using [Barge](https://github.com/oceanprotocol/barge) to run a local Kovan node, you can connect to that local Kovan node at RPC URL [http://localhost:8545](http://localhost:8545) (called "Localhost 8545" in MetaMask).
## Nile Testnet
### Kovan Blockchain Explorers
_Formerly called the Ocean POA Tesnet._
There are some Kovan blockchain explorers, e.g. [Etherscan for Kovan](https://kovan.etherscan.io/) and [BlockScout for Kovan](https://blockscout.com/eth/kovan). You can use those to check the status of a transaction, the balance of an account, and more.
The Nile Testnet is similar to the Kovan Testnet, except all the nodes are operated by the Ocean Protocol Foundation. The Ocean Protocol [keeper contracts](https://github.com/oceanprotocol/keeper-contracts) (smart contracts) are deployed there.
### Keeper Contracts on Kovan
Moreover, there is a [Secret Store](/concepts/components/#secret-store) operated by the Ocean Protocol Foundation which is connected to the Nile Testnet.
The Ocean Protocol [keeper contracts](https://github.com/oceanprotocol/keeper-contracts) (smart contracts) are deployed on Kovan. In fact, several versions of the keeper contracts have been deployed there. You can find the addresses of recently-deployed keeper contracts (including the OceanToken contract) as follows:
## Spree Testnet
1. Go to [the list of keeper-contracts releases (Git tags) on GitHub](https://github.com/oceanprotocol/keeper-contracts/releases).
1. Click on the name of a release's Git tag in the left sidebar. It will look something like `v0.8.3`.
1. Scroll down to the **Kovan Testnet** section of the README.md file. The contract addresses are listed there. Note: Sometimes there is a disconnect between the release number and the listed version number.
When Ocean Protocol developers run [Barge](https://github.com/oceanprotocol/barge) with the `--local-spree-node` option, a "Spree Testnet" node is deployed on their local machine: a local "testnet" not connected to any public testnet. It's named after the main river flowing through Berlin, Germany, where many Ocean Protocol developers are located.
Note: Because Ocean Protocol uses ZeppelinOS to manage smart contract upgrades, a keeper contract address might not change over time (because it's just the address _of the proxy contract_) but the actually-used smart contract might change, along with its functionality.
## Technical Details about the Public Testnets
### Ocean Components Connected to Kovan
- [Details about the Nile Testnet](https://github.com/oceanprotocol/dev-ocean/blob/master/doc/devops/secret-store-cluster.md) (which is called the "Parity Secret Store Cluster" on that page).
- [Addresses of the keeper contracts](https://github.com/oceanprotocol/keeper-contracts#testnet-deployment) (smart contracts) deployed in the public testnets (and more).
There is a [Secret Store](/concepts/components/#secret-store) connected to the Kovan Testnet for use by Ocean Protocol projects (including your projects). It's operated by BigchainDB GmbH. Its URL is:
[https://secret-store-kovan.dev-ocean.com/](https://secret-store-kovan.dev-ocean.com/)
Aside from the Secret Store, there is no other Ocean Protocol software component (e.g. Aquarius) that is live, connected to the Kovan Testnet, and operated by BigchainDB GmbH.
## The Nile Testnet
_Formerly called the Ocean POA Testnet._
The Nile Testnet is similar to the Kovan Testnet, except all the nodes are operated by BigchainDB GmbH.
### Nile Testnet Parameters
Parameter | Value
-------------------|---------------
RPC URL (required) | [https://nile.dev-ocean.com/](https://nile.dev-ocean.com/)
ChainID | 8995 (decimal for MetaMask) or 0x2323 (hexadecimal)
Symbol | Whatever you like
Nickname | Whatever you like
- In MetaMask, you don't need to include the port number with the RPC URL.
- If you're using MetaMask, see the [MetaMask docs about how it uses the ChainID](https://metamask.github.io/metamask-docs/Main_Concepts/Sending_Transactions).
- If you're using [Barge](https://github.com/oceanprotocol/barge) to run a local Nile node:
- You can connect to that local Nile node at RPC URL [http://localhost:8545](http://localhost:8545) (called "Localhost 8545" in MetaMask).
- You can configure that local Nile node by editing the files in the `barge/networks/nile/config/` directory.
### Nile Blockchain Explorers
There is a Nile blockchain explorer at [https://submarine.dev-ocean.com/](https://submarine.dev-ocean.com/). You can use it to check the status of a transaction, the balance of an account, and more. It uses the following symbols for Nile Ether and Nile Ocean Tokens:
Cryptocurrency | Symbol used
------------------|------------
Nile Ether | POA
Nile Ocean Tokens | OCEAN or SBT-OCN
### Keeper Contracts on Nile
See the subsection about the [Keeper Contracts on Kovan](#keeper-contracts-on-kovan). The Nile contract addresses can be found in the same way.
### Ocean Components Connected to Nile
There are several Ocean Protocol software components that are live, connected to the Nile Testnet, and operated by BigchainDB GmbH:
- Secret Store at [https://secret-store.dev-ocean.com](https://secret-store.dev-ocean.com)
- Aquarius at [https://nginx-aquarius.dev-ocean.com](https://nginx-aquarius.dev-ocean.com)
- Brizo at [https://nginx-brizo.dev-ocean.com](https://nginx-brizo.dev-ocean.com)
- Jupyter Hub at [https://mantaray.dev-ocean.com](https://mantaray.dev-ocean.com)
- [Token Bridge Frontend](https://github.com/oceanprotocol/bridge-ui) (for a token bridge between Nile and Kovan) at [https://token-bridge.dev-ocean.com](https://token-bridge.dev-ocean.com)
> Internal note: The private "atlantic" repo documents the internal details of the Nile Testnet in `networks/nile/README.md`.
## A Spree Testnet
When Ocean Protocol developers run [Barge](https://github.com/oceanprotocol/barge) with the `--local-spree-node` option, a "Spree Testnet" is deployed on their local machine: a local testnet not connected to any external public testnet. The RPC URL is [http://localhost:8545](http://localhost:8545) (called "Localhost 8545" in MetaMask).
Spree Testnet details can be found in the [Barge README.md file](https://github.com/oceanprotocol/barge/blob/develop/README.md).
You can configure the Spree nodes by editing the files in the `barge/networks/spree/` directory.
Note: Spree testnets are named after the Spree River, the main river flowing through Berlin, Germany, where many Ocean Protocol developers are located.