Revenge trading: stop the objective from becoming “get it back”

The short answer

Revenge trading is loss-chasing behavior in which recovering a recent loss begins to replace the strategy's normal objective. The trader may enter sooner, increase size, accept a weaker setup, loosen invalidation, tolerate worse execution, or keep trading beyond a session boundary because ending negative now feels unacceptable.

The label describes a decision sequence; it is not a clinical diagnosis and cannot be proven from one losing trade followed by one new trade. Compare the post-loss decision with the trader's prewritten rules and baseline behavior, then preserve alternative explanations.

Ask what the next trade is trying to accomplish

A normal strategy evaluates the next opportunity on its own evidence, expected payoff, costs, and risk. A revenge sequence makes the prior loss a hidden input: the size is chosen to earn it back, the deadline is “before the session ends,” or the setup threshold falls because waiting would leave the loss unresolved.

Add one pre-trade field: “Would I take this exact trade, at this size and route, if the previous trade had been flat?” A written no, hesitation, or changed justification triggers the interrupt; it does not authorize a smaller improvised version of the same trade.

Look for changes relative to a baseline

• Speed: time from the loss or failed exit to the next scan, funding transfer, approval, order, or entry compresses materially.
• Size: capital at risk, slippage tolerance, priority fee, or number of concurrent positions rises without a planned volatility adjustment.
• Setup quality: required evidence disappears, a new token or strategy appears, or a watched level becomes optional.
• Exit behavior: invalidation moves farther away, a losing position is averaged without a rule, or profit is taken early merely to turn the session green.
• Execution tolerance: worse routes, stale quotes, unknown contracts, failed transactions, and higher costs become acceptable.
• Boundary changes: the trader extends time, adds attempts, moves funds, switches wallets, or redefines the session after a stop condition.

Reconstruct the sequence instead of trusting memory

Save the loss transaction, actual wallet balance change, fees, position status, and time. Then list the next searches, page views where available, messages, transfers, quotes, signatures, cancellations, and trades. Compare them with ordinary sessions for time-to-next-entry, size, setup tag, evidence completeness, slippage, costs, hold time, and number of attempts.

The journal should preserve the plan as it existed before the loss. A rationale written after the next trade cannot establish that the decision met a prior rule. Versioned checklists and timestamped notes reduce hindsight reconstruction.

Research supports caution, not mind reading

Coval and Shumway found that professional pit traders with morning losses were more likely than traders with morning gains to assume above-average afternoon risk. Experimental disposition-effect research also shows that gains and losses relative to a reference point can change selling behavior and risk preferences.

Those studies do not prove that every post-loss Solana trade is revenge trading, nor do they establish one universal cooldown. Market structure, participant, sample, and strategy differ. Use the findings to justify monitoring post-loss behavior, then use your own timestamped decisions to evaluate the individual case.

Preserve legitimate reasons for a fast next action

A planned hedge, arbitrage leg, liquidity migration, partial-fill correction, duplicate-transaction defense, correlated-risk reduction, or second entry already specified in the strategy can follow a loss quickly. Speed alone is not the claim.

Ask whether the action and size were documented before the loss, whether it reduced or added net risk, whether its evidence threshold changed, and whether the same response occurs after comparable winning or flat trades. Classify the result as planned response, supported loss chasing, possible drift, or unknown.

Build a circuit breaker that changes access

Define triggers in advance: a per-trade breach, session loss, consecutive losses, an unplanned size increase, a moved invalidation, repeated failed orders, or an attempt to trade after the session ended. The trigger can cancel resting orders, disable quick execution, revoke a bot session, move uncommitted risk capital out of the hot wallet, and start a reconciliation checklist.

Use the loss limit and session limit as the hard outer controls. Breathing, walking away, or talking to someone may help, but a safety rule should not depend only on accurately judging your own state while the urge to continue is active.

Stopping new trades does not resolve open risk

First reconcile wallet balances, pending signatures, partial fills, open orders, delegates, and every position. Follow the prewritten exit or monitoring plan. Do not abandon a live position to prove that the session has ended, and do not add a new speculative position under the label of “hedge” unless it meets the original hedge rule.

If a breach already increased exposure, reduce according to liquidity and failure priority rather than trying to exit every asset through the same route at once. Record residual risk and who remains responsible for monitoring it.

Review the trigger and the control separately

Reconstruct what changed after the loss, then ask whether the circuit breaker fired, whether it changed access soon enough, and how it was bypassed. A rule that repeatedly requires perfect self-control at the worst moment needs a stronger implementation, not a more motivational description.

Do not rewrite strategy thresholds from one episode. Tag the breach, return at a predetermined reduced-risk state if the plan allows, and evaluate repeated patterns across a meaningful sample before changing the strategy itself.

A post-loss interrupt workflow

1. Freeze new risk. Stop entries and preserve the loss, account state, time, and active orders before another decision changes the evidence.
2. Reconcile exposure. Resolve pending transactions, balances, open orders, positions, and the actions still required by the original plan.
3. Run the counterfactual. Ask whether the next candidate would be taken identically if the previous result had been flat.
4. Apply the circuit breaker. Disable access, end the session, and complete the documented loss-limit response.
5. Reconstruct the sequence. Compare speed, size, setup evidence, execution tolerance, and boundary changes with the baseline.
6. Return by rule. Require the planned reset, review, and risk state rather than using a new opportunity as proof of readiness.

What belongs in the journal

Record the triggering loss and actual balance change, prior plan version, time to next search and order, candidate setup and counterfactual answer, planned versus actual size, slippage and fee changes, invalidation edits, entries and attempts, wallet transfers, session and loss-limit status, circuit-breaker trigger, access controls applied, open-risk reconciliation, alternative explanations, return conditions, and process classification independent of final P&L.

Primary and official sources