Skip to main content

​
Walrus Evidence Pipeline

Red Sentinel stores the evidentiary record of every completed attack as an immutable blob on Walrus, Sui’s decentralized blob store, and anchors each blob to the Sui blockchain so anyone can independently retrieve and verify it. This section documents the integration end to end: the TEE-to-Walrus pipeline, the evidence blob schema, the on-chain anchoring mechanism, the public evidence explorer, and the known limitations of the current release.

​
Why Walrus

Attack verdicts are small (roughly 2–10 KB per record) but must be permanent, tamper-proof, and independently auditable. Walrus provides:
  • Immutable blob storage — encoded across storage nodes with erasure coding; blobs cannot be edited after certification.
  • Sui-native economics — storage is paid for in WAL over a fixed number of epochs (Red Sentinel stores records for 5 epochs).
  • Public retrievability — any blob can be read back by its blob id over a plain HTTP request from a public aggregator, no wallet and no Sui infrastructure required.

​
What gets stored

For every completed attack, one evidence blob is created containing the attack prompt, the Sentinel agent’s response, the jury verdict and evaluation score, and the provenance needed to trace the record back to on-chain settlement. See Evidence Blob Schema.

​
The pieces

​
Verify something right now

You don’t need a wallet or a Sui node. Open the Public Evidence Explorer, pick any record, and follow the VERIFY_INDEPENDENTLY links to fetch the raw blob from the Walrus aggregator.