paritytech / paritytech/web3-storage
Areas of work to be done
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 12
- Forks
- 3
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 33
Description
- Agreement Management
- What all parameters are needed for having a right agreement? For example Network Bandwidth and throughput support
- Matching Agreements
- Can we speed up accepting agreements
- What if agreements are not matched automatically
- Deployment Plan
- Who will be our Storage providers?
- What should be the storage provider min requirements?
- Cost Benefit analysis for the Storage Provider
- Hardware configuration of the Storage Providers and the cost associated with it
- Earning potential
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 files, tests, or entry points are identified. Start by turning the agreement management, deployment plan, storage-provider requirements, and cost-benefit questions into explicit project requirements. Done would mean these areas have agreed answers or documented decisions, including agreement parameters, matching and acceptance, provider criteria, hardware costs, and earning potential.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100