Mint/Burn Flow Changelog: v2 archive
Historical release evidence. Return to current versions and the complete history index.
What this controls
Mint/Burn Flow 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
Grade-aware flight-to-quality classification
Flight-to-quality shifted from static safe-haven lists to report-card score buckets, with fallback only when grade data is stale or missing.
Impact snapshot
- Safe/risky FTQ buckets now derive from report-card scores (safe >= 65, risky < 50, neutral ignored)
- Static safe-haven sets are now fallback-only for unavailable or stale report-card cache
- Largest-event attribution aligned to requested window semantics in aggregate mode
v2.1Mar 1, 2026ReconstructedGrade-aware flight-to-quality classification
Flight-to-quality shifted from static safe-haven lists to report-card score buckets, with fallback only when grade data is stale or missing.
- Safe/risky FTQ buckets now derive from report-card scores (safe >= 65, risky < 50, neutral ignored)
- Static safe-haven sets are now fallback-only for unavailable or stale report-card cache
- Largest-event attribution aligned to requested window semantics in aggregate mode
DetailsHide details
Grade-aware flight-to-quality classification
Flight-to-quality shifted from static safe-haven lists to report-card score buckets, with fallback only when grade data is stale or missing.
- Safe/risky FTQ buckets now derive from report-card scores (safe >= 65, risky < 50, neutral ignored)
- Static safe-haven sets are now fallback-only for unavailable or stale report-card cache
- Largest-event attribution aligned to requested window semantics in aggregate mode
Impact notes
- Safe/risky FTQ buckets now derive from report-card scores (safe >= 65, risky < 50, neutral ignored)
- Static safe-haven sets are now fallback-only for unavailable or stale report-card cache
- Largest-event attribution aligned to requested window semantics in aggregate mode
- dcdefde
- c1c1839
v2.0Mar 1, 2026ReconstructedUSDT treasury-event capture and partial-data gauge support
Coverage and scoring robustness were upgraded to capture USDT treasury mint/burn events and keep the gauge active during early-history ramp.
- Added `startBlock` per config for near-history initialization instead of scanning from genesis
- USDT now tracks `Issue` and `Redeem` events that do not emit standard `Transfer` mints/burns
- Gauge now computes from available non-null FIS inputs instead of returning null when any coin lacks sufficient history
DetailsHide details
USDT treasury-event capture and partial-data gauge support
Coverage and scoring robustness were upgraded to capture USDT treasury mint/burn events and keep the gauge active during early-history ramp.
- Added `startBlock` per config for near-history initialization instead of scanning from genesis
- USDT now tracks `Issue` and `Redeem` events that do not emit standard `Transfer` mints/burns
- Gauge now computes from available non-null FIS inputs instead of returning null when any coin lacks sufficient history
Impact notes
- Added `startBlock` per config for near-history initialization instead of scanning from genesis
- USDT now tracks `Issue` and `Redeem` events that do not emit standard `Transfer` mints/burns
- Gauge now computes from available non-null FIS inputs instead of returning null when any coin lacks sufficient history
- 2144236
- 1eddad0