docs: deal scraper RFC #631
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
th7nder
requested changes
Dec 11, 2024
rfcs/004-deal-scraper.md
Outdated
|
|
||
| ## Abstract | ||
|
|
||
| This RFC proposes the design and functionality of an application to map `piece_cids` to their respective owners, identified by [Peer ID][1]s, in the Polka-Storage ecosystem. |
There was a problem hiding this comment.
I'm wondering, who needs that from the business perspective at this point.
When a Storage Client is making a deal, they know with whom, so they should know where their file is stored.
The only thing they need is to resolve PeerID to a Multiaddress and then connect to the SP, download the file and that's it.
Not sure who the user of it would be.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds an RFC for the on-chain deal information scraper, which maps Peer IDs to piece_cid's. The application will need to maintain a database that holds these mapping, the database is not mentioned in this RFC but should be considered when implementing. This is an initial draft, I will do some testing to check if this will work.