Connecting to Baobab
Last updated
Last updated
This section covers how to connect your 4-node ServiceChain network to the Baobab network. You will set up a Baobab EN and connect the EN with one of your SCNs. Then you will enable the anchoring feature to put ServiceChain block information onto the Baobab network.
1 Linux or MacOS server for EN
Minimum hardware requirements for testing
CPU: 4-core (Intel Xeon or equivalent), RAM: 16GB, HDD: 50GB
Please refer to the System Requirements for more explanation.
Download the Baobab EN executable. For the full list of downloadable binaries, see Download.
Assumptions and Limitations
A ServiceChain network is installed and running. Please refer to Setting up a 4-node Service Chain to setup a network.
A Baobab EN.
One EN can only connect to one SCN since only one-to-one connection is supported.
Every SCN does not have to connect to the EN.
The installation is the uncompression of the downloaded package. Extract the archive on the EN server.
From the EN server, download the genesis.json for Baobab network.
Now, we will initialize the EN node using the genesis file. Execute the following command. It will create the data folder storing the chain data and logs on your home directory. You can change the data folder using the --datadir directive.
Go to the ken installation folder and rename mv kend_baobab.conf kend.conf, then edit conf/kend.conf as follows.
You can check block sync status by watching klay.blockNumber. If this number is not 0, the node is working fine. Downloading all blocks on the Baobab network may take a long time depending on network conditions and hardware performance, so we recommend using Fast Sync to synchronize blocks.
If you want to stop a node, you can use the command kend stop
Take note of EN-01's KNI which is the information used to connect from an SCN-L2-01 node. This value will be used in the next step when generating main-bridges.json.
Log on to an SCN-L2-01 (note: not the EN-01 node) and create main-bridges.json on ~/data. Replace [::] located after @ letter with EN-01 node's IP address.
From the SCN-L2-01 node's shell, edit kscn-XXXXX-amd64/conf/kscnd.conf. If SC_SUB_BRIDGE is set to 1, data anchoring starts automatically when the SCN-L2-01 node starts. In this example, SC_PARENT_CHAIN_ID is set to 1001 because the chainID of the parent chain, Baobab, is 1001. SC_ANCHORING_PERIOD is the parameter that decides the period to send an anchoring tx to the main chain. By setting the value to 10, you configure the node to perform anchoring every 10 blocks. The default value is 1.
Restart kscn by executing the following command:
Check if the SCN-L2-01 is connected to the EN-01 by checking subbridge.peers.length
After finishing the EN-01 and SCN-L2-01 connection, you can log ServiceChain block information on the parent chain via Anchoring. In this section, you will top up a parent operator account, enable Anchoring, and check the anchored block number.
Anchoring requires SCN-L2-01 to make an anchoring transaction to Baobab. So subbridge.parentOperator account should have enough KLAY to pay the transaction fee. Get some KLAY from Baobab Wallet Faucet and transfer some KLAY to the parentOperator. For data anchoring in real service, parentOperator needs to have enough KLAY for transaction fee.
To start anchoring, execute the following command:
After anchoring starts, you can check the latest block anchored to Baobab by using subbridge.latestAnchoredBlockNumber. Please note that this only works after the EN already followed up on the latest block of Baobab. By default, SCN-L2-01 tries anchoring on every block from the block on which anchoring is turned on. The anchoring period can be set by changing SC_ANCHORING_PERIOD. If the value is set to 10, the node tries anchoring when the block number is a multiple of 10.
