Client-server stack for Web3
There are currently two ways to interact with Web3 storage solutions:
- Through a pinning service and a gateway: the advantage is that files are served through URLs, an app can then access the files with conventional methods, e.g. simply putting a picture in
<img src="gateway.example.com/Qm...">. The disadvantage is that there is a subscription payment associated with pinning services. Also this is not really decentralized! - Turn the device to a full IPFS node: this model works beautifully in Brave desktop browser as an example, and makes sense for laptop and PC since they normally have large HDDs. It's much harder on mobile devices, however, biggest hurdle is to have Apple on board with the idea of relaxing file system access in iOS! Even if all goes well, a mobile device is NOT a good candidate for hosting the future Web! They get lost easily and are resource constrained (battery, memory).
box aims to address these issues by creating a third alternative: Personal Server
A personal server is a commodity hardware (PC, Raspberry Pi, etc.) that's kept at home vs. in pocket. It helps with actual decentralization, also saves money since people pay once for HDDs and own them forever, no monthly charge! From privacy perspective, it guarantees that data doesn't leave the premise unless user specifically wants to (e.g. sharing).
To achieve this, we are developing protocols to accommodate client-server programming with minimal effort on developer's side:
- File Protocol: Send and receive files in a browser or an app (stage: prototype)
- Data Protocol: Database interface over at client-side; facilitates describing linked JSON documents and having them saved/retrieved (stage: design draft)
- AI Protocol: Map-Reduce stack for distributed processing (stage: ideation)
An app talks with the server(s) by invoking APIs from @functionland/fula library. The Fula library abstracts away the protocols and libp2p connection, instead exposes APIs similar to MongoDB for data persistence and S3 for file storage.
On the server side, data or file will be saved on a private IPFS instance. There is also a public IPFS instance which comes to play in sharing: when the end user requests to share some data, an encrypted copy will be saved on the public IPFS network, anyone with whom the key has been shared can access the data.
The box stack can provide backup guarantees by having the data pinned on multiple servers owned by the user. However, in cases that the user needs absolute assurance on data longevity, e.g. password records in a password manager app or scans of sensitive documents, the encrypted data can be sent over at Filecoin blockchain.
| Name | Description |
|---|---|
| protocols | Libp2p protocols for the box stack |
| beast | Server implementation in Go |
| mobile | Client library in golang with gomobile interface comptibility for generating IOS and Android apps |
- https://filecoin.io/blog/posts/249k-for-17-projects-from-dorahacks-filecoin-grant-hackathon/
- https://dev.to/fx/google-photos-open-source-alternative-with-react-native-80c
- https://hackernoon.com/were-building-an-open-source-google-photos-alternative-with-react-native-zw4537pa
- https://crustnetwork.medium.com/crust-network-and-functionland-partnering-up-on-web3-developer-tools-309e41074fc5