Skip to main content
Pharos

Depeg Tracker and DEWS Changelog: v5 archive

Historical release evidence. Return to current versions and the complete history index.

What this controls

Depeg Tracker and DEWS Changelog: v5 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.

Latest version

v5.99May 13, 2026

Structured Yield Source-Risk DEWS Input

DEWS now consumes populated Yield Intelligence source-risk and rank-attribution fields inside the existing Yield Anomaly sub-signal, while neutral or missing structured rows remain no-ops.

Impact snapshot

  • The `yield` sub-signal can now score populated `sourceRisk.rewardShare`, `sourceRisk.sourceDepthRatio`, `sourceRisk.sourceAgeSeconds`, `sourceRisk.sourceSwitchCount30d`, `sourceRisk.sourceRiskPenalty`, high reviewed `venueRiskTier`, and rank-attribution source-risk/source-switch drivers
  • Structured yield evidence is additive with existing `yield_data.warning_signals` and still caps the Yield Anomaly sub-signal at 100
  • Neutral structured rows do not become available zero-stress signals, so missing or neutral evidence does not dilute the DEWS weighted average
  • The DEWS source-state loader reads structured evidence from the published `yield-rankings` cache and preserves legacy warning-only behavior when that cache is missing or malformed
v5.99May 13, 2026

Structured Yield Source-Risk DEWS Input

DEWS now consumes populated Yield Intelligence source-risk and rank-attribution fields inside the existing Yield Anomaly sub-signal, while neutral or missing structured rows remain no-ops.

  • The `yield` sub-signal can now score populated `sourceRisk.rewardShare`, `sourceRisk.sourceDepthRatio`, `sourceRisk.sourceAgeSeconds`, `sourceRisk.sourceSwitchCount30d`, `sourceRisk.sourceRiskPenalty`, high reviewed `venueRiskTier`, and rank-attribution source-risk/source-switch drivers
  • Structured yield evidence is additive with existing `yield_data.warning_signals` and still caps the Yield Anomaly sub-signal at 100
  • Neutral structured rows do not become available zero-stress signals, so missing or neutral evidence does not dilute the DEWS weighted average
  • The DEWS source-state loader reads structured evidence from the published `yield-rankings` cache and preserves legacy warning-only behavior when that cache is missing or malformed
Details

Impact notes

  • The `yield` sub-signal can now score populated `sourceRisk.rewardShare`, `sourceRisk.sourceDepthRatio`, `sourceRisk.sourceAgeSeconds`, `sourceRisk.sourceSwitchCount30d`, `sourceRisk.sourceRiskPenalty`, high reviewed `venueRiskTier`, and rank-attribution source-risk/source-switch drivers
  • Structured yield evidence is additive with existing `yield_data.warning_signals` and still caps the Yield Anomaly sub-signal at 100
  • Neutral structured rows do not become available zero-stress signals, so missing or neutral evidence does not dilute the DEWS weighted average
  • The DEWS source-state loader reads structured evidence from the published `yield-rankings` cache and preserves legacy warning-only behavior when that cache is missing or malformed
