How to Run Scenario and Sensitivity Analysis for Arbitrage

How to Run Scenario and Sensitivity Analysis for Arbitrage

arbitrage scenario sensitivity analysis is a focused control used to decide whether visible market data is genuinely comparable for the same asset, time window, and intended size. Unlike a general arbitrage introduction, this guide concentrates on the relationship among Base Case, Adverse Price Move, and Depth Reduction.

The practical question is not whether arbitrage scenario sensitivity analysis can be displayed, but whether it remains consistent after Base Case, Adverse Price Move, Depth Reduction, Transfer Delay, and Fee and Cost Shock are aligned. The worked case in this article starts with a base-case net margin of 0.62% and ends with fails stress case; the change is produced by validation, not by a prediction of future return.

What is arbitrage scenario sensitivity analysis?

This concept is a repeatable governance method for recording assumptions, realised outcomes, and deviations.

The purpose of this article is not to encourage a transaction. It explains which evidence is required for arbitrage scenario sensitivity analysis and when a displayed result should be treated as unreliable. In particular, Transfer Delay and Fee and Cost Shock can expose constraints that are not visible in a headline percentage.

Key indicators to monitor

Base Case

Base Case is input number 1 in an arbitrage scenario sensitivity analysis review. If it is not measured at the same timestamp and intended size, the comparison can become misleading.

Record the raw value, source, update time, and validation state, then compare it with the venue’s official interface or an independent second source.

Adverse Price Move

Adverse Price Move is input number 2 in an arbitrage scenario sensitivity analysis review. If it is not measured at the same timestamp and intended size, the comparison can become misleading.

Record the raw value, source, update time, and validation state, then compare it with the venue’s official interface or an independent second source.

Depth Reduction

Depth Reduction is input number 3 in an arbitrage scenario sensitivity analysis review. If it is not measured at the same timestamp and intended size, the comparison can become misleading.

Record the raw value, source, update time, and validation state, then compare it with the venue’s official interface or an independent second source.

Transfer Delay

Transfer Delay is input number 4 in an arbitrage scenario sensitivity analysis review. If it is not measured at the same timestamp and intended size, the comparison can become misleading.

Record the raw value, source, update time, and validation state, then compare it with the venue’s official interface or an independent second source.

Fee and Cost Shock

Fee and Cost Shock is input number 5 in an arbitrage scenario sensitivity analysis review. If it is not measured at the same timestamp and intended size, the comparison can become misleading.

Record the raw value, source, update time, and validation state, then compare it with the venue’s official interface or an independent second source.

Technical deep dive: measurement boundaries and audit trail

A robust arbitrage scenario sensitivity analysis model should expose its assumptions instead of hiding them inside one score. The following deep dive separates measurement, source quality, size sensitivity, operational limits, and auditability. Each block is deliberately tied to a different input so the model can be reviewed and challenged.

Measurement boundary for Base Case

Base Case should first be defined with a clear numerator, denominator, unit, venue, and timestamp. A value without those boundaries cannot be compared reliably with Adverse Price Move. Record whether the observation is a quote, a completed trade, an order-book aggregate, a venue rule, or an externally calculated field. This prevents a familiar label from hiding a different definition.

Source integrity behind Adverse Price Move

The usefulness of Adverse Price Move depends on where it came from and how it was transformed. Compare source time with receive time, preserve the raw response where possible, and document every normalisation step. If Depth Reduction comes from another endpoint or update frequency, the model should flag that asymmetry rather than silently combining both values.

Size sensitivity of Depth Reduction

Depth Reduction must be recomputed at more than one intended size. A value that remains stable at 500 USDT may change materially at 5,000 or 50,000 USDT because depth, minimums, rounding, or fixed costs enter the calculation. Plotting Depth Reduction against Transfer Delay across several sizes exposes the point at which the route stops behaving like the headline row.

Operational threshold for Transfer Delay

