Depeg Tracker and DEWS Changelog: v4 archive
Historical release evidence. Return to current versions and the complete history index.
What this controls
Depeg Tracker and DEWS Changelog: v4 archive version history
Use this changelog to trace how Pharos changed the related scoring, data-source, threshold, or interpretation rules over time. Entries record the contract active at each release; archived rules are retained so historical charts and citations can be read against the rules active at the time.
Primary references
Latest version
Bootstrap sentinel and core-liquidity freshness gating
DEWS bootstrap is now a one-time state transition, and stale or missing core liquidity inputs no longer masquerade as acceptable startup conditions.
Impact snapshot
- Bootstrap grace now ends after the first successful DEWS publication via a dedicated `dews:bootstrap-complete` sentinel instead of piggybacking on stablecoins-cache freshness
- Only explicitly optional missing tables remain bootstrap-allowed before first success; core dependencies no longer inherit that grace
- Fresh `dex_liquidity` is now required for publication, with rows older than 2 hours treated as a hard degraded source failure
v4.9Mar 23, 2026Bootstrap sentinel and core-liquidity freshness gating
DEWS bootstrap is now a one-time state transition, and stale or missing core liquidity inputs no longer masquerade as acceptable startup conditions.
- Bootstrap grace now ends after the first successful DEWS publication via a dedicated `dews:bootstrap-complete` sentinel instead of piggybacking on stablecoins-cache freshness
- Only explicitly optional missing tables remain bootstrap-allowed before first success; core dependencies no longer inherit that grace
- Fresh `dex_liquidity` is now required for publication, with rows older than 2 hours treated as a hard degraded source failure
DetailsHide details
Bootstrap sentinel and core-liquidity freshness gating
DEWS bootstrap is now a one-time state transition, and stale or missing core liquidity inputs no longer masquerade as acceptable startup conditions.
- Bootstrap grace now ends after the first successful DEWS publication via a dedicated `dews:bootstrap-complete` sentinel instead of piggybacking on stablecoins-cache freshness
- Only explicitly optional missing tables remain bootstrap-allowed before first success; core dependencies no longer inherit that grace
- Fresh `dex_liquidity` is now required for publication, with rows older than 2 hours treated as a hard degraded source failure
Impact notes
- Bootstrap grace now ends after the first successful DEWS publication via a dedicated `dews:bootstrap-complete` sentinel instead of piggybacking on stablecoins-cache freshness
- Only explicitly optional missing tables remain bootstrap-allowed before first success; core dependencies no longer inherit that grace
- Fresh `dex_liquidity` is now required for publication, with rows older than 2 hours treated as a hard degraded source failure
v4.8Mar 22, 2026Contradicted live depegs now retire into pending confirmation
When a low-confidence primary price now contradicts an open live depeg across the peg, the stale live row is retired immediately and the replacement move waits in pending confirmation instead of leaving the wrong direction active.
- Opposite-direction live depeg rows no longer remain active just because the correcting primary price is still confirm_required
- Direction flips from cached, fallback, low-confidence, or stale primary inputs now close the stale live row and insert a replacement pending candidate
- Public active-depeg state stops claiming the wrong side of the peg while confirmation catches up on the corrected move
DetailsHide details
Contradicted live depegs now retire into pending confirmation
When a low-confidence primary price now contradicts an open live depeg across the peg, the stale live row is retired immediately and the replacement move waits in pending confirmation instead of leaving the wrong direction active.
- Opposite-direction live depeg rows no longer remain active just because the correcting primary price is still confirm_required
- Direction flips from cached, fallback, low-confidence, or stale primary inputs now close the stale live row and insert a replacement pending candidate
- Public active-depeg state stops claiming the wrong side of the peg while confirmation catches up on the corrected move
Impact notes
- Opposite-direction live depeg rows no longer remain active just because the correcting primary price is still confirm_required
- Direction flips from cached, fallback, low-confidence, or stale primary inputs now close the stale live row and insert a replacement pending candidate
- Public active-depeg state stops claiming the wrong side of the peg while confirmation catches up on the corrected move
v4.7Mar 21, 2026Early peg score: minimum data threshold lowered from 30 to 7 days
Peg score is now emitted after 7 days of tracking instead of 30, with an 'Early score' label for the 7-30 day window.
- Minimum tracking threshold reduced from 30 to 7 days, so coins receive a composite peg score after their first week
- Scores based on 7-30 days of data are labelled 'Early score' in the hero card (amber text with tooltip)
- Report card peg-stability dimension is now rated from day 7; NR only appears for coins with < 7 days of history
DetailsHide details
Early peg score: minimum data threshold lowered from 30 to 7 days
Peg score is now emitted after 7 days of tracking instead of 30, with an 'Early score' label for the 7-30 day window.
- Minimum tracking threshold reduced from 30 to 7 days, so coins receive a composite peg score after their first week
- Scores based on 7-30 days of data are labelled 'Early score' in the hero card (amber text with tooltip)
- Report card peg-stability dimension is now rated from day 7; NR only appears for coins with < 7 days of history
Impact notes
- Minimum tracking threshold reduced from 30 to 7 days, so coins receive a composite peg score after their first week
- Scores based on 7-30 days of data are labelled 'Early score' in the hero card (amber text with tooltip)
- Report card peg-stability dimension is now rated from day 7; NR only appears for coins with < 7 days of history
v4.6Mar 10, 2026Confidence-aware depeg routing, extreme-move confirmation, and provenance surfacing
Depeg detection stopped treating every non-null price as equally trustworthy and now routes ambiguous or catastrophic moves through explicit confirmation paths.
- Cached, fallback, low-confidence, and stale primary prices now require confirmation before they can open or close live depeg state
- Extreme moves no longer get dropped just for crossing the old <0.5x or >2x peg guardrail; they enter a dedicated confirmation lane instead
- peg-summary now exposes price provenance and trust state, and the depeg page consumes backend freshness metadata plus real event-history pagination
DetailsHide details
Confidence-aware depeg routing, extreme-move confirmation, and provenance surfacing
Depeg detection stopped treating every non-null price as equally trustworthy and now routes ambiguous or catastrophic moves through explicit confirmation paths.
- Cached, fallback, low-confidence, and stale primary prices now require confirmation before they can open or close live depeg state
- Extreme moves no longer get dropped just for crossing the old <0.5x or >2x peg guardrail; they enter a dedicated confirmation lane instead
- peg-summary now exposes price provenance and trust state, and the depeg page consumes backend freshness metadata plus real event-history pagination
Impact notes
- Cached, fallback, low-confidence, and stale primary prices now require confirmation before they can open or close live depeg state
- Extreme moves no longer get dropped just for crossing the old <0.5x or >2x peg guardrail; they enter a dedicated confirmation lane instead
- peg-summary now exposes price provenance and trust state, and the depeg page consumes backend freshness metadata plus real event-history pagination
v4.5Mar 9, 2026Trusted DEX-price gating for depeg suppression, confirmation, and UI checks
DEX cross-validation now shares an explicit trust policy so thin pools cannot suppress or confirm depegs, and low-confidence rows no longer surface on the public DEX Price Check UI.
- Depeg suppression/confirmation now requires fresh DEX rows with >= $1M aggregate source TVL
- UI-facing dexPriceCheck exposure now requires fresh data with >= $250K aggregate source TVL
- Thin DEX rows can no longer veto new depeg events or promote pending confirmations on their own
DetailsHide details
Trusted DEX-price gating for depeg suppression, confirmation, and UI checks
DEX cross-validation now shares an explicit trust policy so thin pools cannot suppress or confirm depegs, and low-confidence rows no longer surface on the public DEX Price Check UI.
- Depeg suppression/confirmation now requires fresh DEX rows with >= $1M aggregate source TVL
- UI-facing dexPriceCheck exposure now requires fresh data with >= $250K aggregate source TVL
- Thin DEX rows can no longer veto new depeg events or promote pending confirmations on their own
Impact notes
- Depeg suppression/confirmation now requires fresh DEX rows with >= $1M aggregate source TVL
- UI-facing dexPriceCheck exposure now requires fresh data with >= $250K aggregate source TVL
- Thin DEX rows can no longer veto new depeg events or promote pending confirmations on their own
v4.4Mar 2, 2026ReconstructedNo-history coins now return null peg score
Peg score stopped treating coins with neither first-seen supply history nor depeg events as implicitly healthy.
- coinTrackingStart now returns null when both firstSeen and events are absent
- computePegScoreWithWindow now yields null pegScore for insufficient-history coins
- Prevents false perfect-score outcomes on sparse or incomplete datasets
DetailsHide details
No-history coins now return null peg score
Peg score stopped treating coins with neither first-seen supply history nor depeg events as implicitly healthy.
- coinTrackingStart now returns null when both firstSeen and events are absent
- computePegScoreWithWindow now yields null pegScore for insufficient-history coins
- Prevents false perfect-score outcomes on sparse or incomplete datasets
Impact notes
- coinTrackingStart now returns null when both firstSeen and events are absent
- computePegScoreWithWindow now yields null pegScore for insufficient-history coins
- Prevents false perfect-score outcomes on sparse or incomplete datasets
- 71cc096
v4.3Mar 1, 2026ReconstructedYoung-coin fairness and stronger active penalties
Peg score became less permissive for young coins with recurring brief depegs and for currently depegged assets.
- Tracking start formalized as max(firstSeen, fourYearsAgo) with earliest-event fallback
- Per-event severity now applies max(duration penalty, magnitude floor)
- Active-depeg penalty steepened to max(5, absBps/50), capped at 50
DetailsHide details
Young-coin fairness and stronger active penalties
Peg score became less permissive for young coins with recurring brief depegs and for currently depegged assets.
- Tracking start formalized as max(firstSeen, fourYearsAgo) with earliest-event fallback
- Per-event severity now applies max(duration penalty, magnitude floor)
- Active-depeg penalty steepened to max(5, absBps/50), capped at 50
Impact notes
- Tracking start formalized as max(firstSeen, fourYearsAgo) with earliest-event fallback
- Per-event severity now applies max(duration penalty, magnitude floor)
- Active-depeg penalty steepened to max(5, absBps/50), capped at 50
- fd83a46
v4.2Mar 1, 2026ReconstructedDEWS wave-2: yield signal + PSI amplifier
DEWS expanded beyond market microstructure signals by incorporating yield-warning telemetry and systemic PSI context.
- Added 8th DEWS sub-signal: yield anomaly (weight 0.05)
- Introduced systemic amplifier: DEWS boosted up to +30% when PSI < 75
- Cron now reads yield_data.warning_signals and latest PSI sample before scoring
DetailsHide details
DEWS wave-2: yield signal + PSI amplifier
DEWS expanded beyond market microstructure signals by incorporating yield-warning telemetry and systemic PSI context.
- Added 8th DEWS sub-signal: yield anomaly (weight 0.05)
- Introduced systemic amplifier: DEWS boosted up to +30% when PSI < 75
- Cron now reads yield_data.warning_signals and latest PSI sample before scoring
Impact notes
- Added 8th DEWS sub-signal: yield anomaly (weight 0.05)
- Introduced systemic amplifier: DEWS boosted up to +30% when PSI < 75
- Cron now reads yield_data.warning_signals and latest PSI sample before scoring
- dcdefde
v4.1Mar 1, 2026ReconstructedDEWS pool stress calibration fix
Corrected pool-stress scaling error that was inflating DEWS pool signal values.
- avg_pool_stress is now consumed as native 0-100 (removed erroneous x100)
- Pool component returned to intended weighting and magnitude
- Reduced false high-band classifications caused by scale inflation
DetailsHide details
DEWS pool stress calibration fix
Corrected pool-stress scaling error that was inflating DEWS pool signal values.
- avg_pool_stress is now consumed as native 0-100 (removed erroneous x100)
- Pool component returned to intended weighting and magnitude
- Reduced false high-band classifications caused by scale inflation
Impact notes
- avg_pool_stress is now consumed as native 0-100 (removed erroneous x100)
- Pool component returned to intended weighting and magnitude
- Reduced false high-band classifications caused by scale inflation
- 2d8f867
v4.0Mar 1, 2026ReconstructedDEWS launch (7-signal model + 15-minute cron)
Launched the Depeg Early Warning System with per-coin stress scoring and persisted 15-minute snapshots.
- Introduced DEWS base model with 7 sub-signals and weighted-redistribution scoring
- Threat bands established: CALM, WATCH, ALERT, WARNING, DANGER
- compute-dews cron writes rolling stress_signals and daily stress_signal_history snapshots
DetailsHide details
DEWS launch (7-signal model + 15-minute cron)
Launched the Depeg Early Warning System with per-coin stress scoring and persisted 15-minute snapshots.
- Introduced DEWS base model with 7 sub-signals and weighted-redistribution scoring
- Threat bands established: CALM, WATCH, ALERT, WARNING, DANGER
- compute-dews cron writes rolling stress_signals and daily stress_signal_history snapshots
Impact notes
- Introduced DEWS base model with 7 sub-signals and weighted-redistribution scoring
- Threat bands established: CALM, WATCH, ALERT, WARNING, DANGER
- compute-dews cron writes rolling stress_signals and daily stress_signal_history snapshots
- a87876c
- 9bfe791