Komodo Docs
GitHub

Common Runtime Parameters

Introduction

The following is an abbreviated list of runtime parameters and settings that can be initiated in a Smart Chain’s .conf file.

These commands largely derive from the upstream Bitcoin software, bitcoind.

Komodo is a fork of Zcash, and Zcash is a privacy-centric fork of Bitcoin. Therefore, essentially all runtime parameters and API commands available in both Bitcoin and Zcash are available in Komodo.

To see additional Bitcoin-based runtime parameters not included here, please visit the relevant Bitcoin wiki page.

addnode

addnode tells the daemon which nodes are trusted to act as seed nodes. After connecting to a node via addnode, the trusted node will send your node the list of all nodes that it is connected to, and your node will then connect to these additional nodes until the max limit is reached.

This contrasts from the connect runtime parameter, as the latter does not attempt to connect your node to additional nodes.

If you are behind a firewall or are having issues connecting to the network, addnode is a stronger option.

On the other hand, if you want to connect only to designated and trusted nodes, connect is a stronger option.

If you run multiple nodes that are connected via a LAN, it is not necessary for each node to open multiple connections. Instead, use connect to connect all to one primary node, and then use addnode on the primary node to connect to the network.

The p2p port must not be blocked by a firewall. If the computers do not have public IP addresses, you will need to port-forward the p2p port on both computers and append the forwarded port to the IP.

📌 Examples:

./komodod -ac_name=EXAMPLECHAIN -ac_supply=1000000 -addnode=<IP of the second node>:8096

Using addnode as a default value in the Smart Chain’s .conf file:

addnode=69.164.218.197

addressindex

addressindex instructs a Smart Chain to maintain an index of all addresses and balances.

We recommend that the user manually delete the blockchain data before initiating this parameter.

addressindex is enabled by default on any Smart Chain that utilizes Antara.

📌 Examples:

Using addressindex as a runtime parameter:

komodod -addressindex=1

Using addressindex as a default value in the Smart Chain’s .conf file:

addressindex=1

bantime

bantime sets the default number of seconds for a ban initiated during the daemon’s session. The default is 86400.

📌 Examples:

Using bantime as a runtime parameter:

komodod -bantime=100000

Using bantime as a default value in the Smart Chain’s .conf file:

bantime=100000

bind

bind instructs the Smart Chain daemon to bind to a given address and always listen on it.

Use [host]:port notation for IPv6.

📌 Examples:

Using bind as a runtime parameter:

komodod -bind=127.0.0.1:9050

Using bind as a default value in the Smart Chain’s .conf file:

bind=127.0.0.1:9050

connect

connect connects the komodod server to a trusted peer node, but not to request or add any additional nodes.

Please refer to the addnode parameter entry for more information.

📌 Examples:

Using connect as a default value in the Smart Chain’s .conf file:

connect=69.164.218.197

conf

conf allows the user to indicate an alternative configuration file for the Smart Chain daemon. The conf runtime parameter requires an absolute path. For example, /home/user/mydirectory/MYCOIN/MYCOIN.conf. Once the conf parameter is activated, the default configuration file is otherwise ignored.

📌 Examples:

Using conf as a runtime parameter:

komodod -conf=/home/username/coinConfs/DEX.conf

datadir

datadir allows the user to indicate an alternative blockchain-data directory for the Smart Chain daemon. The datadir parameter requires an absolute path. For example, home/user/mydirectory/MYCOIN/MYCOINDATA. Once this parameter is activated, the daemon will ignore the default data directory.

The name of the alternative directory must match the value provided to the ac_name parameter.

📌 Examples:

Using datadir as a runtime parameter:

komodod -datadir=/home/username/coinData/DEX

donation

donation donates all user rewards to a specific address. This value must be set to a 33 byte pubkey.

📌 Examples:

Using donation as a default value in the Smart Chain’s .conf file:

donation=027dc7b5cfb5efca96674b45e9fda18df069d040b9fd9ff32c35df56005e330392

exchange

exchange forfeits all user rewards to miners. Set this to explicitly not claim user rewards.

📌 Examples:

Using exchange as a default value in the Smart Chain’s .conf file:

exchange=1

exportdir

exportdir tells the Smart Chain daemon where to store the wallet backup files created through the backupwallet and dumpwallet calls.

📌 Examples:

Using exportdir as a default value in the Smart Chain’s .conf file:

exportdir=/home/myusername/mydirectory

