Safety Scores Changelog: v6 archive

USDaf's Asymmetry reserve feed can now qualify for live collateral passthrough when the protocol API snapshot is fresh.

• The adapter now preserves Asymmetry's top-level API timestamp as verified reserve-source freshness.
• Branch symbols are normalized before risk lookup, so casing-only variants such as wBTC no longer degrade the feed.
• No scoring policy changed; the feed still needs fresh independent evidence and an ok sync state.

Contemporaneous release record.

Commit provenance not recorded

Timestamped reserve feeds can now re-enter collateral-quality passthrough when they satisfy the existing freshness and sync-health gates.

• Circle, M0, Mento, and USD.AI reserve adapters now preserve usable upstream disclosure or dashboard timestamps instead of leaving those snapshots marked freshnessMode=unverified.
• Re Protocol and Yuzu mappings now classify newly observed reserve buckets explicitly, so clean fresh snapshots are not degraded as unknown exposure.
• The global gate is unchanged: only fresh, independent, ok sync snapshots with verified or intrinsically current freshness can drive report-card collateral scoring.

Contemporaneous release record.

Commit provenance not recorded

Active-depeg and dependency edge cases now follow the documented Safety Score model more strictly.

• Peg Stability now passes through computePegScore() during active depegs instead of applying the old 65-point peg-dimension cap before the multiplier.
• activeDepegBps now comes from the open depeg event's peak severity, so final Safety Score caps use the same severe-event source as redemption-route impairment.
• Stale redemption-backstop snapshots no longer uplift Liquidity / Exit; the dimension falls back to fresh DEX evidence or NR until the redemption snapshot refreshes.
• Missing upstream dependency scores are applied at the existing 70-point unavailable fallback for their declared weights, and the contagion stress test now propagates transitively through downstream dependency chains.

Contemporaneous release record.

Commit provenance not recorded

Severe active depegs now force redemption uplift to prove current exercisability instead of relying on static route documentation.

• Liquidity / Exit now ignores redemption backstops that are unresolved, low-confidence, or marked impaired by route-availability evidence.
• Active depegs at or above 2500 bps disable static, documented-bound, live-proxy, issuer/API, queue, and estimated redemption uplift.
• Live-direct, dynamic, permissionless routes with atomic or immediate settlement can still contribute during severe depegs because they carry current direct redemption evidence.

Contemporaneous release record.

Commit provenance not recorded

Direct inherited freeze risk now counts two reserve-side collateral classes that were previously under-attributed: custodied BTC wrappers and issuer-seizable tokenized collateral.

• Shared isBlacklistable() now treats centralized-custody BTC wrappers such as WBTC and cbBTC as direct inherited freeze exposure rather than only weak possible clues.
• Issuer-seizable tokenized collateral such as PAXG, XAUT, and reviewed tokenized share symbols such as BOSS joined the direct inherited-freeze signal set introduced in this phase.
• Coins with these reviewed collateral assets gained inherited-freeze treatment in this phase; v7.13 later superseded the reserve-weight gate with the current any-reserve inherited instead of possible.

Contemporaneous release record.

Commit provenance not recorded

NAV wrappers that explicitly wrap a stablecoin now inherit peg risk from the referenced base asset instead of getting an automatic neutral peg multiplier.

• Configured NAV wrappers can now reuse a referenced base stablecoin's pegScore in Safety Score report-card scoring.
• Pure fund-share NAV tokens with no configured peg reference still keep pegScore = NR and the neutral multiplier treatment.
• This specifically closes the loophole where a wrapped stablecoin NAV structure could avoid the stronger v6.93 peg penalty even when the underlying base stablecoin had clear peg risk.

Contemporaneous release record.

Commit provenance not recorded

Peg stability now has more weight in the final grade, and severe live depegs can hard-cap the score regardless of otherwise strong base dimensions.

• PEG_MULTIPLIER_EXPONENT increased from 0.20 to 0.40.
• Active depegs at or above 1000 bps now cap the overall score at D, and active depegs at or above 2500 bps cap it at F.
• activeDepegBps is now exposed in report-card raw inputs so the frontend and stressed-grade recomputation paths apply the same cap logic.

Contemporaneous release record.

Commit provenance not recorded

LUSD now uses direct Liquity v1 system-collateral reads instead of the generic proof-style liveness probe, so clean snapshots qualify as independent live reserve evidence.

• The dedicated liquity-v1 adapter reads getEntireSystemColl() and getEntireSystemDebt() from the official Ethereum TroveManager.
• LUSD reserve snapshots remain a single-bucket 100% ETH view, but the adapter is now registered as independent instead of weak-live-probe.
• This promotes LUSD's clean authoritative reserve snapshots into collateral-quality live passthrough without relaxing the generic gate for other single-asset probes.

Contemporaneous release record.

Commit provenance not recorded

Blacklistability attribution now treats reserve-side freeze clues as first-class signals instead of only trusting explicit slice flags and resolved upstream coin IDs.

• Shared isBlacklistable() now resolves to possible when curated or live reserve labels imply blacklistable stablecoins, wrappers, or CEX/custody rails below the majority threshold.
• Majority direct reserve exposure still resolves to inherited; the new heuristics are there to prevent reserve-side exposure from incorrectly falling through to no.
• Live reserve enrichment and curated reserve evaluation now share the same direct clue detection for named stablecoin baskets and explicit custody/CEX descriptors.
• This does not relax the collateral passthrough gate: static-validated, weak-live-probe, and freshnessMode=unverified reserve feeds remain detail-visible only.

Contemporaneous release record.

