Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Etherscan trace decoder #1015

Closed
onbjerg opened this issue Mar 22, 2022 · 0 comments · Fixed by #1190
Closed

Etherscan trace decoder #1015

onbjerg opened this issue Mar 22, 2022 · 0 comments · Fixed by #1190
Assignees
@onbjerg
Labels
A-tracing Area: tracing C-forge Command: forge Cmd-forge-test Command: forge test D-average Difficulty: average P-normal Priority: normal T-feature Type: feature

Comments

@onbjerg
Copy link
Member

onbjerg commented Mar 22, 2022

When running tests in forking mode, we should try to identify contracts using Etherscan.

Leftover stretch task from #918
@onbjerg onbjerg added T-feature Type: feature Cmd-forge-test Command: forge test C-forge Command: forge A-tracing Area: tracing P-normal Priority: normal D-average Difficulty: average labels Mar 22, 2022
@onbjerg onbjerg self-assigned this Mar 28, 2022
This was referenced Apr 4, 2022
Merged
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@onbjerg onbjerg

Labels
A-tracing Area: tracing C-forge Command: forge Cmd-forge-test Command: forge test D-average Difficulty: average P-normal Priority: normal T-feature Type: feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: identify addresses from etherscan when forking foundry-rs/foundry
1 participant
@onbjerg