Blockchain threat intelligence

Not a qualified workload
There is no Relata-run blockchain scenario in the 3.0 battery. The detection test suite for this vertical is a standalone Python suite that does not start a Relata node. This page therefore describes a pattern built from verified general features, and does not claim blockchain-specific operators: CRYPTO_TRACE was removed in 3.0.

The problem

A compliance or security team watches transfers on an EVM-compatible chain: sanctioned counterparties, mixer interaction, wash-trading loops, structuring and velocity spikes, flash-loan and reentrancy shapes. The detectors are heuristics. The storage question is different: keep every transfer and address as it was believed at the time, link addresses, and let an analyst walk from a flagged transfer to the surrounding graph and back to the evidence.

The shape

  • Load. Your collector (or OpenETL) maps explorer API responses to normalized Transfer rows and sends them to POST /v1/ingest/bulk. A data contract (PUT /v1/ingest/contracts/{dataset}) quarantines malformed frames, and Idempotency-Key plus source_checkpoint make at-least-once delivery safe.
  • Detect. Heuristics run in your code against POST /v1/query results, or as native window rules (threshold and correlation) for count-in-window patterns such as velocity and structuring. Findings can be written back as Alert rows with POST /v1/alerts.
  • Link. Wallet-to-wallet flows are links (POST /v1/links). GET /v1/graph/traverse, GET /v1/graph/shortest-path and the SQL DEGREE operator answer "who did this wallet touch".
  • Remember. Everything is bi-temporal: AS OF SYSTEM TIME shows what you knew when you raised an alert, and WITH PROVENANCE shows the source.
  • Sanctions. Load an OFAC or vendor list as a type you own and join against it. The reference fixtures used in the test suite are a small static sample, not a feed.

Honest limits

  • Not a detection engine: no mempool simulation, no multi-hop entity clustering, no live sanctions data.
  • Heuristic outputs are only as good as the detector you write. The reference suite is a set of positive, negative and edge cases.
  • Alert evidence export and triage are the same as in the SIEM / SOC page and share its limits.

Exercised by

The graph, window-rule, ingest-contract and alert pieces are exercised by V3-02 and V3-14 (see the SIEM page for results and recorded defects). The blockchain heuristics themselves were exercised only by the standalone suite, which does not use Relata.