We've added r/MidnightMainnet support to dStorage Pro, complementing our existing support for Midnight Preprod and Arweave networks.
Developers can now use dStorage Pro's managed payments infrastructure to work across these networks without having to manage protocol tokens or worry about transaction funding.
We're continuing to build, improve and contribute real value to the ecosystem, one step at a time.
Account recovery is an important part of the Web3 user experience, and that's exactly what Midnight Passport brings to the table. But what happens to the data associated with that account?
We think Midnight Passport +r/dStorage can provide a more complete solution.
Here's how the pieces complement each other:
Midnight Passport: Passkey-based account access and recovery, without seed phrases.
dStorage: Client-side encryption and decentralized storage, so infrastructure never sees plaintext.
Midnight: Privacy-preserving ownership verification using ZK proofs.
Together, they offer a way for users to recover both their identity and their data, without relying on centralized services to hold their information.
We're sharing this approach because we believe it could be useful to other teams building on Midnight.
Building a Midnight dApp? We'd be happy to help explore how to integrate passkeys, encrypted data storage, and privacy-preserving ownership into your project. That's exactly what we're building dStorage for: making these capabilities easier to integrate so developers can focus on their applications.
Remember our post about how integrating decentralized storage + Midnight doesn't have to be a pain?
We're taking another step to make it easier.
You can now get free Midnight DUST sponsorship when claiming dStorage Pro test sandbox credits. That means you can experiment with the integration without needing to get DUST yourself first.
We've also published a new guide to walk you through the setup.
๐ What you can explore with dStorage:
Client-side encryption: Keep your data private.
Decentralized storage: Keep control and ownership of your data.
Midnight integration: Connect through our dedicated adapter.
dStorage Pro: Simplify decentralized protocol payments, including DUST.
๐ Want to try it? Use coupon code `PRIVATE_BY_DESIGN` to claim free test credits.
If you're building on Midnight, give it a try and let us know what you think. We'd love to hear what you're working on and where your pain points may be!
If you thought integrating decentralized storage and a privacy-preserving blockchain like r/Midnight was too complicated, we're here to prove you wrong.
r/dStorage is bringing the pieces together so developers can build with:
Decentralized infrastructure often comes with fragmented payment systems.
Different networks require different tokens.
Different protocols have different transaction mechanisms.
And users or developers may need to acquire, hold and manage those tokens just to interact with the infrastructure.
For example, a dApp might need AR token to pay for decentralized storage (r/Arweave), while also needing DUST to interact with Midnight Network (r/Midnight). These are very different networks and use cases, but from the application's perspective they're both simply infrastructure costs that need to be paid.
That's one of the problems we're addressing with dStorage Pro (r/dStorage).
The idea is to provide a liquidity and payment layer for decentralized infrastructure, abstracting away some of the token-management complexity.
A dApp can fund its dStorage Pro account using:
๐ณ Credit card
โฟ BTC/crypto
๐ต Stablecoins
...other
dStorage Pro can then handle the acquisition of the required protocol tokens and transaction signing on behalf of the application.
So instead of building separate payment infrastructure for every network, the application can interact with a common liquidity layer:
dApp โ dStorage Pro โ required token โ decentralized network
That could mean:
AR โ Arweave
or
DUST โ Midnight
and potentially other decentralized networks as additional adapters are integrated.
The goal isn't to hide the underlying protocols. It's to make them easier for applications to use.
We're also designing this around modular adapters, so storage, blockchain and payment infrastructure can be swapped independently rather than hard-coded into the application. (dStorage.pro docs)
We believe this is an important piece of infrastructure if decentralized applications are going to move beyond users having to understand the payment mechanics of every protocol they interact with.
The network can remain decentralized. The application doesn't necessarily need to expose all of that complexity to the user.
I'm very curious how other Web3/decentralized projects are currently handling this:
How do you manage liquidity and protocol-specific tokens when your application interacts with multiple decentralized networks?
From there, you create your dStorage โ a private space for your personal data, without handing control of that data to the application.
๐ Encrypted locally Your data is encrypted before leaving your device.
๐ Stored on a decentralized network Your encrypted data isn't locked inside a single application's infrastructure.
โ๏ธ Verifiable on-chain Cryptographic fingerprints provide a verifiable way to verify the integrity of your data.
๐ 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