Skip to content

Conversation

@Jds-23
Copy link

@Jds-23 Jds-23 commented Nov 24, 2025

Resolves #12644

Motivation

Solution

Removed the code that checks for a cache and builds from it in crates/verify/src/bytecode.rs.

Added test that validates recompilation on source change: Builds with correct source (creates cache), replaces source with different code, runs verify-bytecode which recompiles (not using stale cache) and detects bytecode mismatch.

I consulted Claude Code to understand the codebase, but the solution was fully authored manually by me.

PR Checklist

  • Added Tests
  • Added Documentation
  • Breaking changes

@Jds-23
Copy link
Author

Jds-23 commented Nov 24, 2025

I tried running:

make build
make pr

Many tests were failing before my change, most not related to my change. Is there a guide to run all testcases smoothly?

@grandizzy
Copy link
Collaborator

I tried running:

make build
make pr

Many tests were failing before my change, most not related to my change. Is there a guide to run all testcases smoothly?

@Jds-23 just kicked CI and all seems good, you probably experience issues locally due to etherscan and other providers rate limiting

Copy link
Collaborator

@grandizzy grandizzy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this makes sense, small nit re test. pending @zerosnacks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

feat: forge verify-bytecode should automatically recompile upon running

2 participants