graphprotocol / graphprotocol/graph-node
[Feature] Deterministic file hosting and fetching
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Description
IPFS.cat and file data sources have data availability issues, so they are non-deterministic. We would benefit greatly from a system of file hosting and fetching that can be relied on for availability and can be included in POIs.
Will start as a research project and will likely need involvement from protocol team.
Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.
No response
Some information to help us out
- Tick this box if you plan on implementing this feature yourself.
- I have searched the issue tracker to make sure this issue is not a duplicate.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No implementation files, tests, or entry points are identified. Start by researching the IPFS.cat and file data source availability issues, how POIs depend on file data, and the protocol-team constraints. Done would require a decided design for reliable hosting and fetching that can be included in POIs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100