Introducing dStorage

Building decentralized applications isn’t just about deploying smart contracts.

If your users’ files ultimately live in a traditional cloud where the infrastructure can access plaintext, your application still relies on trusting a centralized provider.

We are building dStorage to change that.

With a single SDK you can:

  • :locked: Encrypt data on the client before it ever leaves the user’s device.
  • :cloud: Store encrypted data on decentralized storage networks (e.g. Arweave).
  • :chains: Coordinate ownership, permissions, and metadata on-chain (e.g. Midnight Network).
  • :key: Keep encryption keys under the user’s control—not the server’s.

The result is a privacy-first architecture where the infrastructure never has access to your users’ plaintext data—not because of a policy or promise, but because the system is designed that way.

What can you build with it?

Any application that needs to keep data off-chain without giving up user privacy.

Examples include:

  • :artist_palette: NFTs — artwork, high-resolution media, metadata, and unlockable content.
  • :money_bag: DeFi protocols — encrypted strategy data, account snapshots, portfolio exports, and compliance documents.
  • :identification_card: Identity & credentials — verifiable credentials, KYC documents, diplomas, and certificates.
  • :hospital: Healthcare — medical records, laboratory results, imaging, and patient documents.
  • :robot: AI applications — prompts, datasets, model outputs, and user conversations.
  • :file_folder: General dApps — contracts, invoices, reports, user-generated content, backups, and application files.

Instead of asking users to trust your infrastructure with their most sensitive data, your application can ensure that only the intended recipients ever have access to it.

Early access to the SDK and developer guides is now available: https://dstorage.pro

Stay Connected

Follow us on X for SDK updates, implementation guides, and early access to new dStorage features: @dStorageTech

2 Likes

Imagine your data following you — without following you around.

You connect to a dApp using a passkey.

From there, you create your dStorage — a private space for your personal data, without handing control of that data to the application.

:locked_with_key: Encrypted locally
Your data is encrypted before leaving your device.

:globe_with_meridians: Stored on a decentralized network
Your encrypted data isn’t locked inside a single application’s infrastructure.

:chains: Verifiable on-chain
Cryptographic fingerprints provide a verifiable way to verify the integrity of your data.

:key: Controlled by your passkey
Your passkey gives you access to your dStorage without a centralized custodian holding your encryption keys.

Then you switch devices.

Connect to the dApp with the same passkey, retrieve your encrypted data, and decrypt it locally.

No account migration.
No centralized data vault.
No company holding your encryption keys.

Just:
Your passkey → Your dStorage → Your data.

And this isn’t just a concept.
We’ve implemented a Passkey Adapter for dStorage that makes this flow possible for dApps. Read our guides to see how to implement it:
https://dstorage.pro/docs