Skip to main content

​
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 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 · Blob Anchoring · Evidence Schema.

​
Design decisions

​
Known gaps

See Known Limitations. 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. 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:
  1. 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.