​

Data Access Architecture

​

Access tiers

​

Principles

1. Public claims have public proof. Anything surfaced publicly (a report score, a KPI counter, a shared record link) derives from data that is itself publicly retrievable — certified Walrus blobs and on-chain events. Aggregation never promotes private data into a public claim.
2. Anonymization happens before publication, not after. The public dataset tier only ever sees scrubbed, de-identified records (see Attack Dataset); identity-bearing fields never enter public blobs.
3. Gating lives at the API, not at the storage layer. Raw feeds for subscribers are gated by the platform API (authentication + entitlement checks). Walrus blobs, once public, cannot be un-published — which is precisely why identity-bearing data is excluded from public blobs at write time.
4. Wallet-free reads for public tiers. Verifying a report or an evidence record requires no wallet, no tokens, and no Sui infrastructure — see the Public Evidence Explorer.

​

Data flow summary

 attack record ──► evidence blob (public, Walrus)  ──► explorer / permalinks
        │                                                 ▲
        ├──► aggregated reports (public, Walrus) ─────────┘
        ├──► anonymized dataset (public, Walrus, on-chain anchored)
        └──► raw internals (private store) ──► subscriber feeds (API-gated)