forge verify-bytecode hangs on runtime code match for contract deployed with CREATE2 #13184

Component

Forge

Have you ensured that all of these are up to date?

• Foundry
• Foundryup

What version of Foundry are you on?

forge Version: 1.5.1-stable Commit SHA: b0a9dd9 Build Timestamp: 2025-12-22T11:39:01.425730780Z (1766403541) Build Profile: maxperf

What version of Foundryup are you on?

foundryup: 1.5.0

What command(s) is the bug in?

forge verify-bytecode

Operating System

Linux

Describe the bug

I'm trying to verify that a deployed Morpho V2 vault matches it's audit report.

Here's the relevant repo and commit:
morpho-org/vault-v2@6f2af6602e05d9e123a87c1067712a4566608044

I cloned the repo, installed the dependencies and checked out that specific commit, then I ran:

forge verify-bytecode 0xBeefF08dF54897e7544aB01d0e86f013DA354111 VaultV2 --constructor-args 0xD700038b3f8d2F1a8193F35d7dD25c02e7155427 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48

The result is that the creation code matches partially, but then the command hangs forever against a remote node (tried with paid endpoints from Alchemy and Tenderly).

> Verifying bytecode for contract VaultV2 at address 0xBeefF08dF54897e7544aB01d0e86f013DA354111
[⠊] Compiling...
No files changed, compilation skipped
Creation code matched with status partial

I'm not entirely sure if this has to do with the use of CREATE2. I also couldn't find a way to specify the salt parameter for this command in the documentation.