Table of Contents
Hyperfiles ⛓️🧠 is a self-organizing universal knowledge graph.
A Hyperfile consists of two linked objects:
Data objects are published off-chain on a P2P decentralized storage layer, IPFS.Reference objects corresponding to each data object are published on-chain.Structuring references makes the much larger data objects composable and able to be seamlessly recombined between different apps. Each data object can also function as its own standalone app when handled inside of a capable BOS gateway (e.g. **everything.dev)**.
https://x.com/HyperfilesOrg/status/1730638052694126925?s=20
App
Docs
Hyperfiles [in progress] | Notion
Code
We made a demo showing how to create and interact with a few simple file types and input/output (IO) sources. Check out the 3min video to get familiar with the simple interface.
https://youtu.be/oR87ea-31ro?si=7q4VLtTqwmEOgsuR
<aside> ⚠️ CAUTION: encryption and private data storage have not yet been implemented in Hyperfiles. Please do not publish any sensitive or proprietary information. Feel free to reach out to us via Telegram in the Hyperfiles “User Support” channel if you have any questions.
</aside>
Currently, all data objects published using Hyperfiles are stored on IPFS. References are stored using the socialDB contract on NEAR Protocol to facilitate on-chain data availability & verifiability for anything from simple text docs to drawings/images/figures and even more complex data types.
*Sidenote: Hyperfiles data objects and references function in an analogous manner to NEAR Protocol transactions and receipts, respectively.
Let’s follow the same steps shown in the demo video to publish our first dataset.
To use the Hyperfiles App you will need:
a Near wallet (an account that only you control), and
$NEAR tokens to save references on-chain.
Here’s a 2min video showing how easy it is to create a NEAR account.
[Credit: @nearinnov8](https://youtu.be/o7P9AoNe5kU?si=6oa9x2HC6Mf82DLT)
Credit: @nearinnov8