paritytech / paritytech/web3-storage
Bandwidth metering
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13
- Forks
- 3
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 33
Description
What happens if some data gets downloaded too much? Should we have some mechanism by which the providers can convince the data owner that many people downloaded their data? Some approaches:
-
We could've users pay for downloads. If there are relatively few service providers, then this could be done using OPRF tokens like privacy pass.
-
We could've uploaders authorise downloads, using either blind signatures or maybe blind OPRF token like privacy pass.
-
If uploaders have a shitcoin then they could pay for downloads in both DOTs and in their shitcoin, so that if the service sees much usage, then the shitcoin might go up in value.
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
The issue names no files, tests, or entry points and presents several possible designs rather than a bounded change. It would need a decided approach and project-specific entry point before a newcomer could define or verify completion.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain, cryptography, payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100