jwasinger

Hi @mratsim, thanks for the feedback on this work-in-progress draft. I'm working on completing an initial version of the EIP along with a Geth implementation, EVMMAX support in Huff, and...

Superseded by https://github.com/ethereum/EIPs/pull/6601

This mostly encompasses the changes in https://github.com/ethereum/go-ethereum/pull/28640 . We will want to eventually break this out into separate more-digestible PRs after the PoC in this branch works.

I think witnesses/values for storage writes are getting omitted on your branch @holiman . I modified your test case to only include a single block ([here](https://github.com/jwasinger/go-ethereum/commit/e61b4389001f8a6821e3aeb35ed11b941c93e56a)). I get this output:...

Ahhh that would explain it.

In https://github.com/gballet/go-ethereum/pull/37, I'm fairly sure this is the case. The `AccessWitness` used is per-`TxContext` (which as the name implies, only exists for the lifetime of a transaction).

I'm not sure there's a good way around this. It is clear that we need the call to `pool.Sync` when calling `fcu` in simulator mode because we want the tests...

Spent the day looking into this and trying to come up with some solution that doesn't involve manually calling txpool `Sync` in calls to `fcu` for dev mode zero-period, and...

There is a problem with the logic (that is also present in master): We only call `Commit` once when responding to `newTxs`. This could potentially leave executable txs dangling if...

closing in favor of #30264