An operational rule should state when Transfer Delay is acceptable, when it requires manual review, and when it is a hard failure. The threshold should not be chosen only from historical success. It should also reflect data uncertainty, venue rules, and the effect of Fee and Cost Shock under an adverse case. Hard failures should override an attractive percentage.

Audit trail for Fee and Cost Shock

A reviewer should be able to reconstruct Fee and Cost Shock from stored inputs. Save the source, timestamp, planned size, formula version, rounding rule, account tier, and final classification. Compare the archived value with Base Case after the event. This turns the model from an opaque signal into a process that can be tested and improved.

Interpreting the formula without false precision

The working formula for this topic is Net result = gross spread - fees - slippage - transfer cost - stress allowance. It is a model, not a law of the market. Inputs may have different update intervals and some costs are known only after execution. Report a sensible range or confidence band when the data does not support many decimal places. A precise-looking result built on uncertain inputs is still uncertain.

Decision boundaries and failure modes

• Single-Variable Optimism is not merely a theoretical warning. Define a detection signal, a review action, and a hard-stop condition for it. Link the condition to Base Case so the reason for rejecting or downgrading a route is visible.
• When Correlated Stress Ignored appears, compare Adverse Price Move with Transfer Delay before accepting the screen result. If both inputs deteriorate together, a historical average is unlikely to be a sufficient safeguard.
• Treat No Break-Even Point as a scenario variable rather than a footnote. Recalculate the model with a conservative assumption and record how much of the buffer is consumed.
• A control for Historical Range Misuse should identify who or what confirms recovery. A green status, a single successful request, or one completed transaction may not prove that normal operation has returned.
• Review False Certainty from One Scenario after the event as well as before it. The difference between the predicted impact and the realised impact is useful calibration data for future arbitrage scenario sensitivity analysis assessments.

A compact decision record

For the hypothetical case—25,000 USDT, initially a base-case net margin of 0.62%, then a -0.14% result when price, depth, and delay worsen together, and finally classified as fails stress case—store four separate statements: what was observed, what was calculated, what was independently verified, and why the final classification was chosen. Keeping those statements separate prevents later analysis from confusing model output with venue-confirmed facts.

Worked example: turning a screen signal into a decision

Consider a hypothetical route of 25,000 USDT. The first screen shows a base-case net margin of 0.62%. When Base Case and Adverse Price Move are checked together, the picture changes to a -0.14% result when price, depth, and delay worsen together. After Depth Reduction, Transfer Delay, and Fee and Cost Shock are added, the route is classified as fails stress case.

Net result = gross spread - fees - slippage - transfer cost - stress allowance

The example shows why a headline value cannot make the decision by itself. An arbitrage scenario sensitivity analysis review quantifies the gap between a visible signal and operationally comparable conditions; account and venue rules can produce different outcomes for different users.

A step-by-step analysis process

Use the following workflow as a reproducible research sequence. A step can stop the review; later steps should not be used to rescue a route that has already failed a hard technical condition.

1. Define the route and intended size

Define the asset identity, venue pair, intended size, and unit of account. State exactly what arbitrage scenario sensitivity analysis is expected to answer and what it does not answer.

2. Check data time and source

Collect Base Case and Adverse Price Move from named sources. Preserve source timestamps and check whether both observations describe the same market moment.

3. Read the two most important indicators together

Recalculate Depth Reduction from raw inputs rather than copying a screen value. Apply the venue’s precision, quantity, and status rules before comparing results.

4. Add fees and execution effects

Change the intended size and observe Transfer Delay. If the classification changes sharply, report the break point instead of one universal percentage.

5. Run a stress test

Treat Fee and Cost Shock as an operational input. Define an acceptable state, a review state, and a hard-fail state before looking at the most attractive row.

6. Perform the final check on official exchange screens

Run the formula with the base case, a modest adverse case, and a combined stress case. Do not assume that price, depth, timing, and cost deteriorate independently.

