You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A general pattern I think all rollups should land on as we move to a multi rollup world is the ability to get the rollup config on chain. This way you can bootstrap the arbitrum sdk with only the rpc url even if the rollup config hasn't been added to this sdk yet.
e.g.
constl2Network=awaitgetL2NetworkFromRpc(l2RpcUrl/** <-- rpc url of target Arbitrum chain */)
This allows us to more easily make tooling work for all chains without needing to specify the config within the library first or needing to tediously craft your own config
The text was updated successfully, but these errors were encountered:
The way we are thinking about this at OP is sticking the config at a predeployed address on l2. That way any config can bet fetched from a known address
A general pattern I think all rollups should land on as we move to a multi rollup world is the ability to get the rollup config on chain. This way you can bootstrap the arbitrum sdk with only the rpc url even if the rollup config hasn't been added to this sdk yet.
e.g.
This allows us to more easily make tooling work for all chains without needing to specify the config within the library first or needing to tediously craft your own config
The text was updated successfully, but these errors were encountered: