How To Configure¶
CodeChain can be configured with either CLI options or a config file. When it comes to which options take precedence, it goes from CLI, user’s own config.toml file, and config.dev.toml in that order.
CLI options can be listed by running the command
$codechain --help. By using the CLI options, or custom config files, the user can overwrite config.dev.toml’s configurations.
The default preset
config.dev.toml file can be located in
Config files can be customized by the user and its location can be designated by using the CLI command
--config. Custom config files created by the user must have the proper custom path.
The following represents the default configuration values of
[codechain] quiet = false db_path = "db" keys_path = "keys" chain = "solo" [mining] [network] disable = false port = 3485 max_peers = 30 min_peers = 10 bootstrap_addresses =  sync = true transaction_relay = true discovery = true discovery_type = "unstructured" discovery_refresh = 60000 discovery_bucket_size = 10 [rpc] disable = false interface = "127.0.0.1" port = 8080 [ipc] disable = false path = "/tmp/jsonrpc.ipc" [snapshot] disable = false path = "snapshot"
CodeChain is set to use the Solo consensus algorithm by default. Tendermint is not suitable for solo testing purposes, since it requires a minimum of 4 users to function properly.
In order to test CodeChain alone, you may want to change chain to Solo. To do this, use
CLI Options for CodeChain client¶
- Specify the certain config file path that you want to use to configure CodeChain to your needs.
- Listen for connections on PORT. (default: 3485)
- Bootstrap addresses to connect.
- Do not open network socket.
- Set the minimum number of connections the user would like. (default: 10)
- Set the maximum number of connections the user would like. (default: 30)
- Specify instance id for logging. Used when running multiple instances of CodeChain.
- Do not show any synchronization information in the console.
- Set the blockchain type out of solo, simple_poa, tendermint or a path to chain scheme file. (default: solo)
- Specify the database directory path.
- Specify the path for JSON key files to be found.
- Specify the snapshot directory path.
- Do not run block sync extension.
- Do not relay transactions.
- Specify the interface address for rpc connections
- Listen for rpc connections on PORT. (default: 8080)
- Do not run JSON-RPC over IPC service.
- Specify custom path for JSON-RPC over IPC service
- Do not run jsonrpc.
- Specify the block’s author (aka “coinbase”) address for sending block rewards from sealed blocks.
- Specify the address which should be used to sign consensus messages and issue blocks.
- A value which is used to check whether a new transaciton can replace a transaction in the memory pool with the same signer and seq. If the fee of the new transaction is new_fee and the fee of the transaction in the memory pool is old_fee, then new_fee > old_fee + old_fee >> mem_pool_fee_bump_shift should be satisfied to replace. Local transactions ignore this option.
- Maximum amount of memory that can be used by the mem pool. Setting this parameter to 0 disables limiting.
- Maximum amount of transactions in the queue (waiting to be included in next block).
- URLs to which work package notifications are pushed.
- Force the node to author new blocks as if it were always sealing/mining.
- Specify the minimum time between reseals from incoming transactions. MS is time measured in milliseconds.
- Specify the maximum time since last block to enable force-sealing. MS is time measured in milliseconds.
- Specify the number of historical work packages which are kept cached lest a solution is found for them later. High values take more memory but result in fewer unusable solutions.
- Do not use discovery. No automated peer finding.
--discovery="kademlia" | "unstructured"
- Decide which p2p discovery extension to use. Options are kademlia and unstructured. In a testing environment, an unstructured p2p network is desirable because it is more than sufficient when there are a few users. (default: unstructured)
- Bucket size for discovery. Choose how many addresses to exchange at a time during discovery.
- Refresh timeout of discovery (ms). It may conflict with:`` –no-discovery``.
- Disable snapshots