Walrus Read Consistency: Two Readers, Same Blob, Zero Surprises
@Walrus 🦭/acc guarantees read consistency through cryptographic commitment. Every blob is hashed once at write time. That hash becomes immutable on-chain via Sui. Any reader retrieving the blob can verify its content matches the committed hash. If two readers retrieve the same blob identifier, they will either get identical content or receive data that fails verification.
This guarantee holds regardless of how the blob is distributed across validators. Even if validators disagree internally—one holds a corrupted fragment, another holds the original—the hash commitment ensures readers converge on a single truth. A reader will either reconstruct the correct blob or fail to reconstruct anything at all. There is no middle ground of silent inconsistency.
The practical implication is profound. Applications can safely build on Walrus without coordinating with other readers. Each reader independently verifies correctness. Collusion and Byzantine validators cannot create phantom versions of data that some readers see and others don't.
Zero surprises means the system behaves exactly as promised.
Two readers querying the same blob will always agree.
