Iridium core daemon overview

Iridium (IRD) core daemon is the center of Iridium system. This daemon is also called “node”. It provide a full Iridium (IRD) Blockchain synchronization, handle the p2p decentralized blockchain, verify Transactions, adjust the difficulty, provide a console for simple tasks and also a JSON/RPC Api to interract with the Iridium network.

Simply run:

$ ./iridiumd

Your node will start syncing the Iridium (IRD) Blockchain.
Embedded help is also available:

$ ./iridiumd --help



The Iridium (IRD) daemon will look for an iridiumd.conf file as default if none is specified at the same level directory. The data dir where the blockchain is stored will be ~/.iridium on linux/mac and %appdata%/iridium on Windows

--help                 # Produce help message
--version              # Output version information
--os-version           # Output system information
--data-dir             # Specify Data directory to store the blockchain, default to ~/.iridium or %appdata%/iridium on windows
--config-file          # Specify configuration file, default to iridiumd.conf

Example:

$ ./iridiumd --data-dir /home/ird/data --config-file /home/ird/iridiumd.conf


These settings can be setup either on command line arguments or in a configuration file, see below for a configuration file example.

--log-file             # Specify a log file, default to iridiumd.log
--log-level            # default log level = 2
--no-console           # Disable daemon console commands
--testnet              # Used to deploy test nets.
                       # Checkpoints and hardcoded seeds are ignored, network id is changed.
                       # Use it with --data-dir flag. The wallet must be launched with --testnet flag.
--rpc-bind-ip          # default to 127.0.0.1 
--rpc-bind-port        # default to 13007 
--p2p-bind-ip          # Network Interface for p2p protocol, default is all (0.0.0.0)
--p2p-bind-port        # Port for p2p network protocol, default is 12007
--p2p-external-port    # External port for p2p network protocol (if port forwarding used with NAT)
--allow-local-ip       # Allow local ip add to peer list, mostly in debug purposes
--add-peer             # Manually add peer to local peerlist
--add-priority-node    # With this parameter(s) could be set list peers to connect to
                       # and attempt to keep the connection open
--seed-node            # Connect to a node to retrieve peer addresses, and disconnect
--add-exclusive-node   # Specify list of peers to connect to only.
                       # If this option is given the options add-priority-node and seed-node are ignored
--hide-my-port         # Do not announce yourself as peerlist candidate
--extra-messages-file  # Specify file for extra messages to include into coinbase transactions
--start-mining         # Specify wallet address to mine for
--mining-threads       # Specify mining threads count


Example:

$ ./iridiumd --data-dir /home/ird/data --config-file /home/ird/iridiumd.conf --testnet --no-console --log-level 3 --log-file /home/ird/iridiumd.log


A configuration file can be used, the default name is iridiumd.conf and looks like this:

$ cat /home/ird/iridiumd.conf
log-level=2
log-file=/home/ird/log/iridiumd.log
p2p-bind-ip=123.45.67.89
p2p-bind-port=12001
rpc-bind-port=13001
no-console=1

Now, it's time to play with the rpc api: The Iridium Core Daemon RPC calls