Last updated
Last updated
You must execute the action on the account on the EOS mainnet with the mainnet account created to represent the chain name. The syntax is as follows:
chain_name
{name} - name of EOS mainnet account deploying chain, e.g., mynewchainnn
chain_meta
{chain_metadata_t} - chain data
is_public
{bool} - whether the chain is public
is_single_node
{bool} - whether chain is a single node
dappservices_contract
{std::string} - account that dappservicex.cpp
is deployed to, e.g., dappservicex
chain_id
{std::string} - chain ID of sidechain
type
{std::string} - type of blockchain, e.g., EOSIO
endpoints
{std::vector} - list of public endpoints for developers to use
chain_json_uri
{std::vector} - publicly available json file that declares chain statistics
Example cleos command:
After that, you must run the init
action on the dappservicex
contract.
chain_name
{name} - name of EOS mainnet account deploying chain, e.g., mynewchainnn
Example cleos command:
And now you’re setup to begin configuring DSPs and then enabling users to use DAPP Network services. DSPs and developers will need to know the chain_name
used on the mainnet and the account the dappservicex.cpp
contract was set to on the new chain.