Depeg Tracker and DEWS Changelog: v2 archive
Historical release evidence. Return to current versions and the complete history index.
What this controls
Depeg Tracker and DEWS Changelog: v2 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
v2.1Feb 20, 2026Reconstructed
Four-year peg-score lookback window
Peg scoring moved to an explicit rolling 4-year horizon instead of unbounded historical span.
Impact snapshot
- computePegScoreWithWindow introduced a 4-year tracking cap
- Detail-page peg scores became explicitly lookback-bounded
- Boundary logic was later corrected in v3.2 for firstSeen direction
v2.1Feb 20, 2026ReconstructedFour-year peg-score lookback window
Peg scoring moved to an explicit rolling 4-year horizon instead of unbounded historical span.
- computePegScoreWithWindow introduced a 4-year tracking cap
- Detail-page peg scores became explicitly lookback-bounded
- Boundary logic was later corrected in v3.2 for firstSeen direction
DetailsHide details
v2.1Feb 20, 2026Reconstructed
Four-year peg-score lookback window
Peg scoring moved to an explicit rolling 4-year horizon instead of unbounded historical span.
- computePegScoreWithWindow introduced a 4-year tracking cap
- Detail-page peg scores became explicitly lookback-bounded
- Boundary logic was later corrected in v3.2 for firstSeen direction
Impact notes
- computePegScoreWithWindow introduced a 4-year tracking cap
- Detail-page peg scores became explicitly lookback-bounded
- Boundary logic was later corrected in v3.2 for firstSeen direction
Reconstructed from git commit history.1 commit
- 29c1bdc
v2.0Feb 20, 2026ReconstructedPeg-score severity rebalance + spread penalty
Peg score shifted to stronger magnitude sensitivity and penalized erratic event-size variance.
- Severity penalty changed from sqrt-based to linear (peakBps/100 scaling)
- Added spreadPenalty from event-magnitude standard deviation (cap 15)
- Composite became: 0.5*pegPct + 0.5*severity - activePenalty - spreadPenalty
DetailsHide details
v2.0Feb 20, 2026Reconstructed
Peg-score severity rebalance + spread penalty
Peg score shifted to stronger magnitude sensitivity and penalized erratic event-size variance.
- Severity penalty changed from sqrt-based to linear (peakBps/100 scaling)
- Added spreadPenalty from event-magnitude standard deviation (cap 15)
- Composite became: 0.5*pegPct + 0.5*severity - activePenalty - spreadPenalty
Impact notes
- Severity penalty changed from sqrt-based to linear (peakBps/100 scaling)
- Added spreadPenalty from event-magnitude standard deviation (cap 15)
- Composite became: 0.5*pegPct + 0.5*severity - activePenalty - spreadPenalty
Reconstructed from git commit history.1 commit
- d2954c3