Procedure for Connecting to JOC Testnet

This document describes the procedure for setting up a Geth node in the user environment and connecting to the Japan Open Chain Testnet. Please refer here if you wish to use RPC Endpoints for connecting dApps.

The flow to connection is as follows:

• 1. Installation of Geth
• 2. Initial Settings
• 3. Initialization of Geth
• 4. Synchronization
• 5. Verification

1. Installation of Geth

Install Geth on the source PC. ( Confirmed to work up to Geth ver 1.13.5 ) https://geth.ethereum.org/docs/getting-started/installing-geth

2. Initial Settings

Create a data directory in any directory. Here, it is called "data".

Unset

$ mkdir data

Create a "genesis.json" in the created data directory to describe block information.

Unset

$ sudo vi data/genesis.json

The content of genesis.json is provided separately in a file.

3. Initialization of Geth

Initialize Geth. Execute the following command to specify the created genesis.json.

Unset

$ geth init --datadir data data/genesis.json

4. Synchronization

Synchronize with the target node. If you want to connect to node-1, execute the following command.

Unset

$ geth --datadir data --networkid=361257328
--bootnodes="enode://ba571177c1c4e85103a323713f72781b1a9ea6ca7316660c
22629bb3fb7565a0436e337b9cfe84140faea510bb156fbe125f96ce7f916ad6914c3
58630559f77@43.206.223.86:30303" -http.api
"clique,personal,eth,net,web3,miner,admin" --http.corsdomain="*"
--http --http.addr="0.0.0.0" --http.port=8546 --snapshot=false
--syncmode="full"

The parameters of the testnet are as follows:

Node	Network ID	enode
Public Cluster-node-1	361257328	enode://ba571177c1c4e85103a323713f72781b1a9ea6ca7316660c22629bb3fb7565a0436e337b9cfe84140faea510bb156fbe125f96ce7f916ad6914c358630559f77@43.206.223.86:30303
Public Cluster-node-2	361257328	enode://8aa6f351eff4bee5d3a6a72ca5820fac65274e9dbd63e13d060682a5228000ab960ff8c177d7cf66b0555859b7eabbc866b71625626a11856e3573bf0592bfed@18.183.231.155:30303

5. Verification

You can verify the synchronization state as follows. If the message "Looking for peers" continues, you may not be properly connected, so please check your synchronization command and network environment.