For remote daemons specify the remote daemon’s IP address.Īdd the following lines to your configuration file to start Forknote RPC Wallet with a remote connection: daemon-address=.For local daemons use localhost or 127.0.0.1 as an IP address.
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. You may establish Forknote daemon on both local and remote machines and connect to. Remote connection allows you to bind your Forknote RPC Wallet to a remote Forknote daemon (forknoted). There are two ways to start Forknote RPC Wallet: Start with a remote connection to the Daemon 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 If the operation was successful you will get a corresponding message with your new Bytecoin address.
Note: if exists Bytecoin RPC Wallet will show you the notification and will ask you to provide a different name. –generate-container option tells RPC wallet to generate container file and exit.
MONERO DAEMON SYNC SLOW PASSWORD
is a secret password for the new wallet file.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.walletd -config /home/Downloads/nf -generate-container To generate a new wallet you should run the following command: $. It contains user addresses and private keys required to operate them. Container file is the only file that stores all data required to run your service. To start using RPC wallet you must first generate a container. “server-root” default is the current working directory. Note: “container-file” and “log-file” options are relative to “server-root”. Note: options “container-file” and “container-password” should ALWAYS be set (in either command line or config file mode). Note: config file’s path is relative to current working directory, not server root. See Blockchain options Example of a config file $ cat. If this option is given the options add-priority-node and seed-node are ignoredĬonnect to a node to retrieve peer addresses, and disconnectĭo not announce yourself as peerlist candidate Specify list of peers to connect to only. Specify list of peers to connect to and attempt to keep the connection open Option that allows you to start Forknote RPC Wallet as an in-process nodeĮxternal port for p2p network protocol (if port forwarding used with NAT) Default is current working directory.Īllows you to run Forknote RPC Wallet in testnet. Working directory that you wish to use for Forknote RPC Wallet.
Default Forknote daemon ports are 80Ī name of log file that you want to use for logging. Default value is 8070įorknote daemon (forknoted) address for remote daemon connection infrastructureįorknote daemon (forknoted) port for remote daemon connection infrastructure. Which port to bind Forknote RPC Wallet to. Which address to bind Forknote RPC Wallet to. Please note, Forknote RPC Wallet config file may consist only of these options: Option The command below launches Forknote RPC Wallet with a specific config file: $. Config file allows you to configure your settings only once and use “–config” option further. To configure RPC wallet you can use both command line and config file. Forknote RPC Wallet JSON RPC API page contains detailed description of every method. Forknote RPC Wallet allows you to accept incoming payments, generate an address for each user via Forknote RPC Wallet JSON RPC API and much more. Forknote RPC Wallet is a HTTP server which provides JSON 2.0 RPC interface for Forknote payment operations and address management. This wiki section describes Forknote integration process into your service with Forknote e-commerce solution called Forknote RPC Wallet.
0 kommentar(er)
