acolytec3

I've done some more exploratory work on this front in this branch in this subdirectory that should be usable as a basis for executing the proof validation. https://github.com/ethereumjs/ethereumjs-monorepo/tree/verkle-experimentation/verkle

Further discussion on Discord confirms that the `rust-verkle-wasm` package does not yet support verkle proof verification and needs additional work to iron out inconsistencies between the rust and go implementations...

I guess it could be worth taking up at some point to decide if we need to add an overlay for fixed-width as it should be pretty feasiible. Native Bigints...

There's also the issue with not being able to use the `StateTestRunner` where specifying EIPS to be activated along with the fork like `London+3540+3670`. I have this working in PR...

only the part about running the `StateTestRunner` with specific EIPs specified. I haven't touched the points that @jochem-brouwer raised in the top of the issue.

Looks like browser tests are failing, specifically [this one](https://github.com/paulmillr/ethereumjs-wallet/blob/0168a241b98748bd1dcb9f1cf98c07d76d9d58f1/test/index.spec.ts#L387). @paulmillr any ideas? Aside from that, why are the tests skipped for `scrypt` with unencrypted wallets? Is that an invalid test...

On the browser tests, near as I can tell, the `mac` value being computed is different than the expected result. ``` + { version: 3, - { address: 'b14ab53e38da1c172f877dbc6d65e4a1b0474c3c', id:...

> On the browser tests, near as I can tell, the `mac` value being computed is different than the expected result. > ``` > > + { version: 3, >...

We've made sufficient progress working on hive tests that it feels like this can safely be closed.

Do we still need this? We fixed a lot of the merge tests but a number of them address really obscure edge cases that @g11tech and I spent a while...