SpikeSync · Boom & Crash Tracker
SPIKESYNC·BOOM&CRASH
Dashboard
SpikeSync
← HOME
Overview
Total Spikes Logged
0
across all instruments
Booms Logged
0
upward spikes
Crashes Logged
0
downward spikes
Most Overdue
no data
Instrument Status
All Instruments — Live Readiness TIME MODE
INSTRUMENTDIRLAST SPIKESINCEEXPECTED AVG% OF AVGSTATUS
Recent Spikes 0
No spikes yet — click SPIKE on the tracker when one happens
Quick Actions
Instrument Selection
Display Mode
Time mode: primary display is elapsed time · tick count shown as estimate
DISABLEDManual mode · click LOG SPIKE when you see one on Deriv
Auto-detect is experimental. It connects to Deriv's public WebSocket to read live tick data and auto-logs moves larger than 10x the recent tick average. Tag ⚡A = auto-logged · Tag M = manual. Keep manual mode as your primary source of truth while you evaluate auto accuracy.
TICK MAGNITUDE · LAST 40 TICKS·avg ·threshold line at normalapproachingSPIKE
Heartbeat
BOOM 300· expected spike every
TIME SINCE LAST SPIKE
0%50%100% (avg)150%
Actions:
Spikes Logged
0
Median Gap
Shortest
Longest
Currently
Recent Spikes for Boom 3000
No spikes logged yet — when you see one on Deriv, click LOG SPIKE above
Full Spike History
All Spikes 0 RECORDS
WHENINSTRUMENTGAPTICKS ≈CAUGHT?P&LNOTES
No spikes logged yet
Statistical Analysis
Instrument
Spikes
0
Expected Avg
Your Median
Your Mean
Shortest
Longest
Caught Rate
Net P&L
Gap Distribution HISTOGRAM
Hour-of-Day Heatmap UTC
What Boom & Crash Actually Are
Synthetic Index Mechanics

Boom and Crash are algorithmically generated synthetic indices created by Deriv. They don't track any real-world asset — prices come from a cryptographically secure random number generator, audited for fairness.

BOOM
Small down-ticks + rare sudden UP spike
trade: wait for spike / scalp the dips
CRASH
Small up-ticks + rare sudden DOWN spike
trade: wait for spike / scalp the rips
THE NUMBER
500/1000/300/600 = avg ticks between spikes
lower number = more frequent spikes
24/7 MARKET
No real-world news affects these
pure algorithmic patterns only
Time Mode vs Tick Mode
⏱ TIME MODE

Primary display: elapsed time since last spike. Tick count shown as secondary estimate.

✓ Always accurate — counts real time
✓ Never drifts
✓ Works after you come back to the tab
Best for: all trading, default choice
# TICK MODE

Primary display: estimated tick count since last spike (auto-incremented by timer at expected tick rate).

✓ Familiar "tick" framing
✓ Matches Deriv's tick counter
⚠ Estimate — drifts if rate is off
Best for: quick visual readiness check
Tick Rates by Instrument
Default Tick Rates (editable in Settings)
INSTRUMENTAVG SPIKE EVERYTICK RATETIME BETWEEN SPIKES ≈
Boom 300300 ticks1 tick / 2 sec~10 min
Boom 500500 ticks1 tick / 1 sec~8 min 20 sec
Boom 600600 ticks1 tick / 2 sec~20 min
Boom 10001000 ticks1 tick / 1 sec~16 min 40 sec
Crash 300300 ticks1 tick / 2 sec~10 min
Crash 500500 ticks1 tick / 1 sec~8 min 20 sec
Crash 600600 ticks1 tick / 2 sec~20 min
Crash 10001000 ticks1 tick / 1 sec~16 min 40 sec

Rates are averages. Actual spike timing is random — the "average" only holds over many spikes. If Deriv changes tick rates, correct them in Settings.

Auto-Detect & Live Data
⚡ What Auto-Detect Does

When turned ON, SpikeSync opens a WebSocket connection to Deriv's public live tick feed for the currently selected instrument. Every incoming tick is compared against a rolling average of recent ticks. When a single tick is larger than the threshold multiple (default 10× the recent average), it's auto-logged as a spike with the ⚡A badge.

