Control Room
Single-pane status for the regulated venue — real-time monitoring, market state, and the DCM/DCO settlement path. Surveillance analysts work the alert queue from here.
System & settlement feeds
data-path health across the DCM/DCO stackLive alert queue
Appendix A — real-time market monitoring| Severity | Type | Market | Description | Status |
|---|
Markets
status snapshotMarket Monitoring
Real-time alerts on disorderly trading and market/system anomalies. Click any alert to open its case and move it through investigation. Regs 38.157 · 38.251(c) — Appendix A
| Severity | Time | Type | Market | Account | Description | Status |
|---|
Cases & Investigations
The alert lifecycle CFTC wants to see end-to-end: triggered → investigating → resolved/closed with justification, with analyst assignment, sign-off and a tamper-evident transition log.
| Case | Opened | Type | Market | Severity | Assignee | Status |
|---|
Markets
Per-product state, oracle-anchored price bands (±20%), and operator halt/pause controls. Halting a market requires two-person authorization. §III · §V · Appendix C
| Mkt | Symbol | Class | Status | Mark | Oracle | Band ±20% | 24h vol | Open int. | Funding 8h | Control |
|---|
Order & Trade Activity
Live blotter of orders, fills and rejections with engine reason codes — the data CFTC sees behind every alert. Every row carries the full audit-trail field set. §III · §IV
| Time | Seq | Event | Side | Market | Price | Size | Account | Result |
|---|
Accounts & Participants
Registry keyed on a single customer-level user ID that traces onboarding → order → execution → clearing. KYC/ECP status shown here; onboarding itself runs in the Bridge Portal / FCM. §II · §VI
| User ID | Type | FCM | KYC | ECP | Status | Equity | Margin used | Pos. |
|---|
FCM & Clearing
FCM omnibus structure — each FCM holds a dedicated DCO/bank account; retail customers are internal sub-accounts. Clearing shown as light status indicators (sent / cleared / settled). §VI
Futures Commission Merchants
omnibus accounts & sub-account rollup| FCM | ID | Status | Omnibus balance | Sub-accounts | Margin posted | Clearing |
|---|
Risk Controls & Kill Switch
Pre-trade risk limits, circuit breakers, and emergency controls to prevent and mitigate market disruptions. Disruptive actions require two-person authorization, verified in-engine. Reg 38.255 · Appendix C
Emergency kill switch
real-time interventionKill account session To build
Terminate a participant's active sessions and reject new intake immediately.
Mass-cancel orders Partial
Withdraw all resting orders for an account across every market in one action.
Suspend account To build
Block an account from trading while positions and balances are preserved.
Switch off product Partial
Halt a product across all accounts and firms in real time.
Circuit breakers & pre-trade controls
Price band Live Active
Oracle-anchored ±20% slippage boundary; aggressive orders beyond the band are auto-rejected (SLIPPAGE_EXCEEDED).
Self-match prevention Live Enabled
Maker order canceled when taker and maker share an address (SELF_TRADE).
Volume circuit breaker To build
Auto-pause when 1-min volume exceeds baseline by threshold.
Volatility breaker To build
Auto-pause on price velocity beyond limit over rolling window.
Pre-trade financial limits
per FCM / participant To build| Scope | Max position notional | Max order size | Max open orders | Credit limit | |
|---|---|---|---|---|---|
| Ridgeline Futures (FCM-001) | $25,000,000 | $2,000,000 | 1,000 | $40,000,000 | |
| Hudson Futures (FCM-002) | $12,000,000 | $1,000,000 | 1,000 | $18,000,000 | |
| Retail default tier | $500,000 | $100,000 | 50 | $750,000 |
Surveillance — Solidus
T+1 trade-practice (Appendix B) and market surveillance (§X) run in Solidus, which holds its own investigation dashboard. This panel covers the hand-off: feed health, the CFTC↔Solidus alert-name mapping, and an open-alert rollup. Reg 38.152 · 38.251–253
Feed to Solidus
Healthy- Transport
- 2nd TCP sync subscriber To build
- Last sync
- 11:42:07 UTC
- Lag
- 0.8 s
- Records sent today
- 1,284,902
- Schema version
- v3 · orders·trades·accounts
- Reconciliation
- 0 gaps
Open Solidus alerts
managed in Solidus- Spoofing / Layering
- 3
- Wash trading
- 1
- Position-limit breach (§X)
- 2
- Large-trader concentration (§X)
- 1
CFTC ↔ Solidus alert mapping
naming differences explained for the demo| CFTC term | Solidus alert | Appendix |
|---|---|---|
| Wash trading | Self-Match / Wash Trade | B |
| Accommodation trading | Wash Trade Alert | B |
| Spoofing / layering | Spoofing · Layering | B · 4c(a)(5) |
| Front-running | Front Running | B |
| Pre-arranged trading | Pre-Arranged Trade | B |
| Money pass | Money Pass | B |
| Trading ahead / against | Customer Order Protection | B |
| Position limits / accountability | Position Limit Breach | §X |
| Large-trader monitoring | Concentration / Large Position | §X |
| Cross-market manipulation | Cross-Product Manipulation | §X |
| Marking the settlement | Ramping / Marking Close | §X |
Audit Trail & Recordkeeping
Event-sourced, deterministic record of every order, trade and operator action — millisecond timestamps, operator ID, and full trade reconstruction by sequence. §IX · Regs 38.551–553 · §1.31
Trade reconstruction
deterministic replay from the event logAudit log
orders, controls & case dispositions — newest first| Time (UTC) | Seq | Actor | Action | Object | Detail |
|---|