Midnight Build Club Show Lumera Storage for Privacy Apps

Midnight publish one Build Club masterclass wey focus on Lumera Protocol and im Cascade storage system on September 10. The session show one architecture wey Midnight dey manage proofs and selective disclosure while encrypted files dey stored outside the Midnight blockchain through Lumera’s SuperNode network.

The workshop follow the partnership wey Lumera Protocol and the Midnight Foundation announce on August 5, wey introduce Cascade as one storage option for applications inside the Midnight ecosystem.

Cascade Connects Private Proofs With Stored Data

Midnight applications fit prove one claim without to publish all the information wey dey behind am. But the source document fit still need to dey available when user or application wan generate another proof.

The model wey dem present during the workshop separate these functions. Midnight fit hold commitment, proof or reference wey relate to one document, while Cascade dey store the encrypted version.

Before upload, dem go hash the file so that later dem fit verify im integrity. After that, Cascade go divide the data into fragments and distribute dem across Lumera SuperNodes. The network dey use redundancy and recovery mechanisms to rebuild fragments wey no dey available and redistribute dem among active operators.

Cascade don already dey available on the Lumera mainnet, but e no dey built inside the Midnight runtime or Compact programming language. Developers dey access am as separate service through Lumera’s SDKs and APIs.

Two Storage Models for Midnight Applications

The presentation outline two approaches to connect private computation with decentralized storage.

The first one, wey dem call Storage First, dey designed for data wey no dey change often, like diplomas, identity documents or certificates. Application fit encrypt file and store am through Cascade, then later use that same document to generate verifiable claims.

The Compute First model apply to information wey dey change regularly, including credit histories and financial records. Application fit store updated encrypted versions and use dem to create new proofs as the underlying data dey change.

The speakers point private KYC, healthcare records and DeFi compliance as potential use cases. These na development examples, no be confirmed production products. Encryption key management still dey with the application or user, meaning say if key lost, access to the stored content fit permanently no dey again.

Research Archive Turn the Model Into Working Prototype

The session include demo of Lumera Research Archive, one publicly accessible prototype to prepare and publish research papers. Users fit connect wallet, save encrypted draft, sign the contents and later release am through public archive.

During the process, dem dey register the document hash before upload, while Cascade dey coordinate storage across SuperNodes. Published paper dey receive Action ID wey fit serve as verifiable reference to the stored material.

Lumera describe Cascade as permanent storage wey person go pay for once in LUME.

Continued retention dey rely on protocol economics, network funding and operators wey dey receive LUME to maintain data availability.

Research Archive never dey presented as production Midnight application. Im current role na to demonstrate how private document, decentralized storage and blockchain proof fit operate as separate but connected layers. The prototype dey give Midnight developers one concrete architecture for applications wey need continued access to encrypted source data side by side with on-chain verification.