⚡A AUTO BADGE
Spike was detected by the WebSocket based on tick magnitude. Direction-filtered: only upward moves count as Boom spikes, only downward as Crash.
M MANUAL BADGE
You clicked LOG SPIKE (or pressed Space) yourself. Treat manual clicks as your source of truth while evaluating auto accuracy.
Status Indicator & Connection States
DISABLED — Auto is off. Manual mode only.
CONNECTING… — Opening the WebSocket. Normally resolves in under a second.
LIVE · SYMBOL — Receiving live ticks. Meta-line shows tick count + threshold + status.
DISCONNECTED — Connection failed. Auto falls back to OFF; toggle again to retry.

On page load, auto-detect is always forced OFF — even if you left it ON last session. This prevents silent background WebSocket connections. You must re-toggle to activate.

Tuning the Threshold with the Magnitude Chart

The TICK MAGNITUDE chart inside the AUTO panel visualizes the last 40 tick-to-tick deltas as vertical bars. A red dashed line marks your current threshold (avg × multiplier). This is your tuning instrument.

GREEN BARS
Normal baseline ticks. Should be consistently small. Noise.
GOLD BARS
Ticks reaching 60%+ of threshold. "Getting close." Warning zone.
RED BARS
Auto-detected spikes. Should dwarf everything else on the chart.
⟐ TUNING WORKFLOW
1. Run AUTO for 15-30 min on one instrument while watching Deriv's chart side-by-side.
2. If real spikes happen on Deriv but bars never crossed the threshold line → lower threshold (try 7, then 5).
3. If the tool auto-fires on moves that weren't real spikes → raise threshold (try 13, then 15).
4. Open Settings to change the value. Default is 10× · range 2-30.
Heartbeat Sparkline

Small live price chart of the last 100 ticks, shown below the magnitude chart. Purpose: confirm data is flowing. Green end-dot = price trending up since window start, red = down. This is not a replacement for Deriv's actual chart — use Deriv for price-action analysis, use this to verify the tool is still receiving data.

Counter Resets & Clearing Data
⟲ RESET COUNTER

Inserts a synthetic spike marker at NOW for the current instrument. The ticks-since-last-spike counter drops to 0.

Use when: you know a spike happened but forgot to log it, or you've been AFK and the counter is hours stale. Tagged with "[manual reset marker]" in notes.
✕ CLEAR THIS INSTRUMENT

Deletes ALL logged spikes for the current instrument only. Other instruments keep their data.

Use when: you want to restart tracking one instrument from zero (testing, or switching strategy). Confirms count before deleting. Cannot be undone.
↻ RECONNECT WS

Force-reconnects the Deriv WebSocket. Only visible when AUTO is ON.

Use when: status says LIVE but tick count hasn't moved for a while, or you suspect stale data. Auto-reconnect runs in background on drops, but this forces it now.
Trading Approaches
▲ SPIKE HUNTER

Wait until the counter is at or past the expected average. Enter in spike direction (long for Boom, short for Crash) with defined stop. If no spike comes, exit and re-enter.

Target: capture the spike · Risk: spike delays, your stop hits first
▼ COUNTER-TREND SCALPER

Trade the baseline drift AGAINST the spike direction. Buy dips on Crash (baseline drifts up), sell rips on Boom (baseline drifts down). Exit before expected spike window.

Target: accumulate small wins · Risk: unexpected spike wipes many scalps
Honest Caveats
⚠ What This Tool Can & Cannot Do
CAN: Track your actual spike timing history, surface statistical patterns, enforce discipline (by making you log and reflect), export data for deeper analysis.

CANNOT: Predict the next spike. Boom/Crash are designed to be random within their distribution. If the "average" is 500 ticks, the next spike could be at tick 50 or tick 2000. Probability shifts with elapsed time but certainty never arrives.

EDGE CLAIM: The real edge on synthetic indices is discipline — correct sizing, accepting that spikes are random, not martingaling, and walking away when patterns break. This tool helps with discipline. No tool can manufacture edge that isn't there.

AUTO-DETECT STATUS: Experimental. It uses a ratio-based threshold against recent tick magnitudes — which works, but is sensitive to tuning. It can MISS real spikes (threshold too strict, or baseline ticks temporarily large) and can FALSE-FIRE on large non-spike moves (threshold too loose). Always keep manual mode as your primary source until you've compared ⚡A catches against Deriv's chart over several sessions. Use the Magnitude Chart to tune the threshold — don't just trust the default.