7. Record the result and update assumptions

Store the decision-time inputs and compare them with the later realised or confirmed state. Use the difference to recalibrate thresholds, not to rewrite the original record.

Main risks and weak assumptions

The risk map below is specific to arbitrage scenario sensitivity analysis. Each item can alter the meaning of the data even when the headline price difference remains unchanged.

Single-Variable Optimism

Single-Variable Optimism can create false confidence in an arbitrage scenario sensitivity analysis review. If it is not measured, the data comparison may break, an order may be rejected, or realised results may diverge materially from the initial estimate.

Control: connect Single-Variable Optimism to a measurable test involving Base Case or Adverse Price Move; define who confirms the result and what condition blocks further review.

Correlated Stress Ignored

Correlated Stress Ignored can create false confidence in an arbitrage scenario sensitivity analysis review. If it is not measured, the data comparison may break, an order may be rejected, or realised results may diverge materially from the initial estimate.

Control: connect Correlated Stress Ignored to a measurable test involving Adverse Price Move or Depth Reduction; define who confirms the result and what condition blocks further review.

No Break-Even Point

No Break-Even Point can create false confidence in an arbitrage scenario sensitivity analysis review. If it is not measured, the data comparison may break, an order may be rejected, or realised results may diverge materially from the initial estimate.

Control: connect No Break-Even Point to a measurable test involving Depth Reduction or Transfer Delay; define who confirms the result and what condition blocks further review.

Historical Range Misuse

Historical Range Misuse can create false confidence in an arbitrage scenario sensitivity analysis review. If it is not measured, the data comparison may break, an order may be rejected, or realised results may diverge materially from the initial estimate.

Control: connect Historical Range Misuse to a measurable test involving Transfer Delay or Fee and Cost Shock; define who confirms the result and what condition blocks further review.

False Certainty from One Scenario

False Certainty from One Scenario can create false confidence in an arbitrage scenario sensitivity analysis review. If it is not measured, the data comparison may break, an order may be rejected, or realised results may diverge materially from the initial estimate.

Control: connect False Certainty from One Scenario to a measurable test involving Fee and Cost Shock or Base Case; define who confirms the result and what condition blocks further review.

How Exarbi supports this analysis

Showing data status, risk level, transfer readiness, and fee impact alongside price differences helps separate an arbitrage scenario sensitivity analysis review from a raw list of percentages.

Exarbi is an independent market-data and decision-support platform. It does not recommend a cryptoasset, execute orders, hold customer funds, or request exchange API keys. A displayed row is a research starting point, not a personal recommendation or an assurance of execution.

Pre-trade checklist

• Was Base Case validated at the same timestamp?
• Was Adverse Price Move recalculated for the intended size?
• Does Depth Reduction match the venue’s actual rule?
• Was an adverse case applied to Transfer Delay?
• Were Fee and Cost Shock and the final assumptions recorded?

Frequently asked questions

Why is arbitrage scenario sensitivity analysis not enough on its own?

Because price, liquidity, fees, transfer conditions, and account restrictions can change together. It is an important filter, not a substitute for final venue verification.

When should arbitrage scenario sensitivity analysis be checked again?

During initial screening, immediately before any action, and whenever the underlying conditions change.

Which data should be recorded?

Record the raw value, source, timestamp, intended size, formula, account rule, and resulting classification.

Conclusion: make decisions from the full picture, not one metric

arbitrage scenario sensitivity analysis supports more disciplined interpretation of visible data; it does not guarantee profitability or executability.

Review how Exarbi presents price differences, data condition, transfer-readiness signals, and risk indicators. Do not treat the interface as an instruction to enter a transaction.

Risk warning: Cryptoassets are high risk. You could lose all the money you invest. This material is educational and does not constitute investment, tax, or legal advice. Verify venue terms, fees, networks, account restrictions, and the lawful position in your jurisdiction.

======================================================================