Skip to content

Conversation

@cgewecke
Copy link
Member

#891

The existing logic for extendConfig tries to clone the user's config and apply it to the resolved HH config after updating gas values, accidentally overwriting some necessary default fields in the forking object, which looks like this:

 forking: {
    url: 'https://opt-mainnet.g.alchemy.com/v2/....',
    enabled: true,
    httpHeaders: {},
    blockNumber: 123190000
  },

This isn't necessary, the config object is already seeded with user's values when extendConfig executes.

@cgewecke cgewecke merged commit df1df12 into master Aug 29, 2024
@cgewecke cgewecke deleted the fix-viem-forking branch August 29, 2024 04:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants