Hyperfiles

Organize everything. ⛓️🧠 Hyperfiles is an attestation-based onchain knowledge graph for #DeSci and impact evaluation. Publish a file to get started. #FOSS #BOS

[Hyperfiles @HyperfilesOrg]

We're creating a semantic data model to promote composability and standardization across knowledge domains.

Deploying early versions of curated schema libraries this week using the revised Hyperfiles meta-schema specification.

h/t @eas_eth for inspiration & encouragement 🎩🙏

[Hyperfiles @HyperfilesOrg]

@ShitzuCommunity @chronear @ilblackdragon Exactly.

[Hyperfiles @HyperfilesOrg]

Our patron saints expanding the network 🫡🚧👷‍♂️
#build #hyperfiles #hyperbuild

[NearBuilders @NearBuilders]

Join us Wednesday at 18:00 UTC for a riveting space!

Our growing community of builders will help you create a blueprint & launch your own construction site 🚧 #BUILD

Explore opportunities to earn rewards by contributing to impactful projects 👷 #OpenWeb

https://t.co/1tNrS8eogy

[DAO Spring @DAOcember]

Week 5 of DAO Spring! 😱

Unsurprisingly, we got 2 more great sessions:
- First one will help you pick the right tools for your DAO, w/ @coolhorsegirl2 & @flow_science
- Second one will help you resolve whatever issue you got in your DAO w/ @gospelofchange & @TorstenGoerke

[Hyperfiles @HyperfilesOrg]

👀👀

[Jerri 🌱DeFi to ReFi to Regen 🌎🍄🧠 @jerri_nft]

@AltCryptoGems @AltCryptoTalk @nansen_ai @cherrypick_xyz @rabbithole_gg @zealy_io @l2beat @dexscreener @artemis__xyz @DeBankDeFi @Footprint_Data Wait till you see @HyperfilesOrg games always changing in web3

[Jaswinder Singh @jassification]

I am looking to interview developers using @NEARProtocol's QueryAPI platform for their Bos apps or any other front end or back end apps.

My DMs are open and your time will be compensated if we end up doing the interview.
Thanks.

[Jimi.tgn @JimiCohen]

I just GROWnated to @HyperfilesOrg 💚

Their vision for on-chain reference objects and indexed data collaboration can transform information sharing for science, impact evaluation, and marketplace functionality✊

Stop by their grant and GROWnate!
#GG20

[Hyperfiles @HyperfilesOrg]

@JimiCohen You Ser are a true gem 💎 thank you for the GROWnation! 🙌🙌

[Hyperfiles @HyperfilesOrg]

HyperTrees are taking shape ✨🌲🌳🌴💫

Hyperstructures made of physical connections linking regenerative places through both space and time 💯
#LetsGROW

[Treegens @treegens]

The 4th batch of Treegens go toooooo...
31.@pacobacpac
32.@ibenxjean
33.@TasheeQev
34.@HyperfilesOrg
35.@ODymarski
36.@AyraFrey41839
37.@BH1991
38.@Get14et
39.@griffgreen
40.@joseebasanta
Let's keep the positive Treenergy flowing! 
#LetsGROW

[Hyperfiles @HyperfilesOrg]

@treegens @pacobacpac @ibenxjean @TasheeQev @ODymarski @AyraFrey41839 @BH1991 @Get14et @griffgreen @joseebasanta Whaaattt!!!! Let's grow! 🪴🌱🤩

[Dawn Kelly @run4pancakes]

@dabit3 @gitcoin This one right here:

[Hyperfiles @HyperfilesOrg]

"Organize Everything" is our tagline for a reason. 💯

Take a look at these explorations of how Hyperfiles can be used for collaborative data governance that our lead builder @flow_science wrote about today.

https://t.co/B8IlN4a7Ba
https://t.co/59pC1GvWn9
https://t.co/cAG9ynLDZn

[Elijah Spina, PhD (🧬,🌿) @flow_science]

