Arsenii Kulikov
Arsenii Kulikov
Such error usually means that you have to wait a bit while Etherscan is indexing your contract. If that happens, running script with `--resume` flag after some time should help
does the deployed contract has any code? can you share the deployment transaction?
right, so this is basically a CREATE transaction with empty data, this contract can't be verified. Can you reproduce this reliably? Does script artifacts look correct?
@notchuks are you on latest nightly? thinking this might have been fixed by https://github.com/foundry-rs/foundry/pull/8532
do you mind sharing script artifacts from `broadcast/` folder? also are you using a public RPC you could share?
could you please share an RPC that's being used?
After https://github.com/foundry-rs/compilers/pull/140 cache now keeps a mapping `source -> build` where each build keeps a list of source ids, which match those appearing in sourcemaps
`Default` is implemented for `MultiCompiler` with `svm-solc` feature, most of our doctests assume it's enabled. perhaps we should remove this feature at this point? I believe it is not that...
Looks like this is only happening on older forge-std versions forge-std 1.2.0 does `abi.decode(vm.parseJson(json, key), (bytes));` instead of `vm.parseJsonBytes(json, key);`, so automatic coercion to address might cause errors during abi...
I think this should already be possible by using `vm.startStateDiffRecording` and `vm.stopAndReturnStateDiff` by checking that reverted call to the given address is present in the returned array Though it's not...