Iridium Wallet Daemon

The Iridium RPC Wallet (iridium_walletd) is a server that provides a JSON 2.0 RPC API for transactions and address management. You can call it from the command line or by it's RPC API. a configuration file can also be made to avoid typing recurrent option.

you can always call the online help by typing

 $ ./iridium_walletd --help

Even in case of a non running daemon, the Iridium RPC Wallet still provive some basic functions as generating a new wallet and showing a wallet address

To start using the RPC wallet (the iridium_walletd binary) you must first generate a new wallet.
A wallet is called a container for the binary.
Container file is the only file that stores all data required to run services.
It contains the user addresses and private keys.
Make sure to backup this file regularly.

To generate a new container (a unique Iridium wallet file), run the following command :

 $ ./iridium_walletd --container-file=mywallet --container-password=password --generate-container

or shorter :

 $ ./iridium_walletd -w mywallet -p password -g

• mywallet is the name of the wallet file ¹⁾.
• password is the secret password of the new wallet file. Remember it, write it, save it : there is no way to recover it.
• the –generate-container or -g option tell iridium_walletd to generate container file and exit.

If the operation is successful, you will get message with your new Iridium address.²⁾

At the same time Iridium RPC Wallet will save your wallet file on the local disk (in the same folder where Iridium RPC Wallet is located) and shut down.

To show a container address (a unique Iridium wallet), run the following command :

 $ ./iridium_walletd --container-file=mywallet --container-password=password --address

or shorter :

 $ ./iridium_walletd -w mywallet -p password --address

• mywallet is the name of the wallet file ³⁾.
• password is the secret password of the new wallet file. Remember it, write it, save it : there is no way to recover it.
• the –address option tell iridium_walletd to show the address of the wallet and exit.

If the operation is successful, you will get message with the address of the asked Iridium wallet.

There are two ways for running the Iridium RPC Wallet :

• Connect to a daemon running on a distant server.
• Run as stand-alone by using the build-in daemon

This allow you to bind your Iridium RPC Wallet ( iridium_walled ) to an Iridium daemon ( iridiumd ) that is already running on a local or a remote machines.

This kind of connection allow you to start Iridium RPC Wallet on a slow machine while the daemon is going to work on a separate server and handle requests from network and some Iridium RPC Wallet or Iridium simple wallet.

For a local already running daemon, you can use either localhost or 127.0.0.1 as IP address.
For a remote daemons, specify the remote daemon's IP address⁴⁾. Default Iridium daemon ports are 12007(p2p) and 13007(RPC).

Run the following command to start an Iridium RPC Wallet with a remote connection:

 $ ./iridium_walletd -w mywallet -p password --daemon-address=remote_ip --daemon-port=13007

This provide you an out-of-box RPC Wallet with nothing else needed.
You will get a fully functional daemon for Iridium network inside Iridium RPC Wallet.
This is also the faster method for developping applications around Iridium.

Use the following command to start Iridium RPC Wallet with an in-process node

 $ ./iridium_walletd -w mywallet -p password --local

Now, you know how to create a wallet, connect to a remote node or use the iridium_walletd as standalone (wallet + daemon).

it's a good time to save your keys: Iridium (IRD) wallets use one “Master” key and two “Spend” keys: one “View only” key and one “View and spend” key.

• The “Master” Key is called “viewSecretKey”, you can retrieve it by querying the JSON-RPC API with the getViewKey method.
• The Spend keys (spendPublicKey & spendSecretKey) are available by querying the JSON-RPC API with the getSpendKeys method.

The Iridium RPC wallet and it's options can be started with both the command line and a configuration file.
The configuration file can be used for the “permanent” options.

When using a configuration file, the container-file and the container-password options have to be found in that file.
For an “exchange” usage, you surely want to intensively use the RPC queries.
In that case, just generate a dumb wallet and use it in the configuration file.

Options passed to the command line has priority over a configuration file : In this example, the rpc port will be binded to 14008 :

$ cat walletd.conf
bind-port=14007
container-file=mywallet
container-password=password
local=yes
log-level=2

 $ ./iridiumd_walletd -c walletd.conf --data-dir ~/walletdDB  --testnet --bind-port 14008

Some options are not available in config file.

iridium_walled is setup ? you can now start to query it : The Iridum Wallet Daemon RPC calls