digiexplorer's DigiDollar "Burn" label vs. the type-3 record — change, not burn? (three mainnet examples, ledger-reconciled)

[eps8sap]

While reconciling a DigiDollar census against getdigidollarstats, I found one place where digiexplorer.info's DigiDollar display and a full DD-ledger walk disagree, and I think it is a label rather than a data problem. Offering it here with receipts in case it is useful.

Observation. For redemptions that carry a type-3 record, the explorer shows the record's amount as "DigiDollar Burn — $X". Walking the DD ledger (every DD output valued from the record that created it), that field is the DD change the redemption re-creates; the burn is everything consumed minus it. Three mainnet examples from the first week after activation:

txid	explorer shows	DD consumed	change re-created	ledger burn
34c67c35…01bdd3 (h 23,871,451)	Burn $100.00	$201.00 (mints $100 + $101)	$100.00	$101.00
58f910ce…c882 (h 23,883,116)	Burn $100.00	$520.00 ($100 change + $420 mint)	$100.00	$420.00
bf4eee6b…04ec (h 23,900,190)	Burn $1.00	$101.00	$1.00	$100.00

Why I'm fairly confident. Under the change reading, the week-one census reconciles to getdigidollarstats at the same height to the cent (net supply $39,835.07 = node; 124 open positions = node), all 29 transfers conserve exactly, and every one of the 13 burns equals the mint amount of the position it closed. Under the burn reading, supply comes out $420 high — the exact amount of the 69a0f7ff… mint that 58f910ce… closed. Our own census made the same misread until this week, so this is offered with some humility: dgbinsights.com/mainnet-report has the corrected figures and the raw records.

Cross-check. An independent decoder (dgb-digidollar-codec 0.2.0, repo) reproduces the explorer's dd_address for every DD output byte for byte, and agrees with the explorer on every field except this label. Each transaction above can be walked in the browser at https://dgbinsights.com/lookup?tx=<txid>, which shows the explorer's own read beside the ledger computation.

If the display intends "declared amount" rather than "burn," a label change suffices; if it intends burn, the computation above is consumed − declared change. Happy to be corrected if I have the semantics of the type-3 record wrong — the source I read it from is src/digidollar/txbuilder.cpp (DD 3 <ddChangeAmountCents>).

— Michael Emery · oracle slot 29 · github.com/dgb-tools