We use Dat in Beaker[1] to host sites and files from the user's device. It's a pretty interesting protocol. It's developed by Code for Science[2], a 501(c)(3) l

We use Dat in Beaker[1] to host sites and files from the user's device. It's a pretty interesting protocol. It's developed by Code for Science[2], a 501(c)(3) led by Max Ogden[3] and with protocol dev led by Mafintosh[4]; their mission is to help with archival of science and civic data. Some interesting properties: 1. It uses a BitTorrent-style of swarm, but primarily to sync signed append-only logs, which are in fact flattened Merkle Trees (similar to Certificate Transparency). The Dat archives are addressed by public keys. The tree is used to enforce the append-only constraint by making it easy to detect if the history has been changed by the author. 2. The "Secret Sharing" feature. The public key of a Dat archive is hashed before querying or announcing on the discovery network, and then the traffic is encrypted using the public key as a symmetric key. This has the effect of hiding the content from the network, and thus making the public key of a Dat a "read capability": you have to know the key to access its files. There's a reference implementation in JS available at https://github.com/datproject/dat-node https://github.com/datproject/dat-node, and a fair number of tools being built around it. 1 https://beakerbrowser.com/ https://beakerbrowser.com/ 2 https://datproject.org/ https://datproject.org/ 3 https://twitter.com/denormalize https://twitter.com/denormalize 4 https://twitter.com/mafintosh https://twitter.com/mafintosh