gen

gen instructs the daemon to attempt to generate new blocks, and thereby mine new coins.

See also setgenerate.

📌 Examples:

Using gen as a runtime parameter to mine using 4 threads:

./komodod -gen -genproclimit=4

genproclimit

genproclimit sets the number of threads to be used for mining. To use all the available processors, use the value -1.

📌 Examples:

Using genproclimit as a default value in the Smart Chain’s .conf file, to mine using 2 threads:

genproclimit=2

keypool

keypool instructs the daemon to pre-generate a certain number of public/private key pairs. This can facilitate wallet.dat backups being valid for both prior transactions and several dozen future transactions.

📌 Examples:

Using keypool as a default value in the Smart Chain’s .conf file:

keypool=100

listen

listen instructs the daemon to listen for RPC calls on the network. It is enabled by default, except when connect is used.

📌 Examples:

Using listen as a runtime parameter:

komodod -listen=1

Using listen as a default value in the Smart Chain’s .conf file:

listen=1

maxconnections

maxconnections sets the maximum number of inbound and outbound connections.

📌 Examples:

Using maxconnections as a runtime parameter:

komodod -maxconnections=NUMBER

Using maxconnections as a default value in the Smart Chain’s .conf file:

maxconnections=NUMBER

mempooltxinputlimit

mempooltxinputlimit is a runtime parameter inherited from Zcash. The functionality it facilitates is now enabled by default, and therefore the parameter is deprecated. Please see the Zcash documentation for more information.

port

port tells the daemon to listen for p2p connections on the indicated TCP port, overwriting the default. The default p2pport for the Komodo(KMD) blockchain is 7770. The default p2p port of a Smart Chain is solely dependant on the -ac_ Antara customization parameters and values used to launch it.

📌 Examples:

Using port as a default value in the Smart Chain’s .conf file:

port=8231

proxy

proxy allows the user to connect via a SOCKS5 proxy.

📌 Examples:

Using proxy as a runtime parameter:

komodod -proxy=127.0.0.1:9050

Using proxy as a default value in the Smart Chain’s .conf file:

proxy=127.0.0.1:9050

pubkey

pubkey sets an address to use as a change address for all transactions. This value must be set to a 33 byte pubkey. All mined/staked coins will also be sent to this address. We recommend that the user ensure they own the corresponding privkey of their chosen pubkey, lest their funds be sent to a pubkey they do not own or control.

The pubkey parameter is required for all Antara-enabled chains. All Antara transactions will utilize the pubkey as an integral property.

📌 Examples:

Using pubkey as a default value in the Smart Chain’s .conf file:

pubkey=027dc7b5cfb5efca96674b45e9fda18df069d040b9fd9ff32c35df56005e330392

Using pubkey as a startup parameter:

-pubkey=027dc7b5cfb5efca96674b45e9fda18df069d040b9fd9ff32c35df56005e330392

regtest

regtest instructs the Smart Chain daemon to run a regression test network. Typically, the user will create a disposable Smart Chain for these purposes. The ac_supply parameter is not required in this instance.

(A regression-test network is a useful tool for rapid trial and testing. Please reach out to us if you are curious to implement this tool in your workflow and are unfamiliar with the process.)

📌 Examples:

Using regtest as a runtime parameter:

komodod -ac_name=TEST -regtest

Using regtest as a default value in the Smart Chain’s .conf file:

regtest=0

reindex

reindex instructs the daemon to re-index the currently synced blockchain data.

📌 Examples:

Using reindex as a runtime parameter:

komodod -reindex

rewind

rewind rewinds the chain to a specific block height. This is useful for creating snapshots at a given block height.

📌 Examples:

Using rewind as a runtime parameter:

komodod -rewind=777777

rpcallowip

rpcallowip tells the daemon which ip addresses are acceptable for receiving rpc commands.

By default, only rpc connections from localhost are allowed.

Specify as many rpcallowip= settings as you like to allow connections from other hosts, either as a single IPv4/IPv6 or with a subnet specification.

📌 Examples:

Using rpcallowip as a default value in the Smart Chain’s .conf file:

  rpcallowip=10.1.1.34/255.255.255.0
  rpcallowip=1.2.3.4/24
  rpcallowip=2001:db8:85a3:0:0:8a2e:370:7334/96

rpcbind

rpcbind instructs the daemon to listen for json-rpc connections.

Use [host]:port notation for IPv6.

