Walrus Write Flow: From Blob to On-Chain PoA in One Clean Cycle
Writing a blob to Walrus is remarkably simple: the client transforms raw data into fragments, distributes them to designated validators, collects signed acknowledgments, and commits the result on-chain. All in one atomic cycle with no intermediate waiting.
The flow begins with computation.
The client encodes the blob using Red Stuff's 2D encoding, producing primary and secondary slivers. Using the blob ID and grid structure, it derives which validators should receive which fragments.
This is deterministic—no negotiation needed.
Fragments are transmitted directly to their designated validators. Each validator receives its specific sliver and immediately computes the cryptographic commitment (hash + proof). The validator returns a signed attestation: "I have received sliver X with commitment Y and will store it."
The client collects these signatures from enough validators (2f+1 threshold). Once the threshold is reached, the client creates a single on-chain transaction bundling all signatures and commitments into a Proof of Availability (PoA). This transaction is submitted to Sui once, finalizes once, and becomes immutable.
The elegance lies in atomicity.
From the client's perspective, the write either fully succeeds (PoA committed on-chain) or fails before any on-chain action. There is no intermediate state where data is partially committed or signatures are scattered across the chain.
One clean cycle from raw data to verifiable on-chain proof that storage is guaranteed.
