rakita
Closed in https://github.com/bluealloy/revm/pull/1386
> @rakita are you familiar with the previous changes for bsc for revm v19? I am not familiar, do you have doc/link/repo or something that I look at? cc @loocapro
Agreeing with @DaniPopes here, better place for this is in[revm-inspectors](https://github.com/paradigmxyz/revm-inspectors/)
This is probably not going to happen with whole `Evm` what i would recommend is to use and send `Context` while rebuilding `Handler` when needed.
Idea is to have a place to save it after you execute transaction. All output of transaction execution (Including log) is returned from `transact`
BALs metrics specs proposal: https://discord.com/channels/595666850260713488/1364000387195076608/1425488151451013150 Or in PR: https://github.com/ethereum/execution-metrics/issues/5
One of request: `I wanted to bring up debugging in this session. It would be very useful if we had the full bal in debug logs from all clients when...
Did you build it in release? We are checking with valgrind for perf degredations: https://github.com/bluealloy/revm/pull/1467#issuecomment-2140860061
@holiman did you have time to test this?
@holiman is this still the case? I think it was a problem with bytecode analysis that was not cached