chore: run ntt pull -> update pauser base

[rplusq]

No description provided.

[Copilot]

Pull Request Overview

This pull request updates the pauser addresses in the mainnet deployment configuration following an ntt pull command. The change replaces the old pauser address with a new one across multiple configuration entries.

• Updated pauser address from 0xdeCafd85661B67bA9c43f3B4DAeF5AD02f8CEa5F to 0x2D723C20Cb297E8F3F8cd885584623F97B5A7583

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[claude]

Claude finished @rplusq's task —— View job

---

Code Review: PR #40

Todo List:

• Read the deployment configuration file
• Review the pauser address changes
• Check for security implications
• Provide feedback

---

Summary

This PR updates the pauser address for the Base chain only in the mainnet NTT deployment configuration. The change was generated by running ntt pull, which synchronizes the local configuration with the deployed on-chain state.

Changes Made

File: ntt/mainnet_deployment.json

• Base chain pauser updated (2 locations):
  • Line 63: transceivers.wormhole.pauser
  • Line 74: pauser
  • Old: 0xdeCafd85661B67bA9c43f3B4DAeF5AD02f8CEa5F
  • New: 0x2D723C20Cb297E8F3F8cd885584623F97B5A7583

Review Findings

⚠️ Inconsistency Concern (Non-blocking)

Issue: The pauser address was updated for Base chain only, but not for Ethereum and Optimism chains, which still use the old address 0xdeCafd85661B67bA9c43f3B4DAeF5AD02f8CEa5F.

Current state in ntt/mainnet_deployment.json:

• Ethereum (lines 15, 26): Uses 0xdeCafd85661B67bA9c43f3B4DAeF5AD02f8CEa5F (old)
• Optimism (lines 39, 50): Uses 0xdeCafd85661B67bA9c43f3B4DAeF5AD02f8CEa5F (old)
• Base (lines 63, 74): Uses 0x2D723C20Cb297E8F3F8cd885584623F97B5A7583 (NEW)
• Solana: No pauser field (expected for Solana)

Questions to consider:

1. Is this intentional? Should Base have a different pauser than Ethereum/Optimism?
2. Or is this a phased rollout where Base was updated first and Ethereum/Optimism will follow?
3. Since this came from ntt pull, does this reflect the actual on-chain state across all chains?

Recommendation: Verify whether the pauser address should be consistent across all EVM chains (Ethereum, Optimism, Base) or if Base intentionally uses a different pauser for operational reasons.

Security Considerations

✅ No immediate security concerns - The change appears to be an administrative update to the pauser role, likely reflecting an on-chain governance action or operational security improvement (rotating the pauser key/address).

Note: Since this was generated by ntt pull, it reflects the actual deployed state on-chain, so the change has already been executed via governance/admin transactions.

---