Commit provenance not recorded

Blacklistability attribution now separates mutable-contract risk from collateral-inherited freeze risk.

• Shared blacklistability resolution no longer treats centralized-dependent governance as enough evidence for possible on its own.
• Reserve-heavy downstream freeze exposure now surfaces as inherited, which is distinct from mutable-contract risk.
• Inherited status became an explicit upstream-freeze category that can use curated reserve-slice blacklistable markers in addition to upstream stablecoin links; v7.13 later removed the reserve-weight gate.

Contemporaneous release record.

Commit provenance not recorded

Safety Score structure is unchanged, but direct latest-state reserve adapters now stamp explicit on-chain freshness so eligible feeds are no longer excluded by missing timestamp metadata.

• evm-branch-balances snapshots now persist freshnessMode=not-applicable.
• Clean independent branch-balance snapshots can once again override curated collateral quality when their latest reserve_sync_state.last_status is ok.
• This aligns implementation with the existing v6.6 freshness gate rather than introducing a new collateral-scoring rule family.

Contemporaneous release record.

Commit provenance not recorded

Blacklistability attribution now treats centralized-dependent stablecoins as possible by default unless a more specific signal applies.

• Shared blacklistability resolution now falls back to possible for centralized-dependent governance instead of false.
• Reserve-heavy dependency cases still surface as possible-inherited when inherited exposure is the more specific explanation.
• Explicit overrides remain authoritative, including curated false exceptions.

Contemporaneous release record.

Commit provenance not recorded

Safety Score structure is unchanged, but collateral-quality live reserve passthrough now requires stronger freshness evidence before a live feed can override curated collateral scoring.

• Independent live reserve feeds still need a fresh authoritative snapshot whose latest reserve_sync_state.last_status is ok.
• In addition, collateral passthrough now requires scoring-eligible freshness evidence: either a verified timestamp path or a freshnessMode of verified or not-applicable.
• Feeds marked unverified remain available on reserve detail/status surfaces, but they no longer override curated collateral quality in report-card scoring.

Contemporaneous release record.

Commit provenance not recorded

Safety Score structure is unchanged, but the collateral-quality live reserve passthrough is now stricter about evidence quality and warning-bearing feeds.

• Live collateral passthrough now requires a fresh authoritative snapshot whose latest reserve_sync_state.last_status is ok.
• The live reserve adapter registry now separates reserve shape (sourceModel) from evidence strength (evidenceClass).
• single-asset and tether style feeds are now treated as weak-live-probe evidence, so they remain visible on reserve detail/status surfaces but no longer override curated collateral scoring.
• Source-age and material unknown-exposure warnings now degrade reserve sync health and automatically keep those snapshots out of collateral passthrough.

Contemporaneous release record.

Commit provenance not recorded

Safety Score structure is unchanged, but Liquity-style formula routes can now use current on-chain redemption fees when live reserve telemetry is available.

• LUSD and BOLD now reuse live reserve sync metadata for current redemption fee bps instead of always sitting in the generic reviewed-formula bucket.
• These routes remain labeled as formula fee models and eventual-only capacity routes, so Pharos does not present them as having an immediate redeemable buffer.
• If live fee telemetry is unavailable, the liquidity dimension falls back to the prior reviewed-formula treatment.

Contemporaneous release record.

Commit provenance not recorded

Safety Score structure is unchanged, but a narrow class of immutable on-chain redemption routes now counts as stronger exit evidence than heuristic capacity models.

• LUSD and BOLD now use documented-bound eventual redemption capacity instead of generic heuristic supply-full modeling.
• These routes still present as eventual-only, so Pharos does not treat full current supply as an immediate redeemable buffer.
• Liquity-style min 50 bps + baseRate fees remain reviewed formula inputs rather than fixed-fee assumptions.

Contemporaneous release record.

Commit provenance not recorded

Safety Score structure is unchanged, but the collateral-quality live reserve passthrough is now stricter about which hourly reserve feeds qualify.

• Live collateral passthrough now requires a fresh authoritative snapshot: the reserve row must be non-empty and matched to the coin's latest successful sync state.
• Only dynamic-mix and single-bucket feeds count as independent live collateral inputs. validated-static feeds stay visible on reserve detail/status surfaces but no longer override curated collateral scoring.
• Single-bucket live feeds now participate in collateral drift and fallback tracking; the old implicit >= 2 slices gate is no longer the scoring contract.

Contemporaneous release record.

Commit provenance not recorded

Safety Score structure is unchanged, but the Liquidity dimension is now stricter about what redemption evidence can improve it.

• Low-confidence redemption routes remain visible in detail surfaces, but they no longer uplift the Safety Score liquidity dimension.
• When the reused DEX liquidity snapshot is stale, it is no longer blended into effectiveExitScore.
• Redemption detail output now distinguishes immediate redeemable capacity from eventual issuer/protocol redeemability.

Contemporaneous release record.

Commit provenance not recorded

Four structural changes landed together in the safety methodology: a wider custody model, a new chain tier for Solana and BNB Chain, a simpler 2-factor Resilience score, and a steeper 5-band chain penalty.

• Custody model expanded from 3 to 6 tiers: onchain, institutional-top, institutional-regulated, institutional-unregulated, institutional-sanctioned, and cex.
• Added mature-alt-l1 for Solana and BNB Chain with score 45.
• Resilience became (collateral + custody) / 2; blacklist capability is now descriptive only.
• Chain-risk penalty moved to 5 bands, and wrapper governance became exempt from that penalty.

Contemporaneous release record.

Commit provenance not recorded