Closed 0xjona closed 2 years ago
More details:
We discussed about a provider software that via command line will:
cc @turinglabsorg to be sure I am right! :)
@irenegia we calculated a "suggested" price policy for the provider?
There's something we can add as default values? The formula should be something like:
min_price = value * duration * size
right?
Working on this document to make some tests: https://docs.google.com/spreadsheets/d/1zd8hVlL2GA1hTBJoeWm5LXnZLlcesDxdFWH1eB1afs0/edit#gid=0
I understood this in a different way:
value
payment
the value : min_price = value * duration * size
Yes of course, it's like you said, I'm just investigating if we can add some default values to provider software and in the meantime I was trying to understand real use cases.
Provider will add some minimum price for each second of pinning and then the dapp will show this price and will adjust total value accordingly to provider's policy.
Here I'm discussing if we need some default value when the provider runs the node for the first time (10 Wei for example) then the provider will be able to change it of course!
Ah yes, got it!
We can see how much is to storing on other networks and propose something similar (eg, filecoin price). Or the price of some centralised solution (AWS)?
Or, third option: we can set the default to zero! (like providers are doing this at the beginning for free to test their software/hardware and get reputation and then will ask for a price)
Or, third option: we can set the default to zero! (like providers are doing this at the beginning for free to test their software/hardware and get reputation and then will ask for a price)
@irenegia as you proposed default value is 0
:fire:
update about the provider's policy
min_price
: minimum price per second per byte, max_rate
: maximum rate (collateral/payment) max_size
: maximum file size accepted in a proposal
min_price
= 0, max_rate
= slashing_multiplier
(here slashing_multiplier
is a protocol parameter, see "protocol parameters" section), and max_size
= 20MB.@irenegia we should mention also provider can now add also the max_collateral_multiplier
to avoid deals too risky, since hackmd is also updated i think we can now close this issue!
@irenegia we should mention also provider can now add also the max_collateral_multiplier
to avoid deals too risky, since hackmd is also updated i think we can now close this issue!
Working on the CLI for the provider.
Via CLI