Centralized exchange perpetual futures — continuous funding rate, no expiry, stablecoin margin.
"Opening a futures brokerage account — KYC documents submitted, margin agreement signed, trading permissions granted."
Trader completes exchange KYC: government ID, proof of address, jurisdiction disclosure. This is the compliance center of gravity — the exchange gates everything at account opening. L4+L5 lit: identity and authorization are policy-enforced. Honesty marker: most offshore perp exchanges (dYdX, Hyperliquid) restrict US persons by geofencing and IP detection, but enforcement relies on self-attestation. The compliance surface is only as strong as the identity gate.
"Wiring funds to a futures margin account — collateral posted before any position can be opened."
Trader deposits USDC (or USDT) as margin collateral. The exchange screens the deposit address for sanctions. Margin requirements are code-enforced — the exchange engine won't allow positions exceeding the collateral ratio. L3+L4 lit: execution logic (margin engine) and account state (balance) both update. Prudential domain (D9) applies because the exchange is effectively a CCP for its traders.
"Executing a futures trade on CME — the order matches against the book, the position opens, and the funding rate begins accruing."
Order matches on the exchange's order book. The perpetual contract has no expiry — it tracks the spot price via a funding rate mechanism that transfers between longs and shorts every 8 hours. L2+L3 lit: consensus (order matching) and execution (position management) run entirely in code. Market integrity (D13) and fraud prevention (D6) are the active compliance domains — the exchange monitors for manipulation, spoofing, and wash trading.
"The exchange's risk engine — like a broker issuing a margin call, but automated and instant. No phone call, no grace period."
The exchange's liquidation engine continuously monitors margin ratios. If the position's unrealized loss erodes margin below the maintenance threshold, liquidation fires automatically — no human intervention, no grace period. L3 Execution lit: the liquidation engine is purely code-enforced. D9 (prudential) and D14 (consumer protection) are the active domains. The exchange is simultaneously the CCP, the risk manager, and the executor.
"Closing a futures position and withdrawing profits — PnL realized, tax obligations crystallize."
Position closes (trader exits or liquidation fires). PnL settles to the trader's margin account in USDC. Withdrawal to external wallet triggers a final sanctions check on the destination address. L4+L5 lit: settlement and reporting are policy-enforced. Tax reporting (D12) applies — realized PnL is taxable income in most jurisdictions. Honesty marker: offshore exchanges may not issue tax forms; the compliance obligation falls entirely on the trader.
Resolved 5 steps across 1 chain(s). 0 threshold(s) triggered. Frameworks: Common Reporting Standard / FATCA.
Coverage notes: 5 disclosed gap(s).
Interactive tabbed stack diagram comparing perpetual futures compliance across 4 venues — margin gates, liquidation engines, pricing oracles.
PERPS COMPLIANCE ARCHITECTURE
Circle's Arc places the entire perps stack — Circle StableFX oracle, margin engine, and liquidation engine — at L3 Execution, inside the Malachite BFT consensus boundary. Price feeds are consensus participants, not external services. Manipulation requires compromising the permissioned validator set. Oracle failure halts the chain rather than causing silent price drift and cascade liquidations. CCTP v2 at L4 is code-enforced for cross-chain collateral movement. Regulatory View Keys provide selective position disclosure. 5 of 7 blocks are code-enforced. This is the deepest perps compliance architecture in the comparison set.
P-301 · ARC PERPS SECTION CUT
Which layers light up across asset classes and venues — enforcement type and regulatory citations for each margin gate.
| VENUE / ASSET | FX PERPS | EQUITY PERPS | COMMODITY PERPS | RWA PERPS |
|---|---|---|---|---|
| ArcCircle | 5 4 3 2 1 | NOT AVAILABLE | NOT AVAILABLE | NOT AVAILABLE |
| HyperliquidHyperliquid Labs | 5 4 3 2 1 | 5 4 3 2 1 | 5 4 3 2 1 | 5 4 3 2 1 |
| Coinbase Intl.Coinbase | 5 4 3 2 1 | 5 4 3 2 1 | 5 4 3 2 1 | 5 4 3 2 1 |
| Generic DEXPermissionless | 5 4 3 2 1 | 5 4 3 2 1 | 5 4 3 2 1 | 5 4 3 2 1 |
FX PERPS
CFTC retail forex rules, MiCA Art. 68 derivatives regime
EQUITY PERPS
SEC jurisdiction unclear (synthetic exposure). CFTC if cash-settled.
COMMODITY PERPS
CFTC jurisdiction clear. Standard DCM registration pathway.
RWA PERPS
Union of underlying asset obligations + derivatives regime. Tokenized collateral guidance.
Pricing oracle placement across consensus-native L3, external feed L4, and centralized engine L5.
Consensus-Native
Arc (Circle StableFX)
External Feed
Hyperliquid / Base DEXs
Centralized
Coinbase International Exchange
Consensus-Native — Circle StableFX at L3
Arc (Circle StableFX)
Circle StableFX engine at L3. Price feeds are consensus participants in the Malachite BFT validator set. Oracle failure equals consensus failure — the chain halts rather than producing blocks with stale prices. No silent price drift, no cascade liquidations from bad data. Manipulation requires compromising the permissioned validator set, which is selected by Circle.
FAILURE MODE
Chain halt
CONSEQUENCE
Operationally worse but financially safer — no funds lost to bad prices. Positions frozen, not liquidated.
MANIPULATION SURFACE
Requires compromising Malachite BFT permissioned validator set
WHY ORACLE DEPTH IS A COMPLIANCE QUESTION
Oracle depth determines the failure mode of the entire derivatives stack. A consensus-native oracle (Arc Circle StableFX at L3) changes the failure mode from "cascade liquidation from stale data" to "chain halt" — the latter is operationally worse but financially safer. No funds are lost to bad prices; positions freeze rather than liquidate. An external oracle (Chainlink, Pyth Network at L4) keeps the chain running on stale prices, producing liquidations that are mechanically correct but economically wrong. A centralized oracle (Coinbase International Exchange matching engine at L5) eliminates the oracle question entirely but concentrates all trust in a single regulated entity. The compliance architecture question is which failure mode the regulatory framework prefers — and for CFTC-regulated venues, "halt rather than liquidate on bad data" maps more cleanly to existing circuit-breaker expectations from traditional derivatives markets.