Thanks for sharing I'll add this to my reference lib.

Unfortunately, from a cursory review their design is, well, feckless. Their + your claims about it (sorry, nothing personal) fall short in a few key areas.

To justify my harsh criticism I felt obligated to explain my conclusions in excruciating detail below and to compare them to the leading edge in flexible data publishing tech for #DeSci:

1) I wouldn't call it a 'big study", or even a study at all. The paper you linked is a report describing a dApp a private for-profit company made. Unfortunately, neither the frontend nor contract code is open source, so the benefits of putting anything on-chain without essential code auditability are heavily compromised. A hypothesis based "study" they could have done would be to use their tool to index a benchmark dataset like OpenAlex, NCBI, etc vs alternative solutions in performing some useful action (e.g. storage/retrieval times, cost/size per object, en/decryption, verifiability, etc).

2) As a professional scientist and member of the scientific community I hold a strongly contrarian perspective to the establishment regarding peer reviewed paper count. I'm pretty confident most if not all of my desci contributor colleagues would agree.

3) Base64 encoding doesn't do much other than prevent BNB from throwing errors when the contract writes the data to it (bc of special characters that might be in text). The data isn't encrypted so their tool can only be used to create references for existing data in the public domain - which defeats their stated purpose for building the app...

"Welcome to the first 100% on chain decentralized storage Dapp for biomedical and general purpose data (such as text, images, audio and video) providing you with Identity, Timestamping, Content and Immutability (ITCI) for your business."

It doesn't make economic/business sense to store data on BNB, an EVM chain with limited horizontal scaling. They should have at least enabled the opBNB L2 to leverage a rollup and mitigate cost + data volume settled on L1. It would cost nearly $80 to save the word "test" using their dApp (screenshot #1). No wonder they didn't run a benchmarking trial.

-----Alternate Solutions-----
A) @oceanprotocol uses a "provider" to encrypt/decrypt URLs of user published data (accessible via HTTP), then they store tokenized references on-chain which grant the owner/purchaser permission to decrypt a target URL. They've got a solid metadata (object labeling) system & built a compute-to-data interface that unlocks actual usability for sensitive/private data, such as almost any business would require.

B) @eas_eth likewise employs multiple privacy options and scalability solutions for publishing data and/or references on-chain.

Users can publish attestations offchain of any size for free, or they can enter encrypted data manually into the appropriate schema field if included in an onchain attestation. EAS released a sha256 hash tool for easy & non-reversible encryption of sensitive data. For even higher security, they created a "private data" attestation schema that encrypts the contents in a Merkle Tree to support selective disclosure (read permissions) of specific fields in the a given data schema. EAS timestamps & UX are a bit clunky, but overall it's an extremely versatile platform + set of standards.

3c) TLDR; at @HyperfilesOrg we're combining the best of both Ocean & EAS with features to support co-governance of collaboratively generated digital data assets. Most of the engineering & integration design was done in Q1-2024, with some groundwork laid in 2023 during two hackathons. Q2-2024 is mainly building/shipping those designs, and we're even adding things to the roadmap like a smart contract to calculate global reputation scores for the Hyperfiles knowledge graph (a social graph with infinitely customizable schemas, version control, automated object classification, and user reputation scoring).

------Hyperfiles Deets------
We're implementing encryption by default for data objects published using our dApp (starting w/ sha256, then Lit Protocol PKPs). We're also replicating the Ocean "provider" architecture for a second layer of security & data provisioning during URL endpoint sharing.

Hyperfiles reference objects are stored in the open-source Near socialDB contract for typically ~$0.07 per object. Hyperfiles a superset to EAS attestations so users can select the EAS attestation standard as a Hyperfiles schema. This interoperability enables users to query standardized metadata across multiple sources, facilitating reusable elements & enforcing composability between completely unrelated data objects, as well as dynamic data object rendering.

