> ## 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.

# Milestone 1 Status Report

> Walrus integration status report for Milestone 1 — architecture summary, design decisions, known gaps, and KPI verification for the 200+ stored evidence blobs.

# Milestone 1 Status Report

This page is the written status report accompanying the Milestone 1 deliverables: a summary of the
integration architecture, the significant design decisions, the known gaps, and how to verify the
on-chain evidence KPIs.

## Integration architecture (summary)

Red Sentinel's Walrus integration connects the platform's TEE verification environment (AWS Nitro
Enclaves) to Walrus such that every completed attack produces a complete evidence blob:

* **Pipeline:** attack → enclave execution + LLM jury verdict → on-chain settlement via Move
  contracts → canonical evidence record (2–10 KB JSON) built server-side → Walrus storage
  (user-signed by default; backend-signed available) → read-back verification → blob id + register/
  certify digests anchored to the attack record.
* **Anchoring:** Walrus `Blob` objects on Sui, recorded register/certify transaction digests, and
  the Sentinel contract's `PromptConsumed` / `AgentDefeated` events.
* **Public surface:** the [Public Evidence Explorer](https://app.redsentinel.xyz/evidence) and the
  unauthenticated `GET /walrus/:network/records/recent` feed, so every KPI below is independently
  checkable in a browser or with `curl`.

Details: [Evidence Pipeline](https://docs.redsentinel.xyz/walrus/evidence-pipeline.md) ·
[Blob Anchoring](https://docs.redsentinel.xyz/walrus/blob-anchoring.md) · [Evidence Schema](https://docs.redsentinel.xyz/walrus/evidence-schema.md).

## Design decisions

| Decision | Rationale |
| - | - |
| Server-authoritative record bytes | The storer cannot forge `success`/`score`; the finalize path verifies stored bytes field-by-field before linking. |
| User-signed storage as the default | The attacker's own wallet pays for and owns the Walrus `Blob` object — records are user property, not platform property. |
| 5 storage epochs | Multi-epoch permanence at sustainable cost per \~2–10 KB record. |
| Read-back verification before linking | Guarantees the on-chain-anchored blob id always resolves to the canonical verdict for that attack. |
| Public aggregator as the read path | Verification requires no wallet, no Sui node, no platform account — just an HTTP GET. |
| Compose Walrus system objects for anchoring | Minimal trust surface for v1; a dedicated anchoring module is Milestone 2 work. |

## Known gaps

See [Known Limitations](https://docs.redsentinel.xyz/walrus/known-limitations.md). The headline items at Milestone 1:

1. Jury rationale, attack classification, chain-of-thought, and the TEE attestation receipt are not
   yet inside the blob (Milestone 2 schema extensions).
2. Anchoring uses Walrus system objects + recorded digests rather than a dedicated
   `EvidenceAnchored` Move event.

## KPI verification

**Deliverable:** on-chain evidence of no fewer than **200 evidence blobs** successfully stored on
the Protocol within two weeks of the Effective Date.

Check it live, no wallet required:

1. Open the [Public Evidence Explorer](https://app.redsentinel.xyz/evidence). The
   **EVIDENCE BLOBS STORED** card shows the total number of certified evidence blobs, computed from
   the platform's anchoring records.
2. Or call the public API directly:

```bash theme={null}
curl -s https://api.redsentinel.xyz/walrus/mainnet/records/recent?limit=1 | jq .total
```

3. Spot-verify any individual record from the explorer's feed: open it, then follow
   **RAW\_BLOB\_ON\_WALRUS** to confirm the bytes exist on Walrus and match the rendered fields.

> **Note:** the counter reflects records certified through the platform's anchoring flow. The
> submission snapshot for the invoice should record the `total` value and its timestamp at the time
> of filing.


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