-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provider software upgrades CLI #67
Comments
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:
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:
|
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, 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 |
update about the provider's policy
|
@irenegia we should mention also provider can now add also the |
1 similar comment
@irenegia we should mention also provider can now add also the |
Working on the CLI for the provider.
Via CLI
The text was updated successfully, but these errors were encountered: