Component
Forge
Describe the feature you would like
When deploying a script that interacts with an external factory, foundry does not verify the created contracts.
E.g. here we call a proxy factory that creates on oz proxy - foundry did not verify the proxy(it's verified because i did it manually).
By my understanding, the reason for that is that foundry does not have the local bytecode of that contract in that case (given the factory was deployed from another repo potentially with other compiler settings).
Now, as i understand foundry scripts, for tracing all touched addresses are downloaded from explorers already - so in fact found should have the code, even if it's not part of the repo. While this is a bit of an edge case, over the last couple years we faced this shortcoming quite a few times.
Additional context
#4522 probably slightly related, as i guess one would need to be able to compile different contracts with potentially different settings without pruning existing ones.
Component
Forge
Describe the feature you would like
When deploying a script that interacts with an external factory, foundry does not verify the created contracts.
E.g. here we call a proxy factory that creates on oz proxy - foundry did not verify the proxy(it's verified because i did it manually).
By my understanding, the reason for that is that foundry does not have the local bytecode of that contract in that case (given the factory was deployed from another repo potentially with other compiler settings).
Now, as i understand foundry scripts, for tracing all touched addresses are downloaded from explorers already - so in fact found should have the code, even if it's not part of the repo. While this is a bit of an edge case, over the last couple years we faced this shortcoming quite a few times.
Additional context
#4522 probably slightly related, as i guess one would need to be able to compile different contracts with potentially different settings without pruning existing ones.