raiden-network / raiden

Raiden Network
https://developer.raiden.network
Other
1.84k stars 378 forks source link

Change EVERY scenario to default fee 0 of token network address: "0x62083c80353Df771426D209eF578619EE68D5C7A" #4890

Closed christianbrb closed 5 years ago

christianbrb commented 5 years ago

Original Issue

Once mediation fee default is implemented #4731 then change EVERY scenario to default fee 0 of token network address: "0x62083c80353Df771426D209eF578619EE68D5C7A"

Analysis from https://github.com/raiden-network/raiden/issues/4890#issuecomment-534161673

Solution

palango commented 5 years ago

@czepluch How do I do that in a scenario?

czepluch commented 5 years ago

@palango the nodes option in the scenario files takes all the same arguments as the raiden node itself, so you should be able to set it there if I understand this issue correctly.

So:

nodes:
  mode: managed
  count: 2
  raiden_version: local

  default_options:
    gas-price: fast
    environment-type: development
    enable-monitoring: true
    YOUR_ARGUMENT_HERE: 0
palango commented 5 years ago

@czepluch @ulope Is it possible to give two arguments? In my example (for the flat fees) I need something like:

    flat-fee: 0x62083c80353Df771426D209eF578619EE68D5C7A 100
czepluch commented 5 years ago

@palango I don't get any complaints from the SP when running like that just now, but can't verify if it actually works as intended yet.

czepluch commented 5 years ago

Alright. I take that back. It doesn't seem to work with multiple arguments right now.

palango commented 5 years ago

I got this while trying: Error: Invalid value for "--flat-fee": Address must be EIP55 checksummed

czepluch commented 5 years ago

Yeah, same here.

czepluch commented 5 years ago

But according to .stdout it seems to have tried to start Raiden with the correct arguments.

Dominik1999 commented 5 years ago

ok,

that leads to the following: