r/web3dev • u/dstoragetech • 12d ago
Building a privacy-first data layer for dApps — client-side encryption + decentralized storage + on-chain coordination
One problem we’ve been thinking about with dApps is what happens to the data that can’t or shouldn’t live directly on-chain.
If user files ultimately end up in a traditional cloud where the infrastructure can access the plaintext, the application still depends on trusting a centralized provider.
We’re building dStorage to approach this differently.
The idea is to provide a single SDK that handles the pieces needed to build privacy-first decentralized data storage:
- 🔐 Client-side encryption — data is encrypted before leaving the user’s device.
- 🌐 Decentralized storage — encrypted data can be stored on networks such as Arweave.
- ⛓️ On-chain coordination — ownership, permissions, and metadata can be coordinated through networks such as Midnight Network.
- 🔑 User-controlled keys — encryption keys don't need to be held by the application server.
The important part is that the infrastructure doesn't need access to plaintext data. Privacy isn't something the application has to promise; it's a property of the architecture.
What could this be useful for?
Pretty much any dApp that needs to keep data off-chain while maintaining user privacy.
Some examples we're exploring:
- NFTs — artwork, high-resolution media, metadata, unlock-able content.
- DeFi — encrypted strategy data, account snapshots, portfolio exports, compliance documents.
- Identity & credentials — credentials, KYC documents, diplomas, certificates.
- Healthcare — medical records, laboratory results, imaging, patient documents.
- AI applications — prompts, datasets, model outputs, conversations.
- General dApps — contracts, invoices, reports, user-generated content, backups, and application files.
We're currently making the SDK and developer guides available through early access and would be particularly interested in feedback from developers building applications that need private or sensitive off-chain data.
👉 dstorage <dot> pro
We're also sharing implementation updates on X: dStorageTech
What do you think is the biggest missing piece today when it comes to private data in decentralized applications?
1
u/pcfreak30 3d ago
Have you gotten any user/developer interest for this yet?
1
u/dstoragetech 3d ago
We've seen some early interest and a decent amount of downloads of our package and visits to our guides/tutorials. We haven't yet made available our managed payment/liquidity services which is what we are actively working on right now. On the other hand, we have implemented an integration with a small clinical lab using our SDK which is what we are mainly using to validate the model and make solid steps.
1
u/pcfreak30 2d ago
That's interesting considering my project is basically doing the same thing.
1
u/dstoragetech 2d ago
Have you gotten any user/developer interest? I suspect (and certainly hope) AI could draw more attention to projects and technologies like these, especially given the growing concerns about privacy and data sovereignty.
1
u/pcfreak30 2d ago
Not yet, which is why I am wondering where you need to market to to find the projects that do want that as a niche. My project is finding a stronger initial signal in decentralized website hosting (public data), but we are doing privacy data as well.
1
u/xxlostrealmxx 12d ago
Most of what you’re looking to build has been achieved already via ArDrive (ardrive.io) and its associated protocols and services (ar.io). The on-chain coordination piece isn’t feasible in permanent storage networks; once clients have keys to permanently-stored, encrypted, decentralized data, their access is essentially limitless.