USAT Reconfiguration

resolveDVNAddresses ignores its dvnNamesOrAddresses argument and always returns the hardcoded LayerZero Labs and USDT0 addresses. It also has no Anchorage entry. Consequently, the Celo verifier derives an expected required-DVN count of two even though layerzero-usat.config.ts now requires LayerZero Labs, USDT0 and Anchorage. The same defect exists in scripts/usat-oAdapterUpgradeable-deployment-config-check.ts:254-266 for Ethereum. This can hide a failed or omitted configuration transaction. For example, the current Celo deployment still has only the original two required DVNs in its send and receive ULN configurations. The verifier nevertheless reports Required DVNs: 2 (expected: 2), says that the ULN configuration matches the LayerZero config and exits successfully. An operator relying on this result could conclude that Anchorage is required when the intended third-DVN policy is not active.

Resolve every entry supplied in dvnNamesOrAddresses instead of replacing the argument with a fixed list. Add Anchorage to each chain mapping, reject unknown names and compare the exact resolved set and count against the live ULN configuration.