Crypto-native trade surveillance, transaction monitoring, and market integrity via the HALO platform — detects spoofing, wash trading, layering, and onchain manipulation across CEX and DeFi venues.
- 01trade surveillance (CEX + DEX)
- 02market manipulation detection
- 03transaction monitoring
- 04stablecoin and token monitoring
- 05case management for compliance ops
| Variable | Scope | Description |
|---|---|---|
| SOLIDUS_API_KEY | Server | API key issued by Solidus for HALO platform integrations. |
| SOLIDUS_TENANT_ID | Server | Tenant identifier used to scope HALO API requests to your organization. |
Use Solidus Labs HALO for trade surveillance and onchain transaction monitoring. Server-side, batch-stream order, trade, and deposit/withdrawal events to the HALO ingestion API (`POST https://api.halo.soliduslabs.com/v1/{tenant}/orders|trades|transactions`) with `Authorization: Bearer <SOLIDUS_API_KEY>` and an `Idempotency-Key` per event. Send normalized fields — `venue`, `instrument`, `side`, `price`, `size`, `timestamp` for orders/trades, and `tx_hash`, `from`, `to`, `asset`, `amount`, `chain` for onchain transactions — so HALO's detection models (wash trade, spoofing, layering, sanctions exposure) fire correctly. Consume alerts via `GET /v1/{tenant}/alerts` and the `alerts.created` webhook, then push reviewer dispositions back with `PATCH /v1/{tenant}/alerts/{id}` to feed the agentic case management workflow.
- ⚑Detection models depend on order-book context, not just trade prints — if you only send fills you lose spoofing/layering coverage. Stream order add/modify/cancel events too.
- ⚑Onchain monitoring relies on Solidus integrations with Chainalysis/TRM/Elliptic — confirm which provider keys yours use, since coverage and entity attribution differ across them.
- ⚑False-positive rates are high for the first 4–6 weeks while behavioral baselines learn your venue — expect heavy reviewer load during tuning and feed dispositions back consistently.
- ⚑Jurisdiction-specific surveillance scenarios (FINRA spoofing rules, MAR for EU MiCA, MAS for Singapore) must be enabled per market — defaults do not light up every applicable scenario.
- ⚑Sandbox uses replayed historical data — alert volumes and timing won't match production, so don't size your case-management headcount from sandbox numbers.
- ⚑Webhooks are HMAC-signed in `x-solidus-signature` — verify and enforce timestamp skew to prevent replay.
- ⚑Trade and surveillance data retention is contract-defined (often 5–7 years for FINRA/SEC) — record-keeping obligations live with you, so ship alerts and raw events to your own immutable store.