You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you agree to open source all work you do on behalf of this RFP under the MIT/Apache-2 dual-license?: Yes
1. What is your project and what problem does it solve? (max 100 words)
This microgrant project involves scoping feasibility of a larger project that would allow anyone to run their own content-addressable server infrastructure (including cloud-native) for serving CAR files (that are also listed in IPNI).
The deliverable will be a fully scoped open source web3 infrastructure tool for teams who want to serve their own data faster, cheaper and without relying on Public Gateways availability.
Potential users include ChainSafe serving Filecoin archival snapshots, Internet Archive, and any web3 provider with IPFS endpoints (Storacha, Pinata, ThirdWeb, etc.)
While other IPFS projects are more focused on IPFS clients or Kubo, this effort would focus on an easy to use and scalable cloud-native approach for teams who want to serve their own content-addressable data. The initial phase of the project will focus on CAR files.
2. a) How is Filecoin used in this project?
This project can ultimately benefit any organization building on Filecoin because it leverages Vasco's knowledge of cloud-native IPFS workflows to improve on an area of the technical stack that many entities in the Filecoin ecosystem do not have time to improve on. It will also encourage ecosystem teams to easily adopt serving content-addressable data where it is not currently used.
This project will involve supporting the CAR file format that is a basic building block of data on Filecoin.
It will also involve packaging this infrastructure as an easy-to-adapt off-the-shelf tool anyone to run, promoting serving of IPFS- / Filecoin-friendly bytestreams on the web and IPFS / Filecoin content addressable data formats used at large.
3. Milestones and Budget
Number
Grant Deliverable
Briefly describe how you will meet deliverable objectives
Timeframe
1.
Architecture Design Spec
Workflow Diagram + Peer Review
2 weeks
2.
Full Proposal
Technical Scope Proposal
1 week
3.
Project Plan
Milestones, Budget
1 week
Total Budget Request: USD $5,000
4. Adoption, Reach, and Growth Strategies
Once this scoping phase has received sufficient feedback from domain experts, a larger grant will be proposed for implementation and open source repackaging and extensive documentation.
5. If accepted, do you agree to share monthly project updates in this Github Issue until the project described here is complete?
Yes, weekly project updates and do regular check-ins with @eshon.
6. Does your proposal comply with our Community Code of Conduct?
Yes.
7. Links and submissions
Previous work: Vasco is a senior JS developer and has worked on IPFS, libp2p and Web3.storage.
Project Name:
Scoping - Repackaging Cloud Native nginx-for-IPFS
Proposal Category:
Developer and data tooling
,Storage
Individual or Entity Name: @vasco
Proposer: @vasco
Project Repo(s): [New Project]
Technical Sponsor: @eshon
Do you agree to open source all work you do on behalf of this RFP under the MIT/Apache-2 dual-license?: Yes
1. What is your project and what problem does it solve? (max 100 words)
This microgrant project involves scoping feasibility of a larger project that would allow anyone to run their own content-addressable server infrastructure (including cloud-native) for serving CAR files (that are also listed in IPNI).
The deliverable will be a fully scoped open source web3 infrastructure tool for teams who want to serve their own data faster, cheaper and without relying on Public Gateways availability.
Potential users include ChainSafe serving Filecoin archival snapshots, Internet Archive, and any web3 provider with IPFS endpoints (Storacha, Pinata, ThirdWeb, etc.)
While other IPFS projects are more focused on IPFS clients or Kubo, this effort would focus on an easy to use and scalable cloud-native approach for teams who want to serve their own content-addressable data. The initial phase of the project will focus on CAR files.
2. a) How is Filecoin used in this project?
This project can ultimately benefit any organization building on Filecoin because it leverages Vasco's knowledge of cloud-native IPFS workflows to improve on an area of the technical stack that many entities in the Filecoin ecosystem do not have time to improve on. It will also encourage ecosystem teams to easily adopt serving content-addressable data where it is not currently used.
3. Milestones and Budget
Total Budget Request: USD $5,000
4. Adoption, Reach, and Growth Strategies
Once this scoping phase has received sufficient feedback from domain experts, a larger grant will be proposed for implementation and open source repackaging and extensive documentation.
5. If accepted, do you agree to share monthly project updates in this Github Issue until the project described here is complete?
Yes, weekly project updates and do regular check-ins with @eshon.
6. Does your proposal comply with our Community Code of Conduct?
Yes.
7. Links and submissions
Previous work: Vasco is a senior JS developer and has worked on IPFS, libp2p and Web3.storage.
https://github.com/vasco-santos
The text was updated successfully, but these errors were encountered: