Great job! I don't have much context on this, but I have a few questions:

1. Should gas be burned before expensive operations?

2. Should introduced code be thread-safe?

Feel free to merge this PR and address these questions later.

Great job! I don't have much context on this, but I have a few questions:

1. Should gas be burned before expensive operations?

2. Should introduced code be thread-safe?

Feel free to merge this PR and address these questions later.

1. Yes gas is burned inside the precompile methods. ArbInfoParser.cs actually decodes the data into the expected types and pass the decoded data as parameters when calling the actual precompile implementation ArbInfo.cs. In that precompile, gas is burned in each precompile method.
2. That precompile in particular is just read-only, just getting data. But maybe for future precompiles that update the state, we should use thread safe code ? 🤔 @damian-orzechowski

2. That precompile in particular is just read-only, just getting data. But maybe for future precompiles that update the state, we should use thread safe code ? 🤔 @damian-orzechowski

Currently I think there is not need for that as there is only a single transaction / EVM processing thread. Unless these precompiles are to be executed elsewhere with possible multithreading, then I don't think it's a requirement (for now).