Jin Suk Park

### Problem Current suave-geth allows only one rpc backend and the `buildEthBlock` precompile focuses on L1(Ethereum) blocks only. In an attempt to expand suave's capability to talk with multiple chains...

I thought it should be the kettle operator running the rpc to keep everything under TEE. So I assumed setting arbitrary urls in contract should be forbidden. Otherwise someone might...

in your scenario @ferranbt, does the kettle operator set the whitelisted url endpoints that suapps can talk with? I am mildly concerned about the security of user setting arbitrary raw...

@dmarzzz do you mean the builder sessions? I think that can be easily managed in the next PR.

@tynes that is really nice set of vm funcs i didn't know. thanks for your advice

@tynes I am seeing the implementation of L1 contracts being equal across rollups, and their proxies are different. Is this intented?

@tynes I am currently debugging why op-batcher is not working for first rollup. It exits immediately after printing execution reverted, which seems to be an issue related to some underlying...