homicommand to create scripts and configuration files for building L3. You can run
homion any Linux/Mac PC. Baobab's
1001, and L2's
chainIDwas set to
1002in the previous example, so for convenience, L3's
chainIDis set to
1003. When operating a blockchain for an actual service, you must register a new
chainIDvalue at https://chainlist.defillama.com/ to avoid the
chainIDconflict with other ServiceChains and EVM chains.
portinformation of ServiceChain L3 nodes in
homi-outputto all SCN nodes (SCN-L3-01, SCN-L3-02, SCN-L3-03, SCN-L3-04) of ServiceChain L3.
static-nodes.jsonto the data folder
~/data, and copy
nodekeysone by one.
conf/kscnd.confon all SCNs in ServiceChain L3 as follows: The
PORTuses 22323, the default port of the ServiceChain.
conf/kscnd.confof SCN-L2-03 as follows.
main-bridges.jsonfile of SCN-L2-03 node, which will be set up the subbridge in the ServiceChain L3.
~/datafolder. Replace [::] after @ with the IP address of the node you checked in step 4.
conf/kscnd.confof the SCN-L3-01 node with subbridge as follows. set
SC_SUB_BRIDGEto 1 for activating the bridge connection, and
chainIDof L2, Set
SC_ANCHORINGto 1 to automatically anchor data upon restart. You can also access the SCN-L3-01 shell and turn on data anchoring with the
subbridge.anchoring(true)command or turn it off with the
SC_ANCHORING_PERIODis a parameter that determines how often anchoring transactions are sent to the parent chain. Set the node to anchor every 10 blocks by specifying a value of 10. Default is 1.
subbridge.peers.lengthto see if SCN-L3-01 is connected to SCN-L2-03, check
subbridge.latestAnchoredBlockNumberto check the latest anchored block number to see if anchoring is in progress.