We’re building Canton Event Stream (Dev Fund #300) — an open-source edge tier that classifies raw ledger events into a stable application vocabulary and fans them out over WebSocket/SSE with Canton’s per-party visibility re-enforced at the edge. Both proposals here sit directly downstream of it, so to be specific about which piece touches which:
- Compliance Middleware SDK → our classified-event API. Compliance monitoring is one of the named consumer classes the classified-event vocabulary is being designed for. A compliance middleware layer is exactly that consumer — it would subscribe to our classified events via the published AsyncAPI spec rather than re-implement classification against raw ledger events. We’d align the vocabulary with the SDK’s needs so it serves this use case directly.
- Public risk dashboard → our streams. A real-time risk dashboard is a natural client of the WebSocket/SSE classified streams — pre-classified, per-party-authorized feeds are exactly what it needs and would otherwise have to rebuild.
Happy to align interfaces as both move forward. Concrete compliance and risk consumers are genuinely useful for shaping the event vocabulary, so this is a two-way benefit.