Skip to main content

Per-Sentinel Security Reports

Milestone 2 deliverable. This page documents the report-generation pipeline and report schema — the public report surface ships with the Milestone 2 release. Per-Sentinel Security Reports aggregate a Sentinel’s entire attack history into a single immutable Walrus blob: a structured, shareable security report that a defender can hand to customers, auditors, or a community as proof of their Sentinel’s track record.

Report contents

Each report blob contains:

Report schema (sketch)

Generation pipeline

  1. Collect. On a schedule, the report worker gathers all certified evidence blob ids and verdict metadata for the Sentinel from the platform’s anchoring records.
  2. Aggregate. Attack outcomes and classifications are rolled up; the aggregate security score is computed from the jury scores in the underlying evidence records.
  3. Store. The report JSON is written to Walrus as an immutable, non-deletable blob (same storage path as evidence records — Evidence Pipeline).
  4. Anchor. The report blob id is anchored on-chain next to the Sentinel’s identity, and the report becomes reachable at a stable shareable URL.
Because reports are derived only from certified evidence blobs (never from mutable platform state), anyone can recompute the aggregates from the evidence index and check the report — the report is a convenience view over verifiable primary records.

Status

Ships with the Milestone 2 release. The Milestone 2 Status Report tracks the deliverable KPIs (≥ 50 aggregate reports generated and stored).