genesis.json
for Baobab
network.--datadir
directive.mv kend_baobab.conf kend.conf
, then edit conf/kend.conf
as follows.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.kend stop
main-bridges.json
.main-bridges.json
on ~/data
. Replace [::]
located after @
letter with EN-01 node's IP address.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.subbridge.peers.length
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.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.