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

Provide a mechanism to direct the Spark checker network to check a specific SP / CID #184

Open
BigLep opened this issue Oct 24, 2024 · 2 comments

Comments

@BigLep
Copy link

BigLep commented Oct 24, 2024

Idea

Enable an SP or an interested party to have a global check of their retrievability using Spark checkers.

User

SP who wants to work out retrievability issues quickly or to more quickly prove that they are "retrievable".

Why

The reasons for doing this:

  1. Get feedback faster than waiting for Spark's task picker to select a deal for a given SP.
  2. Give diagnostic signal that this is a particularly important check that someone is interested in seeing as much output on as possible as easily as possible.

Other thoughts

  1. Allow the requesting and payment of this is to be done via smart contract, and at least a portion of the payment be shared amongst the checkers of that spark round.
@BigLep
Copy link
Author

BigLep commented Oct 24, 2024

This idea came up in https://www.notion.so/protocollabs/2024-10-24-Meeting-Working-Group-129837df73d48050b03cff92900cd1a0 . I don't know if this is the right place to put this. Feel free to move/close/etc. if not relevant.

@juliangruber
Copy link
Member

Idea:

Once we have tasking in a smart contract, this can work as a bidding market.

Let's say the Spark team bids 0.01 FIL per task (arbitrary number), anyone who wants to prioritize their task (perform a quick check) needs to bid higher than that (say 0.015 FIL). Checkers will prefer high paying tasks. Any checker who wants to absolutely maximize their winnings can also choose tasks below 0.01 FIL.

With this bidding market, we don't create a 2 class system with proper Spark tasks and one-off tasks, where we need to decide what to schedule when.

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

2 participants