Skip to content
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

Closed
0xjona opened this issue Jul 12, 2022 · 9 comments
Closed

Provider software upgrades CLI #67

0xjona opened this issue Jul 12, 2022 · 9 comments
Assignees

Comments

@0xjona
Copy link
Collaborator

0xjona commented Jul 12, 2022

Working on the CLI for the provider.

Via CLI

  • Price policy
  • IPFS size check
  • Auto-accept
  • [remote pinning key]
@0xjona 0xjona moved this to 📫 in retriev.org Jul 12, 2022
@0xjona 0xjona moved this from 📫 to ToDo in retriev.org Jul 12, 2022
This was referenced Jul 12, 2022
@irenegia
Copy link
Collaborator

irenegia commented Jul 12, 2022

More details:

We discussed about a provider software that via command line will:

  • Set up a node on a remote server (always on-line)
  • Sign up to the protocol
  • Create a price policy, that is the minimum value accepted as payment (per byte and per unit of times)
  • For each deal proposal received, will check if the params there satisfy the policy. If yes, the proposal is automaticlaly accepted.

cc @turinglabsorg to be sure I am right! :)

This was referenced Jul 12, 2022
turinglabsorg added a commit that referenced this issue Jul 14, 2022
@turinglabsorg turinglabsorg moved this from ToDo to Implementation in retriev.org Jul 14, 2022
turinglabsorg added a commit that referenced this issue Jul 14, 2022
@turinglabsorg
Copy link
Collaborator

@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

@irenegia
Copy link
Collaborator

I understood this in a different way:

  • the provider has its own policy where value
  • in the app, when a client create a proposal we suggest as payment the value : min_price = value * duration * size

@turinglabsorg
Copy link
Collaborator

turinglabsorg commented Jul 15, 2022

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!

@irenegia
Copy link
Collaborator

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)

turinglabsorg added a commit that referenced this issue Jul 18, 2022
Repository owner moved this from Implementation to Validation in retriev.org Jul 18, 2022
@turinglabsorg turinglabsorg reopened this Jul 18, 2022
@turinglabsorg
Copy link
Collaborator

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 🔥

turinglabsorg added a commit that referenced this issue Jul 18, 2022
turinglabsorg added a commit that referenced this issue Jul 19, 2022
turinglabsorg added a commit that referenced this issue Jul 19, 2022
turinglabsorg added a commit that referenced this issue Jul 21, 2022
@irenegia
Copy link
Collaborator

update about the provider's policy

  • Each provider has a deal policy that states:
    - the min_price: minimum price per second per byte,
    - the max_rate: maximum rate (collateral/payment)
    - the max_size: maximum file size accepted in a proposal
    • The default values are min_price= 0, max_rate = slashing_multiplier (here slashing_multiplier is a protocol parameter, see "protocol parameters" section), and max_size= 20MB.

@turinglabsorg
Copy link
Collaborator

@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!

1 similar comment
@turinglabsorg
Copy link
Collaborator

@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!

turinglabsorg added a commit that referenced this issue Jul 28, 2022
@turinglabsorg turinglabsorg moved this from Validation to Done in retriev.org Aug 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants