--legacy?

[austintgriffith]

Issue with Arbitrum Deployments using --legacy flag

Recently I've been doing a lot of deployments on Arbitrum for my game and a lot of times I need to remove the --legacy from the make file... well, claude removes it for me -- then everything works

here is a writeup of why according to claude:

The current Makefile in Scaffold-ETH 2's Foundry package uses the --legacy flag for all non-localhost deployments (line 21). This causes deployment failures on Arbitrum (and potentially other modern L2s) because the legacy transaction format doesn't properly handle EIP-1559 gas pricing. When deploying multiple contracts in sequence, Foundry estimates gas prices at the start, but if the base fee increases between transactions (common on active networks), subsequent transactions fail with "max fee per gas less than block base fee" errors. The fix is to remove the --legacy flag for networks that support EIP-1559 (like Arbitrum, Optimism, Base) and add a reasonable --priority-gas-price buffer (e.g., 30000000 wei / 0.03 gwei) to prevent gas estimation race conditions during multi-contract deployments. The --legacy flag should probably only be used for localhost/Anvil or explicitly for networks that don't support EIP-1559, rather than being the default for all non-localhost deployments.

[technophile-04]

Thanks for bringing this up! It will be removed in #1197 🙌