Skip to content
This repository has been archived by the owner on May 13, 2022. It is now read-only.

How much ETH should the Wizard require? #205

Closed
fredo opened this issue May 13, 2020 · 4 comments
Closed

How much ETH should the Wizard require? #205

fredo opened this issue May 13, 2020 · 4 comments
Labels
Prio 1 Include in Sprint Backlog

Comments

@fredo
Copy link
Contributor

fredo commented May 13, 2020

This is an issue to discuss how much ETH should be required to run the wizard.

Currently we ask for the upper bound assuming Closing 4 channels and buyin the maximum amount of RDN and DAI which leads to 0.18 ETH which is quite a high entry barrier.

To lower this amount, we could have some options:

  • Do not assume that the user will have 4 channels
  • Only allow to buy a fixed amount of RDN and DAI (Maybe only in the first run. later the user could top up as he wishes)

IMHO in would be okay to not calculate costs for closing the channels in as the user can top up later at any time. This could even be done in the WebUI. Also the wizard on further runs (2nd 3rd and so on) could check for open channels and compare the current eth balance against what would be needed to close all channels he has. All in all topping up ETH is not big of a deal since this can happen while Raiden is running.

In the first run we could also go with low amounts of RDN and DAI to provide a low entry barrier. Once the user likes using raiden we could give him the opportunity to exchange more (or even variable amounts) in further runs of the wizard.

Example:
10 RDN ~ 0.00565 ETH
5 DAI ~ 0.02578 ETH
2 USD ~ 0.010602 ETH transaction fee

Total: 0.042032 ETH
This would end up in ~ 0.05 ETH. @Dominik1999 What is you opinion here?

@fredo
Copy link
Contributor Author

fredo commented May 13, 2020

Due to price fluctuation we could also calculate transaction costs for the DAI and RDN swap on the spot and make the ETH price variable

@Dominik1999
Copy link
Contributor

Dominik1999 commented May 13, 2020

Thanks @fredo !

We should definitively decrease that amount. We also discussed that in our Biz Dev Meeting together with @czepluch and Luis (can't find GH name?).

We might come up with more convenient numbers by minimizing all three factors - channels to be opened, RDN needed and DAI needed

  • Channels: We need to hold ~0.025 ETH for every channel we want to open. Raiden does not allow us to open a channel otherwise. see below

  • RDN: We should not let the user chose how many RDN she will swap. 10 is a good number if we expect the user not to use a Monitoring Service. (with 2 DAI in the channel that might not be needed)

  • DAI: We can even go for for a lower amount of DAI.

Gas needed to operate Raiden

from raiden.utils.gas_reserve import _get_required_gas_estimate
from raiden_contracts.contract_manager import gas_measurements

gas = _get_required_gas_estimate(gas_measurements(version="0.37.0-b3"), new_channels=4)
print(f"{gas:,d}")

leads to 6,559,056 which is ~0.07 ETH at 10 GWEI

# 1 GWei:
>>> 6559056 * 1e9 / 1e18
0.006559056

# 10 GWei:
>>> 6559056 * 10e9 / 1e18
0.06559056

# 20 GWei:
>>> 6559056 * 20e9 / 1e18
0.13118112

@Dominik1999
Copy link
Contributor

Dominik1999 commented May 13, 2020

We decided to have 0.11 ETH for the user and fixed amounts to swap 10 RDN and 3 DAI

3 Channel         0.075 ETH
10 Raiden T   0.00565 ETH
5 DAI              0.015468 ETH
2 $ for             0.01 ETH

@Dominik1999
Copy link
Contributor

@fredo can you specify the necessary changes in back- and frontend and create issues?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Prio 1 Include in Sprint Backlog
Projects
None yet
Development

No branches or pull requests

2 participants