References (and subsequent versions) are uniquely timestamped by their blockheight. Human-readable object paths uniquely identify references stored under each user's personal data tree in socialDB.

The entire Hyperfiles app - every single React frontend component - is also stored immutably on the Near socialDB contract via path & blockheight (the same way references are stored). The code is easily viewable/forkable directly from the app itself if users want to customize or contribute new components (screenshot below).

Comparatively, the INNBC claim to be "the first 100% on chain decentralized storage Dapp for biomedical and general purpose data" is frankly, complete BS and highlights just how flawed & ineffective peer-review is when managed by exploitative publishers. Their dApp is not 100% on-chain and it's definitely not the first to do what it does.

Hyperfiles already has read/write adapters for off-chain storage layers: IPFS and GitHub. A suite of additional default adapters in the Q2-2024 roadmap include local storage, Notion, Obsidian, Arweave, Ceramic, Verida, EVM Chains (via Solidity ABI), and even a few indexing services as data input options.

It's taken a systematic and relentless approach to engineer, integrate and distill the diversity of features behind Hyperfiles into our current roadmap of smart contracts & frontend UI components. You can try the open beta at https://t.co/Zug0QK3If1 and access our prolific documentation wiki from the app as well.

Join the Hyperfiles TG group and I'll send you some free $NEAR tokens to pay storage deposits & gas fees.
https://t.co/DD9THvrpu7

-----References-----
In-progress "development" version of Hyperfiles:
https://t.co/eEfyMxyJwI

List of on-chain components (widgets):
https://t.co/4YlHFYFp5z

Off-chain code repos (React components, "gateway" app to render React code from Near), and our smart contracts:
https://t.co/hRvZNhbwVl

[Jaswinder Singh @jassification]

Async RPC calls on @NEARProtocol are really really fast. This is why we should give them a deeper look as an ecosystem.

Here is a thread of my recent findings and thoughts.

PS: For a short introduction for what I mean by Async calls, read this previous thread.

[Hyperfiles @HyperfilesOrg]

⚠️ Hyperfiles is in open-beta and under active development. If you’re interested in contributing, we're always seeking additional open-source contributors. Just check out our GitHub, docs, and hop in the chat!

7/🧵

[Hyperfiles @HyperfilesOrg]

🧠 We’ve created extensible Schema & Type Libraries deployed to an open social graph contract. Hyperfiles creates a universal, self-organizing, attestation-based knowledge graph for scientific sensemaking, impact evaluation, and empirical hypothesis testing.

6/🧵

[Hyperfiles @HyperfilesOrg]

Together, these features enable collaborative data curation, co-governance of digital assets, marketplace functionality, and more. User can even interact with and dynamically render data objects according to the permissions they hold.

5/🧵

[Hyperfiles @HyperfilesOrg]

🧠 Adapters are used to establish interfaces with your choice of storage locations. You will soon be able to delegate and receive read, write, owner-level permissions to specific fields and records defined in reference objects.

4/🧵

[Hyperfiles @HyperfilesOrg]

⛓️ Hyperfiles creates indexed onchain reference objects to map the contents of corresponding data objects, stored anywhere.

Hyperfiles are a superset of the popular EAS attestation standard that provide additional context by explicitly linking the data field to schemas.

3/🧵

[Hyperfiles @HyperfilesOrg]

Hyperfiles was originally developed as "Hypercerts on BOS" during the BuidlBox Funding the Commons Hackathon in August 2023, then extended into "Hyperfiles" during Backdrop Build v3 in November 2023 (completion certificate is the logo image for our #GG20 application).

2/🧵

[Hyperfiles @HyperfilesOrg]

🌟 Hyperfiles is live in two rounds for #GG20!

💻 dApps & Apps Round: https://t.co/EuIX9eu2tf

✍️ Hypercerts Ecosystem Round: https://t.co/IfPaauKcg0

They're separate rounds with separate matching pools, so support in both is very much appreciated!

1/🧵 More info below... 👇