HookModule.read() always derives when given a Hook Config

[ltyu]

Problem

Currently when running warp apply, the function eventually calls EvmERC20WarpModule.updateExistingHook(), which initializes the EvmHookModule with the actualConfig.hook.

hyperlane-monorepo/typescript/sdk/src/token/EvmERC20WarpModule.ts

Lines 523 to 528 in 4383086

	const hookModule = new EvmHookModule(
	this.multiProvider,
	{
	chain: this.args.chain,
	config: actualConfig.hook,
	addresses: {

When hookModule.update(expectedConfig.hook!) is called, await this.read() is also called, which derives the hookConfig again.

Since the hookConfig was previously derived by the WarpModule, this is extra work. This is problematic with large hook configs such as the Mailbox's default hook, which adds significant time to warp apply and potentially other future updates (core apply).

Solution

• Consider updating the HookModule to store the actualConfig and assume that this is derived previously and return this in the read()