foundry-poc-mainnet-fork

To generate a Foundry PoC, provide a vulnerability report, chain details, fork target, and deployed contract addresses to reproduce the exploit end-to-end against real EVM contracts on a mainnet fork. This creates a submission-ready test without mocks.

Reproducing a smart contract exploit using real protocol state involves creating Foundry tests that interact with real deployed EVM contracts on a forked network, executing the vulnerability from trigger action to final impact to assert causal-chain execution.

Yes, verified contract addresses are required to run a mainnet fork PoC in Foundry. You also need chain details and fork configuration to accurately reproduce vulnerability interactions against real deployed contracts without artificial protocol state changes.

Yes, security findings are classified as frozen historical, forward-looking, or both before building the reproduction path. This classification step ensures the mainnet fork PoC accurately targets the correct temporal context of the vulnerability.

Yes, this approach works for bug bounty submissions requiring mainnet state assertions. It generates end-to-end Foundry proof-of-concept tests that validate vulnerabilities and assert impact using real protocol interactions on forked EVM networks.

Mocks are not used because they introduce artificial protocol state changes. Instead, mainnet fork reproductions interact with real deployed EVM contracts, ensuring the PoC reflects actual protocol interactions and causal-chain execution for accurate vulnerability validation.