Will this RPC debug_executionWitness support Prague hardfork?

[felicityin]

Will this RPC debug_executionWitness support Prague hardfork?

curl -X POST https://reth-ethereum.ithaca.xyz/rpc \
  -H "Content-Type: application/json" \
  -H "Accept-Encoding: gzip" \
  -d '{
    "jsonrpc": "2.0",
    "method": "debug_executionWitness",
    "params": ["latest"],
    "id": 1
  }' \
  -o response.gz

Or does it support ​​pulling​​ the information of the account ​​'0xfffffffffffffffffffffffffffffffffffffffe'​​? This is a system contract account used by the Prague hardfork.

[mattsse]

The system account is not touched during the syscalls, per spec it is only set as the caller address

hence it is not touched I believe it's missing from the state output, so perhaps not relevant here?

or where would this be required?

[mattsse]

which alloy-evm version are you using?

[mattsse]

nvm I can just check https://github.com/felicityin/reth-processor

[mattsse]

oh I see

this might be a cross version drift, because I believe the evm version you're using would load the system addr but the one in latest reth doesnt

is it feasible to update the reth and alloy deps?

[mattsse]

another thing, could you try manually inserting keccak(0xfffffffffffffffffffffffffffffffffffffffe)

into the accountset and check if that bypasses it

[felicityin]

The alloy-evm version is 0.12.3.

Yes, I can update the reth and alloy deps.

Thanks, I will try manually inserting keccak(0xfffffffffffffffffffffffffffffffffffffffe) into the accountset.

[mattsse]

I see, let me try to hotfix this and perhaps you can verify

[felicityin]

Thanks!

[felicityin]

@mattsse I have fixed this issue: felicityin/reth-processor@b8a6088