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
If we imagine that our integration code at some point ends up in upstream nitro it should be possible to upgrade to an arbos version that supports the integration without actually using it. So I think it would be more appropriate to turn on the espresso integration via a call to the setChainConfig pre-compile instead of enabling it directly when performing the ArbOS upgrade (as we do now).
The text was updated successfully, but these errors were encountered:
Currently we enable the espresso integration via the chain config
nitro-espresso-integration/arbos/arbosState/arbosstate.go
Lines 330 to 332 in 8df6661
If we imagine that our integration code at some point ends up in upstream nitro it should be possible to upgrade to an arbos version that supports the integration without actually using it. So I think it would be more appropriate to turn on the espresso integration via a call to the
setChainConfig
pre-compile instead of enabling it directly when performing the ArbOS upgrade (as we do now).The text was updated successfully, but these errors were encountered: