Skip to content
CCPEDIAby Unity Nodes
OPEN#827 Issue

Hacken open-source monitoring and risk-scoring stack #302 - Adoption Milestone A3 — Consumed by an SV-Approved Compliance Vendor

Opened 21-09-2026 by pedrodneves, last activity 1mo ago

Discussion
0 messages
0 people

A3 — Consumed by an SV-Approved Compliance Vendor

Funding: 86,000 CC (20% of adoption envelope)

Trigger:

  • At least one SV-approved compliance vendor (TRM Labs, Elliptic, Lukka, or Hypernative) formally ingests Extractor's alert schema via webhook or API in one of their production compliance workflows.
  • Signed integration agreement OR a public CIP-addendum documenting the integration OR a joint blog post from the vendor and Hacken.

Verification: signed integration agreement or public CIP/joint post referencing Extractor as an upstream data source.