Configure Forknote RPC Wallet

To configure RPC wallet you can use both command line and config file. Config file allows you to configure your settings only once and use “–config” option further. The command below launches Forknote RPC Wallet with a specific config file:

$ ./walletd --config /home/Downloads/myconfig.conf

To get help on available options run:

$ ./walletd -h

Please note, Forknote RPC Wallet config file may consist only of these options:

Note: config file’s path is relative to current working directory, not server root.

Note: options “container-file” and “container-password” should ALWAYS be set (in either command line or config file mode).

Note: “container-file” and “log-file” options are relative to “server-root”. “server-root” default is the current working directory.

Generate a new wallet

To start using RPC wallet you must first generate a container. Container file is the only file that stores all data required to run your service. It contains user addresses and private keys required to operate them. Make sure to backup this file regularly.

<mycontainer> is the container file name and a path to it (relative or absolute); path is optional in this argument, specifying only a container’s name will result in new file located in the same folder as RPC Wallet

<mypass> is a secret password for the new wallet file. Whichever you like;

Note: if <mycontainer> exists Bytecoin RPC Wallet will show you the notification and will ask you to provide a different name.

If the operation was successful you will get a corresponding message with your new Bytecoin address. At the same time Bytecoin RPC Wallet will save your container on the local disk (in the same folder where Bytecoin RPC Wallet is located) and shut down

Start Forknote RPC Wallet

There are two ways to start Forknote RPC Wallet:

Start with a remote connection to the Daemon

Remote connection allows you to bind your Forknote RPC Wallet to a remote Forknote daemon (forknoted). You may establish Forknote daemon on both local and remote machines and connect to. Such type of connection allows you to start Forknote RPC Wallet on a relatively slow machine while heavy loaded daemon is going to work on a separate powerful server.

For local daemons use localhost or 127.0.0.1 as an IP address.

For remote daemons specify the remote daemon’s IP address.

Default Forknote daemon ports are 8080 and 8081.

Add the following lines to your configuration file to start Forknote RPC Wallet with a remote connection:

daemon-address=<remote_ip>
daemon-port=8080

Note: Forknote daemon (forknoted) should be running at the moment RPC wallet is starting in a remote connection mode.

Note: Forknote RPC Wallet will still provide some functionality even if Daemon server fails. For example, you will be able to generate addresses for your users.

Start as in-process node

You can also start Forknote RPC Wallet with an in-process node. This allows you to start RPC Wallet out-of-box with no external daemon required. You will get a fully functional node for Forknote network inside Forknote RPC Wallet. You don’t have to download or install anything besides Forknote RPC Wallet. This approach will help reduce the overheads required for infrastructure maintenance.

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

$ ./walletd --config /home/Downloads/myconfig.conf --local

Run Forknote RPC Wallet

Forknote RPC wallet can be started in both daemon and console modes.

Daemon mode - Forknote RPC Wallet is launched in the background, while you can continue to work with a console window.