Starbase01

• 

  Is filesystem one word or two?

Inspiration

We want two IPIPs: one for onboarding data with HTTP POST, and one for authoring (modifying/pathing) it with HTTP PUT. This allows us to ship most useful onboarding first, and then do authoring as an optional add-on, which services may support, but dont have to (if they are only onboarding to filecoin etc).

cf. https://github.com/ipfs/specs/issues/375

There are many disparate options for uploading data to IPFS. This project aims to contribute in that area.

What it does

This Docker Extension provides a user interface to facilitate onboarding large datasets, or user-content like videos and photos. It also enables mechanics to reward users for participating as "workers" in the docker swarm. The manager of the swarm can earn rewards as a traditional storage provider, while workers earn a share of the profit by facilitating a manager's data redundancy strategy.

There is also a facility for content-creators to earn FIL by adding interesting content /data to the network. At the moment, a creator can earn FIL based on events triggered when someone becomes a GitHub Sponsor or purchases through the GitHub marketplace.

How we built it

I've made some small tweaks to the @codesandbox/sandpack and ipfs-webui projects. The deployment is handled through Docker Extension scaffolding and relies on restic and rest-server to handle encryption and data redundancy.

Challenges we ran into

I am continuing to make changes to the UX and didn't have as complete a demo of the features as I would like in the video. Hopefully the documentation in the source code makes up for that.

Accomplishments that we're proud of

I think this could be a viable product if it gained enough critical mass.

What we learned

There are many disparate options for uploading data to IPFS

What's next for test

Improve UX and add other modes for onboarding besides GitHub Sponsorships.

Built With

• codesandbox
• docker
• excalidraw
• fvm
• golang
• hardhat
• ipfs
• remix
• restic
• typescript