oceanprotocol/docs
1
0
Fork 0
mirror of https://github.com/oceanprotocol/docs.git synced 2024-11-26 19:49:26 +01:00
Code Releases Activity

Give more help with connecting to Nile Testnet

Browse Source
This commit is contained in:
Troy McConaghy 2019-04-05 15:48:35 +02:00
parent 41f0e97c11
commit a49200e0d6
2 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/concepts/testnets.md
View File

@ -27,6 +27,10 @@ _Formerly called the Ocean POA Testnet._
The Nile Testnet is similar to the Kovan Testnet, except all the nodes are operated by BigchainDB GmbH. The Nile Testnet is similar to the Kovan Testnet, except all the nodes are operated by BigchainDB GmbH.
### Connect to the Nile Testnet
See the [tutorial page about connecting to Ocean-related networks](/tutorials/connect-to-networks/#connect-to-the-nile-testnet).
### Nile Blockchain Explorers ### 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: 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:
@ -52,6 +56,8 @@ There are several Ocean Protocol software components that are live, connected to
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. 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.
When running a Spree Testnet, you can connect to a node at RPC URL [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. 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. Note: Spree testnets are named after the Spree River, the main river flowing through Berlin, Germany, where many Ocean Protocol developers are located.

6
content/tutorials/connect-to-networks.md
View File

@ -16,9 +16,9 @@ Here are the parameters you might need to connect to the [Nile Testnet](/concept
| Parameter | Value | | Parameter | Value |
| ------------------ | ---------------------------------------------------------- | | ------------------ | ---------------------------------------------------------- |
| RPC URL (required) | [https://nile.dev-ocean.com/](https://nile.dev-ocean.com/) | | RPC URL (required) | [https://nile.dev-ocean.com/](https://nile.dev-ocean.com/) |
| ChainID | 8995 (decimal for MetaMask) or 0x2323 (hexadecimal) | | ChainID | `8995` (decimal for MetaMask) or `0x2323` (hexadecimal) |
| Symbol | Whatever you like | | Symbol | Whatever you like, e.g. `NILE ETH` |
| Nickname | Whatever you like | | Nickname | Whatever you like, e.g. `Nile Testnet` |
In MetaMask, click on the network name then click on `Custom RPC` in the drop-down list. Scroll down to the `New Network` section. Enter the above RPC URL. You don't need to add a port number to the end of the RPC URL. Enter the ChainID, Symbol and Nickname if you like. See the [MetaMask docs about how it uses the ChainID](https://metamask.github.io/metamask-docs/Main_Concepts/Sending_Transactions). In MetaMask, click on the network name then click on `Custom RPC` in the drop-down list. Scroll down to the `New Network` section. Enter the above RPC URL. You don't need to add a port number to the end of the RPC URL. Enter the ChainID, Symbol and Nickname if you like. See the [MetaMask docs about how it uses the ChainID](https://metamask.github.io/metamask-docs/Main_Concepts/Sending_Transactions).