System Requirements and Installation Guide


Raiden is a payment channel implementation which provides scalable, low latency, and cheap token payments for Ethereum.


The preferred way to install Raiden is downloading a self contained application bundle from the GitHub release page.


Download the latest raiden-<version>-linux.tar.gz, and extract it:

tar -xvzf raiden-<version>-linux.tar.gz

The Raiden binary should work on most 64bit GNU/Linux distributions without any specific system dependencies, other than an Ethereum client installed in your system (see below). The Raiden binary takes the same command line arguments as the raiden script.


Download the latest raiden-<version>, and extract it:

unzip raiden-<version>

The resulting binary will work on any version of macOS from 10.12 onwards without any other dependencies.

Or you can use Homebrew to install the most up to date binary:

brew tap raiden-network/raiden
brew install raiden

An Ethereum client is required in both cases. The Raiden binary takes the same command line arguments as the raiden script.


You will need to have an Ethereum client installed in your system. Alternatively, you can skip the setup of an ethereum node and use the –eth-rpc-endpoint argument to remotely use an ethereum node of your choice.

Now you are ready to get started.

For developers

If you plan to develop on the Raiden source code, or the binary distributions do not work for your system, you can follow these steps to install a development version.


Additional dependencies for development installations

  • You need to make sure that your system has solc, the ethereum solidity compiler installed. Refer to its documentation for the installation steps.
  • You will also need to obtain the system dependencies for pyethapp.
  • For running raiden smoketest, you will need to have synapse installed. Run ./tools/ (synapse needs tk as a dependency).

Installation from source

Clone the repository:

git clone

Navigate to the directory:

cd raiden

It’s advised to create a virtualenv for Raiden (requires python3.6) and install all python dependencies there.

After you have done that you can proceed to install the dependencies:

pip install -c constraints.txt --upgrade -r requirements-dev.txt
python develop

You will also need to connect your Ethereum client to the Ropsten testnet. See below for guidelines on how to connect with both Parity and Geth.


Please refer to the detailed step-by-step guide for setting up a macOS development environment.


Please refer to the nix setup guide for setting up a development environment using the nix package manager.

Requirements for Safe Usage

In order to use Raiden correctly and safely there are some things that need to be taken care of by the user:

  • Layer 1 works reliably: That means that you have a local Ethereum node, either geth or parity, that is always synced and working reliably. If there are any problems or bugs on the client then Raiden can not work reliably.
  • Unique account for Raiden: We need to have a specific Ethereum account dedicated to Raiden. Creating any manual transaction with the account that Raiden uses, while the Raiden client is running, can result in undefined behaviour
  • Raiden account has sufficient ETH: Raiden will try to warn you if there is not enough ETH in your Raiden account in order to maintain your current open channels and go through their entire cycle. But it is your job as the user to refill your account with ETH and always have it filled.
  • Persistency of local DB: Your local state database is located at ~/.raiden. This data should not be deleted by the user or tampered with in any way. Frequent backups are also recommended. Deleting this directory could mean losing funds.
  • Raiden Always online: Make sure that your node is always working, your network connection is stable and that the Raiden node is always online. If it crashes for whatever reason you are responsible to restart it and keep it always online. We recommend running it inside some form of monitor that will restart if for some reason the Raiden node crashes.
  • Ethereum Client Always Online: Make sure that your Ethereum client is always running and is synced. We recommend running it inside some form of monitor that will restart if for some reason it crashes.
  • Ethereum Client can not be changed: Swapping the Ethereum client while transactions are not mined is considered unsafe. We recommend avoiding switching Ethereum clients once the Raiden node is running.
  • Never expose the Raiden REST API to the public: For Raiden’s operation, the client needs to be able to sign transactions at any point in time. Therefore you should never expose the Raiden Rest API to the public. Be very careful when changing the –rpc and –rpccorsdomain values.
  • Be patient: Do not mash buttons in the webUI and do not shut down the client while on-chain transactions are on the fly and have not yet been confirmed.

Firing it up

Using geth

Run the Ethereum client and let it sync:

geth --syncmode fast --rpc --rpcapi eth,net,web3,txpool


When you want to use a testnet add the --testnet or --rinkeby flags or set the network id with --networkid directly.

Unless you already have an account you can also create one in the console by invoking personal.newAccount().

If problems arise for above method, please see the Ropsten README for further instructions.

Then launch Raiden with the default testnet keystore path:

raiden --keystore-path  ~/.ethereum/testnet/keystore

Using parity

Run the client and let it sync:

parity --no-warp --jsonrpc-apis=web3,eth,net,parity


When you want to use a testnet add the --chain ropsten or --chain kovan flags or set the network id with --network-id directly.


Parity sometimes loses its historical DB (potentially after updates). Due to this some events might be lost which will result in Raiden not being able to fetch all events. Therefore it is recommended to make sure to have Parity fully synced with the –no-warp option.

After syncing the chain, an existing Ethereum account can be used or a new one can be generated using parity-ethkey. After account creation, launch Raiden with the path of your keystore supplied:

raiden --keystore-path ~/.local/share/io.parity.ethereum/keys/test

Using –eth-rpc-endpoint/Infura


Raiden may fail during restarts when Infura is used. This can happen because Raiden does not know about transactions in the memory pool and therefore new transactions might reuse these nonces. This will lead to a node crash.

In order to use Raiden with an rpc-endpoint provided by an Infura Ethereum node, sign up with Infura to get an API token. After that you can start using Raiden on Ropsten directly:

raiden --keystore-path  ~/.ethereum/testnet/keystore --eth-rpc-endpoint "<yourToken>"


When you want to use a testnet you need to update the URL of the infura endpoints, e.g. for the ropsten testnet use<yourToken>

Select the desired Ethereum account when prompted, and type in the account’s password.

See the API walkthrough for further instructions on how to interact with Raiden.