This option can be specified multiple times.

The default setting is to bind to all interfaces.

📌 Examples:

Using rpcbind as a runtime parameter:

komodod -rpcbind=127.0.0.1:9704

Using rpcbind as a default value in the Smart Chain’s .conf file:

rpcbind=127.0.0.1:9704

rpcclienttimeout

rpcclienttimeout indicates the number of seconds to wait for an rpc command to complete before killing the process.

📌 Examples:

Using rpcclienttimeout as a runtime parameter:

komodod -rpcclienttimeout=SECONDS

Using rpcclienttimeout as a default value in the Smart Chain’s .conf file:

rpcclientttimeout=SECONDS

rpcconnect

rpcconnect allows the user to connect to komodod and send RPC commands from a host. By default, it is set to localhost.

📌 Examples:

Using rpcconnect as a default value in the Smart Chain’s .conf file:

rpcconnect=127.0.0.1

rpcport

rpcport tells the daemon to listen for RPC connections on the indicated TCP port overwriting the default. The default rpcport for the Komodo(KMD) blockchain is 7771. The default rpcport of a Smart Chain is solely dependant on the -ac_ Antara customization parameters and values used to launch it.

📌 Examples:

Using rpcport as a default value in the Smart Chain’s .conf file:

rpcport=8232

sendfreetransactions

sendfreetransactions instructs the daemon to send transactions as zero-fee transactions if possible. The default value is 0.

📌 Examples:

Using sendfreetransactions as a default value in the Smart Chain’s .conf file:

sendfreetransactions=0

server

server instructs the daemon to accept json-rpc commands. It is enabled by default.

📌 Examples:

Using server as a runtime parameter:

komodod -server=1

Using server as a default value in the Smart Chain’s .conf file:

server=1

spentindex

spentindex instructs a Smart Chain to maintain a full index of all spent transactions (txids).

We recommend that the user manually delete the blockchain data before initiating this parameter.

spentindex is enabled by default on any Smart Chain that utilizes Antara.

📌 Examples:

Using spentindex as a runtime parameter:

komodod -spentindex=1

Using spentindex as a default value in the Smart Chain’s .conf file:

spentindex=1

stopat

stopat stops the chain at a specific block height. This is useful for creating snapshots at a given block height.

📌 Examples:

Using stopat as a runtime parameter:

komodod -stopat=1000000

splitperc

The splitperc parameter allows the user to decide what happens to a UTXO that is successfully able to stake a block in the POS64 staking system (i.e. a Smart Chain started using the -ac_staked Antara customization parameter). This parameter’s value defines the percentage of the staking UTXO value to leave in the same address. The rest of of the staking UTXO value is added to the new UTXO created to the coinbase address.

Examples:

  • -splitperc=0 merges the staking UTXO value and the coinbase value to the coinbase address
  • -splitperc=50 takes half of the staking UTXO value and sends it to the coinbase address
  • -splitperc=100 does not change the staking UTXO

📌 Examples:

Using splitperc as a runtime parameter:

komodod -ac_name=HELLOWORLD -ac_supply=777777 -ac_reward=100000000 -ac_staked=20 -splitperc=50

testnode

The testnode parameter allows the daemon to mine without being connected to any other peers. This is useful for debugging and testing.

If this parameter is not set, the daemon will not attempt to mine blocks unless it has at least one other peer.

📌 Examples:

Using testnode as a runtime parameter:

./komodod -testnode=1

Using testnode as a default value in the Smart Chain’s .conf file:

testnode=1

timestampindex

timestampindex instructs a Smart Chain to maintain a timestamp index for all block hashes.

We recommend that the user manually delete the blockchain data before initiating this parameter.

📌 Examples:

Using timestampindex as a runtime parameter:

./komodod -timestampindex=1

Using timestampindex as a default value in the Smart Chain’s .conf file:

timestampindex=1

txindex

txindex instructs a Smart Chain to track every transaction made on the relevant blockchain.

txindex is enabled by default on all Smart Chains, and is utilized in delayed Proof of Work (dPoW), privacy modules, and Antara.

whitebind

whitelist binds the daemon to a given address and whitelists peers connecting to it.

Use [host]:port notation for IPv6

📌 Examples:

Using whitebind as a runtime parameter:

komodod -whitebind=127.0.0.1:9050

Using whitebind as a default value in the Smart Chain’s .conf file:

whitebind=127.0.0.1:9050