Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

investigate if forking should use the chainId of the original chain #628

Closed
davidmurdoch opened this issue Sep 11, 2020 · 0 comments · Fixed by #1537
Closed

investigate if forking should use the chainId of the original chain #628

davidmurdoch opened this issue Sep 11, 2020 · 0 comments · Fixed by #1537
Assignees
@davidmurdoch
Labels
forking
Milestone
7.0.0

Comments

@davidmurdoch
Copy link
Member

Perhaps it should use the original chainId only for eth_call/debug_traceTransaction calls before the fork block number, while still using the configured/default id for RPCs after the fork block number.

/cc @haltman-at, @gnidan
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@davidmurdoch davidmurdoch

Labels
forking
Projects
None yet
Milestone
7.0.0
Development

Successfully merging a pull request may close this issue.

fix: make forking chainId aware trufflesuite/ganache
1 participant
@davidmurdoch