---
title: "Mint/Burn Flow Changelog"
canonical: "https://pharos.watch/methodology/mint-burn-flow-changelog/archive/v5/"
description: "Mint/Burn Flow Changelog - Pharos methodology version history."
---

# Mint/Burn Flow Changelog

[All versions](https://pharos.watch/methodology/mint-burn-flow-changelog/)

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

## v5.2 - GYD retirement from active mint/burn coverage

**Effective:** 2026-04-14

GYD was removed from active mint/burn flow tracking after its cross-chain contract incident left the token functionally dead and moved it to the cemetery dataset.

- Mint/burn flow configs no longer scan the Ethereum GYD token after the asset moved out of the active stablecoin registry
- Public flow coverage counts and stablecoin registry totals now exclude GYD from active surfaces
- Historical rows remain in D1 if previously ingested, but current API scope is driven by the active config registry

Origin: Contemporaneous release record

Commits: Commit provenance not recorded

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

## v5.1 - Canonical-chain mint/burn scope for native issuance tracking

**Effective:** 2026-04-08

Mint/burn coverage now follows each asset's configured issuance chain instead of assuming Ethereum-only scope, with USDai switched to native Arbitrum issuance/redemption tracking and stale non-canonical rows excluded from public aggregates.

- USDai mint/burn tracking now runs on Arbitrum as the canonical native issuance chain instead of Ethereum bridge-transfer noise
- Aggregate and per-coin APIs now read only configured `(stablecoinId, chainId)` pairs so stale historical rows on non-canonical chains do not contaminate public flow metrics
- Cron metadata, coverage helpers, status reconciliation, daily digest, and DEWS mint/burn inputs now honor chain-aware mint/burn scope
- Admin backfill auto-selection and explicit config replay now work across the configured issuance-chain set instead of Ethereum-only

Origin: Contemporaneous release record

Commits: Commit provenance not recorded

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

## v5.0 - Bridge-transfer flow exclusion for omnichain tokens

**Effective:** 2026-04-08

Bridge-aware classification now excludes bridge-transfer mints as well as burns, starting with USDai's LayerZero OFT path, and replay/backfill runs can repair previously inserted rows.

- LayerZero OFT transfers now mark both the mint-side and burn-side event rows as `flowType='bridge_transfer'` so they drop out of counted economic-flow aggregates
- USDai's Ethereum tracker now recognizes the documented USDai OAdapter / LayerZero packet flow instead of treating equal-sized bridge mints and burns as issuance activity
- Bridge classification now runs after all parsed rows are assembled for the config chunk, so mint-side bridge rows are visible to the classifier
- Replay and backfill persistence now updates `flow_type` on existing rows, allowing post-deploy repair of previously ingested bridge-transfer noise

Origin: Contemporaneous release record

Commits: Commit provenance not recorded