evalir
evalir
@strumswell this actually should've been fixed recently—could you post a repro of what's happening?
@strumswell ack—will close this for now. If you do see it's not an issue on your side pls let us know and we'll reopen & investigate!
> foundry did not utilize all the threads of my CPU to perform the fuzzing interesting cc optimizooor @DaniPopes
Closing as stale—please let us know if it isn't fixed and we'll reopen
@trojanMcAfee `forge` will not compile faster as it does not add any overhead. All the time you're seeing is exclusively the `solc` binary compiling all contracts.
needs a cleanup before another review, mainly regarding fee mgmt—will handle later today.
yep https://github.com/alloy-rs/alloy/pull/239 is blocking as an encoding fix—we need to adjust the encoding strategy on alloy a bit to accomodate the fact that 4844 has two encodings: trie encoding (with...
Indeed, as @onbjerg said make sure you're using an archive endpoint—else you won't have the required data.
yep @onbjerg could be this. Will look into it
seems the repro is missing the `./setup.ts` file