Crypto Strategy Risk: Exposure, Stops and Operational Loss
Separate price exposure, collateral, custody, API authority, liquidation and unresolved orders instead of relying on a single stop level.
Separate market loss from the other exposure layers
A crypto risk review begins with product, venue, account and quantity. Market movement, collateral conversion, custody, permissions and operational availability are different layers. A stop may address one intended price response without addressing inaccessible funds, a missing account snapshot or an incorrectly mapped contract. List the claims a control can actually enforce before trusting its label.
Spot ownership, borrowing and perpetual exposure can have different obligations. Record contract multiplier, settlement asset and valuation source rather than convert every balance into a generic dollar total. A margin requirement is not a maximum-loss guarantee. A provider grade does not determine a suitable personal position or leverage. This page gives a documentation framework, not an account-specific risk budget or certification of any exchange.
Keep collateral and quote-currency conversions explicit
Suppose a fictional account reports 10,000 quote-token units. At an assumed conversion of one account-currency unit per token the displayed value is 10,000; at 0.99 it is 9,900. The one-hundred difference is a conversion scenario on the same quantity, not a forecast of a peg break or proof that a named token has that price.
Record the conversion source, valuation clock and whether assets can actually be moved or sold under the account's conditions. Product P&L quoted in a settlement token and an account-currency return can differ. If collateral, fees or quantities change during a path, a fixed-notional approximation is incomplete. Keep the original units beside the converted display so a clean dashboard cannot silently conceal an unsupported rate or inaccessible balance.
Inspect triggers, partial fills and liquidation separately
A stop condition, a price-constrained order and a liquidation mechanism are different processes. Request the exact product and broker or venue contract, including trigger reference and supported conditions. Coinbase's official order reference documents one product family and explicitly limits execution protection in adverse conditions; it is not a universal description of all crypto derivatives.
Preserve each partial fill and remaining order state. An invented one-unit entry with 0.40 filled and 0.60 cancelled leaves 0.40 entered, not zero or one. A pause in alerts does not close it. Liquidation, collateral deductions and exchange-imposed changes require their own records rather than a generic stop-distance calculation. This guide supplies no liquidation price, safety buffer or probability of adverse execution for a live account.
Review API authority and failure-state ownership
Identify whether a key can view data, trade, transfer or withdraw under the exact integration. Use current product documentation and the actual permission configuration; do not assume another platform's vocabulary matches it. Never publish credentials in a worksheet or a public evidence packet. A research data collector and an order publisher need different authority and operating evidence.
Document timeouts, duplicate submissions, stale account state, maintenance and later reconciliation. An unknown submission result must remain unknown until authoritative reports resolve it. Save instruction identifiers and retry policy so one request cannot silently become several orders. A functioning API does not certify the strategy, custody or account state. No paid account, private key or live permission test was accessed for this guide.
Stress product costs and common exposure without inventing frequency
Funding assumptions must retain sign, event count, rate units and notional path. In the fictional 10,000 fixed-notional worksheet, fourteen basis points of execution cost and six two-basis-point funding charges total twenty-six. Under a one-percent adverse move, net scenario result is -126. Changing a signed funding assumption creates a separate scenario, not a measured probability or expected future payment.
Show each position and collateral exposure before aggregating a joint shock. Differently named tokens may share a venue, settlement asset or common event. An assumed gain can offset losses arithmetically without proving diversification. CFTC's manipulation advisory informs evidence questions, not an accusation against a service without records. Preserve original scenarios and unknown empirical inputs rather than estimate correlations or worst-case loss from illustrative numbers.
Require cloud-owned controls and a reconciled state journal
A production control needs deployed revision, account route, durable state, decision authority and failure reporting. It must continue with the workstation off; a local notebook, tunnel or fallback file cannot become the hidden production owner. Local correctness tests can remain local while actual operating evidence comes from the managed service.
The blank review record captures those layers and the response to unavailable inputs. Work the conversion and partial-fill fixtures outside market results, then inspect actual contracts if available. A valid finding may confirm permission documentation while leaving execution or collateral valuation unresolved. Do not convert that partial finding into a global safe-exchange badge. This publication reports no live risk-system certification, independently checked custody balance or personalised assurance that a planned stop contains every crypto loss.
Review checkpoints
| Object | Preserve | Do not infer |
|---|---|---|
| Layers | Price, collateral, custody and authority separately | A stop manages every source of loss |
| Operation | Unknown submissions and final execution reports | No API response means no order exists |
| Conclusion | Product contracts and cloud control evidence | A clean balance display certifies safety |
Download blank research record (CSV)
Headers only. No trades, account outcomes or operating receipts are supplied.
Primary Sources
- Coinbase Advanced: product order documentation
- Coinbase Advanced Trade API: documented interface scope
- CFTC: virtual-currency pump-and-dump advisory
Crypto Friction Budget Worksheet
Continue the Research
Cash arithmetic leaves risk objects unresolved
The new lens's 77.94 quote-unit default is an authored full-position amount after entered fees and funding. It contains no liquidation, collateral haircut, partial close or stop guarantee. Its inverse branch has coin settlement and a separately entered quote valuation, not authenticated wallet or account cash. Changing units clears funding and valuation assumptions to expose that boundary. The original risk lesson remains essential: contract access, collateral, custody, order state and responsible cloud ownership require actual sources. No positive teaching case selects an allocation or proves a safe live trading plan.