---
title: "Yield Intelligence Changelog"
canonical: "https://pharos.watch/methodology/yield-changelog/archive/v7/"
description: "Yield Intelligence Changelog - Pharos methodology version history."
---

# Yield Intelligence Changelog

[All versions](https://pharos.watch/methodology/yield-changelog/)

<a id="changelog-v-7-48"></a>

## v7.48 - dTRINITY sdUSD Multi-Chain Weighted Source

**Effective:** 2026-05-13

dTRINITY dUSD yield now publishes a TVL-weighted sdUSD source across the Ethereum and Fraxtal dStake vaults instead of using only the Ethereum DeFiLlama row.

- `dusd-dtrinity` resolves an exact DeFiLlama weighted pool group for Ethereum and Fraxtal sdUSD
- The synthetic source key starts a new history series so prior Ethereum-only rows are not treated as equivalent 30-day samples
- The dUSD metadata entry stays unchanged because its checked-in collateral and contract data already documents chain-isolated deployments

Origin: Contemporaneous release record

Commits: Commit provenance not recorded

<a id="changelog-v-7-47"></a>

## v7.47 - Avant savUSD ownership correction

**Effective:** 2026-05-13

Avant yield is now attributed to the tracked savUSD senior-tranche wrapper rather than base avUSD, matching Avant's current token documentation.

- `savusd-avant` now owns the Avant native savings pool directly in the yield manifest
- `avusd-avant` is no longer marked yield-bearing because avUSD is the non-yield base asset and savUSD is the yield-accruing route
- Parent-side `avusd-avant` savUSD variant and pool mappings were removed so new yield history publishes under the tracked savUSD asset

Origin: Contemporaneous release record

Commits: Commit provenance not recorded

<a id="changelog-v-7-46"></a>

## v7.46 - Zephyr ZYS direct yield source

**Effective:** 2026-05-12

Zephyr yield is now attributed to the tracked ZYS yield-share wrapper rather than base ZSD, using Zephyr Scanner's historical-return API as a direct protocol source.

- `zys-zephyr-protocol` is tracked as a yield-bearing NAV wrapper over `zsd-zephyr-protocol`
- `protocol-api:zys-zephyr-protocol` reads Zephyr Scanner one-day effective APY and publishes it as `Zephyr Scanner ZYS returns`
- `zsd-zephyr-protocol` remains non-yield-bearing so the base stablecoin does not receive the wrapper's APY row

Origin: Contemporaneous release record

Commits: Commit provenance not recorded

<a id="changelog-v-7-45"></a>

## v7.45 - USG Yield Ownership Correction

**Effective:** 2026-05-08

Tangent USG is no longer treated as a yield-bearing asset because yield accrues in the separate sUSG savings wrapper, not in USG itself.

- `usg-tangent` now carries `yieldBearing: false`, matching Tangent's USG/sUSG split
- `usg-tangent` is removed from intentional yield-gap coverage because it is no longer part of the yield-bearing manifest universe
- The intentional-gap manifest remains reserved for assets that are actually marked yield-bearing but lack a reliable runtime APY source

Origin: Contemporaneous release record

Commits: Commit provenance not recorded

<a id="changelog-v-7-44"></a>

## v7.44 - Solayer sUSD Treasury fallback coverage

**Effective:** 2026-05-05

Solayer sUSD is covered through the rate-derived Treasury fallback lane, while newly added reward-bearing account or restricted strategy assets stay out of runtime yield until a reliable APY source is wired.

- `susd-solayer` now has an explicit rate-derived T-bill fallback strategy in the yield manifest
- Reward-bearing account products and restricted strategy tokens without reliable public APY telemetry are not marked as runtime yield-bearing, so they do not publish misleading zero-strategy yield rows
- The active yield-bearing invariant still requires every marked asset to have a runtime strategy before it can enter live yield rankings

Origin: Contemporaneous release record

Commits: Commit provenance not recorded

<a id="changelog-v-7-43"></a>

## v7.43 - Tracked savings wrappers own their native APY history

**Effective:** 2026-04-22

Base stablecoins no longer publish tracked savings-wrapper APY through parent-owned config or historical series when the wrapper is itself a tracked asset.

- `sUSDe`, `sUSDS`, `sDAI`, `sfrxUSD`, and `scrvUSD` now own the native runtime pool and deterministic rate readers that used to live on `USDe`, `USDS`, `DAI`, `frxUSD`, and `crvUSD`
- Those five base assets no longer advertise wrapper-owned `yieldBearing` metadata or serve the old wrapper APY series through `/api/yield-history`; the historical discontinuity is intentional and reflects corrected ownership rather than a missing backfill
- Parent-side wrapper source keys are filtered immediately at read time and purged on the hourly yield sync path, so misattributed pre-handoff rows do not linger under the base ids after rollout

Origin: Contemporaneous release record

Commits: Commit provenance not recorded

<a id="changelog-v-7-42"></a>

## v7.42 - First-Class Risk Wrapper Yield Assets

**Effective:** 2026-04-21

Yield wrappers whose holder risk differs materially from the base stablecoin now own their yield rows directly instead of publishing through the base asset.

- Cap `stcUSD`, GAIB `sAID`, Main Street `msY`, and K3 `sBOLD` are tracked as first-class yield-bearing NAV/wrapper assets rather than as native yield on cUSD, AID, msUSD, or BOLD
- `stUSDS` uses the generic on-chain ERC-4626 exchange-rate reader because the risk-capital token is distinct from Sky's plain sUSDS savings wrapper and has no standalone DeFiLlama stablecoin row
- Aave Umbrella `stkGHO` is inventoried as an intentional runtime-yield gap until a reliable reward APY source is available, avoiding a misleading zero-yield publication

Origin: Contemporaneous release record

Commits: Commit provenance not recorded

<a id="changelog-v-7-41"></a>

## v7.41 - On-Chain Bootstrap Seeds Excluded From Rolling APY

**Effective:** 2026-04-21

Deterministic on-chain seed rows used only to establish a 7-day exchange-rate anchor no longer count as observed zero-yield samples in rolling APY, excess-yield, stability, or PYS calculations.

- On-chain rows whose first observations were bootstrap `0%` APY placeholders now compute `apy7d`, `apy30d`, `excessYield`, yield stability, and PYS from real APY samples once an anchor exists
- `excessYield` remains defined as `apy30d - benchmarkRate`; detail-page and hero-chip copy now labels it as 30-day based so it is not confused with current APY spread
- Historical seed rows remain in `yield_history` for exchange-rate anchoring, but the evaluator excludes rows with `data_source='onchain'`, `exchange_rate IS NOT NULL`, `apy = 0`, and `apy_base IS NULL` from rolling stats

Origin: Contemporaneous release record

Commits: Commit provenance not recorded

<a id="changelog-v-7-4"></a>

## v7.4 - Pre-Launch Lending Overrides Quarantined

**Effective:** 2026-04-13

Pre-launch assets are now isolated from deterministic lending override publication, so upcoming coins cannot appear in live yield rankings before launch.

- `pusd-polaris` is now an explicit pre-launch intentional gap instead of resolving through a deterministic Silo v2 lending override
- Yield source resolution now skips configured explicit or deterministic lending candidates unless the target asset is in the active stablecoin universe
- The stablecoin metadata registry now keeps pre-launch assets in per-coin files with `status: "pre-launch"`; the legacy `shared/data/stablecoins/pre-launch.json` shell stays empty while upcoming pages and launch alerts continue to work

Origin: Contemporaneous release record

Commits: Commit provenance not recorded

<a id="changelog-v-7-3"></a>

## v7.3 - scrvUSD Current-Rate On-Chain Reader

**Effective:** 2026-04-11

Curve Savings crvUSD now uses a dedicated Yearn V3 profit-unlock reader for current APY instead of the generic 7-day ERC-4626 exchange-rate delta.

- Legacy parent-side `crvusd-curve` rows are quarantined from the generic `convertToAssets(1e18)` Tier 1 reader because that trailing 7-day delta understated Curve's current savings APY
- The new `onchain:scrvusd-curve:scrvusd-current-rate` source reads scrvUSD vault `totalSupply`, `totalAssets`, `profitUnlockingRate`, and `fullProfitUnlockDate` to compute the current daily-compounded APY
- The existing DeFiLlama scrvUSD pool remains as a curated alternative and fallback row, while source-specific history starts fresh under the new current-rate source key

Origin: Contemporaneous release record

Commits: Commit provenance not recorded

<a id="changelog-v-7-2"></a>

## v7.2 - USD.AI Base/Yield Token Split

**Effective:** 2026-04-04

Yield coverage now treats sUSDai as its own tracked yield-bearing NAV token instead of hanging the savings venue off the base USDai page via wrapper indirection.

- `usdai-usd-ai` is no longer treated as a yield-bearing wrapper host, so base USDai stops inheriting sUSDai's savings pool as its native yield source
- New tracked asset `susdai-usd-ai` now owns the existing USD.AI savings pool mapping directly, aligning yield rankings with the dedicated sUSDai detail page and nav-token semantics
- The stale USD.AI wrapper config that pointed at Arbitrum PYUSD as the `sUSDai` variant address is removed, eliminating a concrete address-level misbinding

Origin: Contemporaneous release record

Commits: Commit provenance not recorded

<a id="changelog-v-7-1"></a>

## v7.1 - Explicit Intentional Gaps For Pre-Launch Yield Assets

**Effective:** 2026-04-03

Pre-launch yield-bearing assets without a live runtime source are now emitted as explicit intentional manifest gaps instead of appearing as covered entries with zero strategies.

- `bd-basedollar` is now classified the same way as other pre-launch yield-bearing assets with no live runtime source, so the manifest no longer reports it as a covered entry with zero strategies
- Coverage audits and operator tooling continue to inventory every yield-bearing asset, but pre-launch gaps are now fail-closed and explicit rather than implicit
- The public yield methodology docs and timeline now call out the intentional-gap treatment for these pre-launch assets

Origin: Contemporaneous release record

Commits: Commit provenance not recorded

<a id="changelog-v-7-0"></a>

## v7.0 - Supply-Relative Size Gates For Published Lending Suggestions

**Effective:** 2026-04-03

Published lending-opportunity rows now require observable venue TVL and must be large enough relative to the tracked stablecoin's circulating supply before they can surface as live recommendations.

- For tracked stablecoins, lending-opportunity rows now require `sourceTvlUsd` and must clear `max(existing absolute floor, 0.1% of current supply)` before publication
- This applies across auto-discovered DeFiLlama lending markets, deterministic exact-pool overrides, and supplemental protocol-native lending venues
- TVL-less protocol suggestions no longer fail open into live recommendations; until venue size is observable they are omitted from published lending-opportunity coverage
- Yield methodology docs and changelog entries now document the new supply-relative recommendation gate explicitly

Origin: Contemporaneous release record

Commits: Commit provenance not recorded
