improve(NetworkUtils): add chainIsL1Function

[bmzig]

As we begin to introduce tryMulticall into the relayer, the MulticallerClient will need to be aware of whether it is calling a spoke pool or hub pool contract (to determine whether it can even call tryMulticall). One approach is to first check if the contract's chain ID we are calling is one which has a hub pool implementation. It would be ideal to introduce this code into the sdk, where there already exists a set of functions which performs similar checks with our other chain IDs.

[pxrl]

One approach is to first check if the contract's chain ID we are calling is one which has a hub pool implementation.

wdyt about just checking for the existence of tryMulticall in the contract interface? I think something like that is still needed (or alternatively a check to verify that the target address is a SpokePool), and in the case of mainnet we still need to distinguish between Hub and Spoke, so I'm not sure how knowing whether the chain is mainnet is helpful.

[bmzig]

One approach is to first check if the contract's chain ID we are calling is one which has a hub pool implementation.

wdyt about just checking for the existence of tryMulticall in the contract interface? I think something like that is still needed (or alternatively a check to verify that the target address is a SpokePool), and in the case of mainnet we still need to distinguish between Hub and Spoke, so I'm not sure how knowing whether the chain is mainnet is helpful.

The issue with this is that we get the contract interface from dist/typechain/factories/contracts in the contracts repo, so this will falsely claim that every spoke pool has tryMulticall (since the ABIs cached are of the most up-to-date contract). The other option is to fetch the deployed bytecode and look for tryMulticall function signature bytes in the code, but since this is asynchronous (and the context in which we want to check whether a contract has tryMulticall is synchronous), it would require some extra refactoring on the relayer + an RPC call (this also assumes that the bytes in tryMulticall's function selector do not appear anywhere else in the contract).

I am adding a function to determine if a contract is a hub pool or spoke pool, but this will be in across-protocol/relayer#1466.

[james-a-morris]

We should include the version bump before merging.

[bmzig]

We should include the version bump before merging.

I don't need this in now, so I'm actually going to just wait until this gets merged in, so that version bump will include this as well. #683