Commit provenance not recorded
    v5.98May 12, 2026

    Registry-backed depeg source families

    Depeg trust and pending-confirmation policy now resolve source families from pricing-source registry metadata, expanding composite labels before family and authority checks.

    • Composite labels such as `coingecko+geckoterminal` are expanded before source-family checks, so they no longer behave like unknown standalone sources
    • CoinGecko variants, DefiLlama list/detail/contract variants, and CoinMarketCap-style list aggregators remain correlated families for confirmation and severe-downside corroboration
    • Fallback/search lanes remain non-authoritative, while hard market, oracle, protocol, and promoted DEX protocol lanes keep explicit registry-backed families
    Details

    Impact notes

    • Composite labels such as `coingecko+geckoterminal` are expanded before source-family checks, so they no longer behave like unknown standalone sources
    • CoinGecko variants, DefiLlama list/detail/contract variants, and CoinMarketCap-style list aggregators remain correlated families for confirmation and severe-downside corroboration
    • Fallback/search lanes remain non-authoritative, while hard market, oracle, protocol, and promoted DEX protocol lanes keep explicit registry-backed families
    Commit provenance not recorded
      v5.97May 11, 2026

      Source-family confirmation and zero-event backfill parity

      Pending depeg confirmation now requires source-family-aware corroboration, stricter DEX/pool independence, refreshed peg references, and canonical confirmer provenance; trusted zero-event backfills now remove stale backfill rows.

      • CoinGecko/DefiLlama off-chain confirmation is selected from the primary agreeSources family set, so same-family circular evidence cannot promote large-cap pending rows on its own
      • Aggregate DEX confirmation requires at least two fresh protocol groups, and pool challengers count distinct protocol/source-family groups while preserving the documented >= $5M single-pool exception
      • Promoted pending rows use refreshed peg references, canonical confirmation_sources keys, and the worst trustworthy confirmer price when setting peak severity
      • Backfill dry-runs and mutating runs now agree when a trusted replay finds zero events: stale source='backfill' rows are previewed and then deleted
      Details

      Impact notes

      • CoinGecko/DefiLlama off-chain confirmation is selected from the primary agreeSources family set, so same-family circular evidence cannot promote large-cap pending rows on its own
      • Aggregate DEX confirmation requires at least two fresh protocol groups, and pool challengers count distinct protocol/source-family groups while preserving the documented >= $5M single-pool exception
      • Promoted pending rows use refreshed peg references, canonical confirmation_sources keys, and the worst trustworthy confirmer price when setting peak severity
      • Backfill dry-runs and mutating runs now agree when a trusted replay finds zero events: stale source='backfill' rows are previewed and then deleted
      • Historical replay applies the live supply floor from historical supply or current stablecoins-cache supply; when both are absent, existing backfill rows are preserved
      Commit provenance not recorded
        v5.96May 5, 2026

        ARS native-peg and KGS FX corroboration

        Direct native-peg corroboration now includes ARS where CoinGecko exposes a supported quote currency, while KGS stays on the secondary daily FX path and deterministic bounds because CoinGecko does not expose a native KGS quote.

        • WARS (ARS) live and pending depeg checks can use fresh native CoinGecko quotes before trusting USD/FX-derived divergence on its own
        • KGST (KGS) depeg checks use the secondary daily FX mirror and hardcoded validation bounds rather than an unsupported CoinGecko KGS quote
        • Historical replay behavior is unchanged except that assets with native ARS market history can prefer that direct native series when available
        Details

        Impact notes

        • WARS (ARS) live and pending depeg checks can use fresh native CoinGecko quotes before trusting USD/FX-derived divergence on its own
        • KGST (KGS) depeg checks use the secondary daily FX mirror and hardcoded validation bounds rather than an unsupported CoinGecko KGS quote
        • Historical replay behavior is unchanged except that assets with native ARS market history can prefer that direct native series when available
        Commit provenance not recorded
          v5.95Apr 18, 2026

          Cross-asset contagion amplifier

          DEWS now applies a bounded per-peg-type contagion amplifier (max 1.2x) derived from the same cycle's first-pass DANGER/WARNING bands, on top of the existing systemic PSI amplifier.

          • A tracked stablecoin entering DANGER/WARNING now raises other same-peg-type coins by up to 15% under current constants (1.15x / 1.08x); the amplifier is defensively capped at 20%
          • First-pass coins that themselves are DANGER/WARNING do not contagion-amplify themselves
          • Amplifier is clamped, explainable (no learned weights), and surfaced on /api/stress-signals as amplifiers.contagion
          Details

          Impact notes

          • A tracked stablecoin entering DANGER/WARNING now raises other same-peg-type coins by up to 15% under current constants (1.15x / 1.08x); the amplifier is defensively capped at 20%
          • First-pass coins that themselves are DANGER/WARNING do not contagion-amplify themselves
          • Amplifier is clamped, explainable (no learned weights), and surfaced on /api/stress-signals as amplifiers.contagion
          Commit provenance not recorded
            v5.94Apr 18, 2026

            Pool-confirmation hardening, backfill atomicity, confirmation-provenance surfacing

            Pool-only pending promotion now requires 2 pools or >= $5M TVL; backfill delete+insert share a batch; off-chain confirmation is circuit-breaker-guarded; promoted depeg events now persist confirmation_sources and pending_reason.

            • Single-pool manipulation can no longer unilaterally promote a pending depeg (bar = 2 pools OR one pool with >= $5M TVL)
            • A worker interruption during backfill no longer leaves a coin with zero depeg rows
            • A CoinGecko/DefiLlama outage no longer hammers the endpoint for 45 min per pending row
            • Promoted events carry confirmation_sources (e.g. 'DEX+CEX') and pending_reason (e.g. 'large-cap+low-confidence') for ex-post diagnostics
            Details

            Impact notes

            • Single-pool manipulation can no longer unilaterally promote a pending depeg (bar = 2 pools OR one pool with >= $5M TVL)
            • A worker interruption during backfill no longer leaves a coin with zero depeg rows
            • A CoinGecko/DefiLlama outage no longer hammers the endpoint for 45 min per pending row
            • Promoted events carry confirmation_sources (e.g. 'DEX+CEX') and pending_reason (e.g. 'large-cap+low-confidence') for ex-post diagnostics
            • DEWS liquidity sub-signal fails closed when both 7-day anchors are missing instead of silently contributing 0
            Commit provenance not recorded
              v5.93Apr 15, 2026

              Blacklist signal coverage follows direct EVM wave

              DEWS blacklist-activity input now follows the direct EVM blacklist tracker expansion, adding supported event-count stress signals for FDUSD, BRZ, AUSD, MNEE, EURI, USDQ, USDO, USDX, AID, TGBP, EURC, and BUIDL where those assets are otherwise DEWS-eligible.

              • The shared supported blacklist symbol set now includes the direct EVM coverage wave
              • DEWS remains coupled to that shared live tracker set instead of maintaining a separate symbol list
              • Non-USD amount valuation remains owned by the blacklist tracker; DEWS uses event counts only
              Details

              Impact notes

              • The shared supported blacklist symbol set now includes the direct EVM coverage wave
              • DEWS remains coupled to that shared live tracker set instead of maintaining a separate symbol list
              • Non-USD amount valuation remains owned by the blacklist tracker; DEWS uses event counts only
              Commit provenance not recorded
                v5.92Apr 15, 2026

                Blacklist signal coverage follows first-wave tracker expansion

                DEWS blacklist-activity input now follows the expanded live blacklist tracker symbol set, adding first-wave issuer-intervention signals for USDG, RLUSD, U, USDtb, and A7A5 where those assets are otherwise DEWS-eligible.

                • The shared supported blacklist symbol set now includes USDG, RLUSD, U, USDTB, and A7A5
                • DEWS continues to derive blacklist-signal eligibility from that shared set instead of maintaining a separate list
                • A7A5's blacklist signal can participate as event-count stress only; non-USD amount valuation remains owned by the blacklist tracker ledger
                Details

                Impact notes

                • The shared supported blacklist symbol set now includes USDG, RLUSD, U, USDTB, and A7A5
                • DEWS continues to derive blacklist-signal eligibility from that shared set instead of maintaining a separate list
                • A7A5's blacklist signal can participate as event-count stress only; non-USD amount valuation remains owned by the blacklist tracker ledger
                Commit provenance not recorded
                  v5.91Apr 11, 2026

                  Conservative DEWS freshness and zero-supply current-row retirement

                  DEWS aggregate responses now expose oldest-row lag separately, and eligible assets with no current circulating supply no longer keep stale current radar rows.

                  • The aggregate `/api/stress-signals` response preserves `updatedAt` as the newest row used for freshness headers while adding `oldestComputedAt` as a body-only lag diagnostic
                  • The DEWS cron now retires current `stress_signals` rows for PSI-eligible assets that are explicitly present in the stablecoins cache with zero current supply, without deleting daily history
                  • Last-valid cached rows still remain available for coins that have positive current supply but insufficient signal coverage in an individual cycle
                  Details

                  Impact notes

                  • The aggregate `/api/stress-signals` response preserves `updatedAt` as the newest row used for freshness headers while adding `oldestComputedAt` as a body-only lag diagnostic
                  • The DEWS cron now retires current `stress_signals` rows for PSI-eligible assets that are explicitly present in the stablecoins cache with zero current supply, without deleting daily history
                  • Last-valid cached rows still remain available for coins that have positive current supply but insufficient signal coverage in an individual cycle
                  Commit provenance not recorded
                    v5.9Apr 8, 2026

                    Direction-true confirmation, pending refreshes, and DEWS live-trust alignment

                    Pending depeg incidents now track live first/last/peak state, confirmation requires same-direction corroboration, and DEWS divergence reuses the live depeg DEX trust floor.

                    • Pending rows are now refreshed while they wait for confirmation, preserving first-seen timestamps but updating last-seen and worst-seen state for the active direction
                    • Pending confirmation now treats opposite-side secondary evidence as contradiction instead of support, and native-quote recovery no longer persists contradictory `recovery_price` values
                    • DEWS divergence now ignores fresh-but-thin DEX rows unless they pass the same `$1M` live depeg trust gate, while the repair path refreshes current rows and prunes unrecomputable daily history from the Mar 9, 2026 trust-floor boundary onward
                    Details

                    Impact notes

                    • Pending rows are now refreshed while they wait for confirmation, preserving first-seen timestamps but updating last-seen and worst-seen state for the active direction
                    • Pending confirmation now treats opposite-side secondary evidence as contradiction instead of support, and native-quote recovery no longer persists contradictory `recovery_price` values
                    • DEWS divergence now ignores fresh-but-thin DEX rows unless they pass the same `$1M` live depeg trust gate, while the repair path refreshes current rows and prunes unrecomputable daily history from the Mar 9, 2026 trust-floor boundary onward
                    Commit provenance not recorded
                      v5.8Apr 7, 2026

                      Daily-confirmed native-peg historical replay

                      Supported non-USD fiat historical replay now treats native-fiat CoinGecko history as a day-scale confirmation lane instead of trusting thin hourly native prints on their own.

                      • Historical native-fiat replay now uses daily points plus a two-point confirmation window across 36 hours before opening normal non-USD fiat backfill events
                      • Extreme single-point native crashes of 5,000 bps or more are still preserved even when the native historical confirmation rule would otherwise suppress them
                      • Broad non-USD backfill repairs can now use authenticated CoinGecko market-chart transport consistently through the admin/backfill path, reducing false rebuild drift during large historical cleanups
                      Details

                      Impact notes

                      • Historical native-fiat replay now uses daily points plus a two-point confirmation window across 36 hours before opening normal non-USD fiat backfill events
                      • Extreme single-point native crashes of 5,000 bps or more are still preserved even when the native historical confirmation rule would otherwise suppress them
                      • Broad non-USD backfill repairs can now use authenticated CoinGecko market-chart transport consistently through the admin/backfill path, reducing false rebuild drift during large historical cleanups
                      Commit provenance not recorded
                        v5.7Apr 7, 2026

                        Launch-date peg-score anchors for older tracked assets

                        PegScore tracking windows now prefer curated launch dates over late-arriving supply-history coverage when the asset metadata provides a trustworthy launch anchor.

                        • PegScore now uses a curated launch date as the age anchor when one is available, falling back to earliest supply-history coverage only when no launch date is curated
                        • Older tracked assets with late `supply_history` coverage no longer appear artificially young in the peg-score window
                        • BRZ now anchors peg-score tracking to its July 19, 2019 launch date instead of a March 2025 supply-history coverage artifact
                        Details

                        Impact notes

                        • PegScore now uses a curated launch date as the age anchor when one is available, falling back to earliest supply-history coverage only when no launch date is curated
                        • Older tracked assets with late `supply_history` coverage no longer appear artificially young in the peg-score window
                        • BRZ now anchors peg-score tracking to its July 19, 2019 launch date instead of a March 2025 supply-history coverage artifact
                        Commit provenance not recorded
                          v5.6Apr 7, 2026

                          Generalized native-peg routing and replay for non-USD fiat assets

                          Live and pending depeg routing now generalize the native-peg corroboration lane across the supported non-USD fiat set, and historical replay prefers native fiat market history where CoinGecko exposes it.

                          • Fresh direct native-peg quotes can now veto, sustain, or resolve live depeg state for supported EUR/CHF/GBP/JPY/SGD/AUD/CAD/BRL/IDR/TRY/ZAR/PHP/MXN/RUB/CNH-style fiat pegs instead of remaining effectively BRL-only
                          • Pending confirmation prefers that same direct native quote first whenever CoinGecko exposes the matching fiat pair, reducing false confirmations from USD/FX reference drift
                          • Historical backfill now replays supported non-USD fiat assets against direct native fiat price history and a native `1.0` peg when that series exists, which removes large classes of synthetic backfill events caused by USD/FX mismatch
                          Details

                          Impact notes

                          • Fresh direct native-peg quotes can now veto, sustain, or resolve live depeg state for supported EUR/CHF/GBP/JPY/SGD/AUD/CAD/BRL/IDR/TRY/ZAR/PHP/MXN/RUB/CNH-style fiat pegs instead of remaining effectively BRL-only
                          • Pending confirmation prefers that same direct native quote first whenever CoinGecko exposes the matching fiat pair, reducing false confirmations from USD/FX reference drift
                          • Historical backfill now replays supported non-USD fiat assets against direct native fiat price history and a native `1.0` peg when that series exists, which removes large classes of synthetic backfill events caused by USD/FX mismatch
                          Commit provenance not recorded
                            v5.5Apr 7, 2026

                            Direct native-peg corroboration for BRL depeg routing

                            Live and pending depeg routing now checks a fresh direct native-peg quote for supported non-USD fiat assets before trusting a USD-price-versus-FX-reference divergence on its own.

                            • BRZ-style depegs can now be vetoed or resolved by a fresh direct BRL quote when the USD/FX-derived signal is back inside threshold or points the other way
                            • Pending confirmation prefers the fresh direct native-peg quote over a weaker derived USD cross-check when CoinGecko exposes that native pair
                            • Prevents thin BRL reference mismatches from opening, sustaining, or confirming false depeg rows while still preserving genuine native-peg stress
                            Details

                            Impact notes

                            • BRZ-style depegs can now be vetoed or resolved by a fresh direct BRL quote when the USD/FX-derived signal is back inside threshold or points the other way
                            • Pending confirmation prefers the fresh direct native-peg quote over a weaker derived USD cross-check when CoinGecko exposes that native pair
                            • Prevents thin BRL reference mismatches from opening, sustaining, or confirming false depeg rows while still preserving genuine native-peg stress
                            Commit provenance not recorded
                              v5.4Apr 7, 2026

                              Thin-fiat peg-reference fail-closed and corroborated primary recovery

                              Live depeg state now fails closed when thin non-USD fiat peg references lose their FX fallback, while fresh multi-source primary agreement can retire stale live rows once the coin is back inside threshold.

                              • Thin fiat peg groups with fewer than 3 live contributors now require cached FX fallback before they can open, update, or resolve live depeg state
                              • Fresh non-cached multi-source primary agreement can now close an already-open live event after recovery even if that source mix is still too soft to open new events directly
                              • Prevents BRL-style peer-median false positives from both opening new live rows and lingering as active depegs after the peg reference normalizes
                              Details

                              Impact notes

                              • Thin fiat peg groups with fewer than 3 live contributors now require cached FX fallback before they can open, update, or resolve live depeg state
                              • Fresh non-cached multi-source primary agreement can now close an already-open live event after recovery even if that source mix is still too soft to open new events directly
                              • Prevents BRL-style peer-median false positives from both opening new live rows and lingering as active depegs after the peg reference normalizes
                              Commit provenance not recorded
                                v5.3Apr 6, 2026

                                DEWS flow baseline continuity on quiet 24-hour windows

                                DEWS no longer drops the mint/burn flow signal just because the latest 24-hour window had zero activity while a mature 30-day baseline still exists.

                                • Coins with >= 7 days of mint/burn history now keep the flow signal available even when the latest 24-hour bucket is quiet
                                • A zero-flow day now contributes zero flow stress instead of silently redistributing the flow weight away from the score
                                • DEWS cron assembly now reflects the documented mint/burn-baseline semantics for mature tracked coins
                                Details

                                Impact notes

                                • Coins with >= 7 days of mint/burn history now keep the flow signal available even when the latest 24-hour bucket is quiet
                                • A zero-flow day now contributes zero flow stress instead of silently redistributing the flow weight away from the score
                                • DEWS cron assembly now reflects the documented mint/burn-baseline semantics for mature tracked coins
                                Commit provenance not recorded
                                  v5.2Apr 3, 2026

                                  Corroborated DEX recovery gating for live depeg state

                                  Aggregate DEX bridge rows no longer count as sufficient evidence on their own for ambiguous-primary recoveries or recovery-style event suppression.

                                  • DEX-assisted live recovery now requires at least two corroborating protocol-level DEX groups inside threshold, not just one trusted aggregate row
                                  • Large challenger pools can veto ambiguous-primary DEX recoveries when they still show the old depeg direction
                                  • New-event suppression and other aggregate-DEX-driven state mutations now share that stricter corroboration policy, reducing synthetic split events on chronically depegged coins
                                  Details

                                  Impact notes

                                  • DEX-assisted live recovery now requires at least two corroborating protocol-level DEX groups inside threshold, not just one trusted aggregate row
                                  • Large challenger pools can veto ambiguous-primary DEX recoveries when they still show the old depeg direction
                                  • New-event suppression and other aggregate-DEX-driven state mutations now share that stricter corroboration policy, reducing synthetic split events on chronically depegged coins
                                  Commit provenance not recorded
                                    v5.1Mar 31, 2026

                                    Ongoing depeg continuity over DEX-only contradiction

                                    Already-open depeg events no longer auto-close just because a trusted aggregate DEX row temporarily moves back inside the threshold while the primary path still shows the same-direction depeg.

                                    • Same-direction DEX disagreement is now advisory for ongoing events instead of forcing a synthetic recovery boundary
                                    • Open depeg rows remain continuous until the standard recovery path confirms a sub-threshold resolution
                                    • Prevents repeated event fragmentation on chronically depegged assets when aggregate DEX pricing briefly snaps back toward peg
                                    Details

                                    Impact notes

                                    • Same-direction DEX disagreement is now advisory for ongoing events instead of forcing a synthetic recovery boundary
                                    • Open depeg rows remain continuous until the standard recovery path confirms a sub-threshold resolution
                                    • Prevents repeated event fragmentation on chronically depegged assets when aggregate DEX pricing briefly snaps back toward peg
                                    Commit provenance not recorded
                                      v5.0Mar 28, 2026

                                      DEWS blacklist coverage parity and thin-peg FX fallback parity

                                      DEWS now applies issuer-freeze signal coverage to the full live blacklistable set and derives thin non-USD peg references with the same cached FX fallback path used elsewhere in the peg-aware pipeline.

                                      • Blacklist signal coverage is now derived from the shared supported blacklist symbol set, so PYUSD and USD1 receive the same DEWS blacklist input treatment as USDC, USDT, PAXG, and XAUT
                                      • Thin non-USD DEWS divergence inputs now use cached `fxFallbackRates` from the stablecoins payload instead of relying only on sparse peer medians
                                      • DEWS input semantics now match the documented blacklist coverage and the live depeg / peg-summary FX-reference path
                                      Details

                                      Impact notes

                                      • Blacklist signal coverage is now derived from the shared supported blacklist symbol set, so PYUSD and USD1 receive the same DEWS blacklist input treatment as USDC, USDT, PAXG, and XAUT
                                      • Thin non-USD DEWS divergence inputs now use cached `fxFallbackRates` from the stablecoins payload instead of relying only on sparse peer medians
                                      • DEWS input semantics now match the documented blacklist coverage and the live depeg / peg-summary FX-reference path
                                      Commit provenance not recorded