> ## Documentation Index
> Fetch the complete documentation index at: https://docs.redsentinel.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Walrus Evidence Pipeline

> How every completed attack on Red Sentinel becomes a permanent, verifiable evidence blob on Walrus — architecture, schema, anchoring, and public verification.

# 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](https://docs.redsentinel.xyz/walrus/evidence-schema.md).

## The pieces

| Component | What it does |
| - | - |
| [Evidence Pipeline](https://docs.redsentinel.xyz/walrus/evidence-pipeline.md) | How an attack flows from the TEE verification environment to a certified Walrus blob |
| [Evidence Blob Schema](https://docs.redsentinel.xyz/walrus/evidence-schema.md) | The exact JSON fields inside every evidence blob |
| [On-Chain Blob Anchoring](https://docs.redsentinel.xyz/walrus/blob-anchoring.md) | How each blob is anchored to Sui so the record can be independently retrieved and verified |
| [Public Evidence Explorer](https://docs.redsentinel.xyz/walrus/evidence-explorer.md) | The wallet-free web UI for browsing and verifying evidence blobs |
| [Known Limitations](https://docs.redsentinel.xyz/walrus/known-limitations.md) | Honest constraints of the current release |
| [Milestone 1 Status Report](https://docs.redsentinel.xyz/walrus/milestone-1-status.md) | Integration summary and KPI verification for Milestone 1 |
| [Per-Sentinel Security Reports](https://docs.redsentinel.xyz/walrus/security-reports.md) | Aggregate security reports per Sentinel (Milestone 2) |
| [Public Attack Dataset](https://docs.redsentinel.xyz/walrus/attack-dataset.md) | The anonymized public dataset of real attack traces (Milestone 2) |
| [Data Access Architecture](https://docs.redsentinel.xyz/walrus/access-control.md) | Public vs. subscriber access tiers |
| [Milestone 2 Status Report](https://docs.redsentinel.xyz/walrus/milestone-2-status.md) | Outcomes and KPI verification for Milestone 2 |

## Verify something right now

You don't need a wallet or a Sui node. Open the
[Public Evidence Explorer](https://app.redsentinel.xyz/evidence), pick any record, and follow the
**VERIFY\_INDEPENDENTLY** links to fetch the raw blob from the Walrus aggregator.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.