Flag --network-type and its options' names are confusing

[konradkonrad]

Problem Definition

--network-type currently supports two options: main and test. They are easily confused with the --network-id parameter for the Ethereum chain, i.e. mainnet.
From what I gathered, not even the name "network type" is very descriptive.

I'm putting this issue up for discussion, but here are some proposals:

• --protocol-configuration release|dev
• --environment release|dev

As for the option names, I could also think of

• live|sandbox

Other suggestions welcome!

[andrevmatos]

How about prod|dev or production|development, as in angular/js builds?

[LefterisJP]

Plus one for production|development

[konradkonrad]

Can we also get some eyes on the option name?

[LefterisJP]

Can we also get some eyes on the option name?

operational-configuration?

So --operational-configuration production or --operational-configuration development?

[andrevmatos]

In JS realm, it's called --environment, or --env, not sure if it applies here

[junaidev]

I am using https://github.com/raiden-network/raiden/releases/tag/v0.14.0 build and connected with a private eth net. When registering new token I am getting {"errors": "Registering a new token is currently disabled in the Ethereum mainnet"} while using ./raiden-v0.14.0-linux --config-file config.toml --environment-type development cli