Mainnet smoketest

[hackaugusto]

Abstract

The current implementation of the smoketest starts a completely fresh test environment, with a private blockchain, matrix servers, and newly deployed smart contracts. This is a good test to simple integration errors for development but it is not useful to check if a release is sane.

Motivation

We had a small configuration problem on a RC https://github.com/raiden-network/raiden-contracts/pull/1380 , which was only caught by manual testing. To detect such errors faster a sanity check for the production configuration is needed.

This check needs to be used by the CI to validate a new release/deploy. After the environment is created, but before the packages are deployed, the sanity check should be executed to validate the mainnet configuration. Thus speeding up the manual labor of testing configuration.

Specification

Add or modify an existing command to start a node with mainnet settings. The goal here is to sanity check the configuration, so the node should validate the smart contract addreses, their byte code, and make sure it can communicate with the services.