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
The collateral that is deposited into the fee bridge needs to decide which instance it honours in case of an upgrade.
For example, it is following along, an upgrade would mean that there is no collateral to transfer funds to the sequencer to cover the fees paid in the blocks. If this causes a failure to execute that is essentially bricking the old instance, so it should be possible to address separately.
For example, one might be able to check a value in the original bridge, if it is no longer the rollup itself, it might need to alter the fee bridge.
A separate thing to consider, if this is using multiple different bridges, it will be different types or messages that is received on the L2 side of things. Meaning that the L2 contract might not allow inserting directly unless we can let it learn that things have changed, so we might need to look into either having a contract where assets might be deposited into multiple different rollups, or passing along with the constants the address of the "current" fee bridge.
The text was updated successfully, but these errors were encountered:
The collateral that is deposited into the fee bridge needs to decide which instance it honours in case of an upgrade.
For example, it is following along, an upgrade would mean that there is no collateral to transfer funds to the sequencer to cover the fees paid in the blocks. If this causes a failure to execute that is essentially bricking the old instance, so it should be possible to address separately.
For example, one might be able to check a value in the original bridge, if it is no longer the rollup itself, it might need to alter the fee bridge.
A separate thing to consider, if this is using multiple different bridges, it will be different types or messages that is received on the L2 side of things. Meaning that the L2 contract might not allow inserting directly unless we can let it learn that things have changed, so we might need to look into either having a contract where assets might be deposited into multiple different rollups, or passing along with the constants the address of the "current" fee bridge.
The text was updated successfully, but these errors were encountered: