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
Right now we use the parameter SafeMaxRLPBytesPerChannel throughout the op-node channel building & op-batcher. We should remove this constant and use the chain spec instead. The specific timestamp to use is the timestamp of the L1 origin of the newest L2 block in the channel. Technically in derivation the new limit will be applied for channels that get processed after the L1 origin of the CB is past the activation time.
The text was updated successfully, but these errors were encountered:
Right now we use the parameter
SafeMaxRLPBytesPerChannel
throughout the op-node channel building & op-batcher. We should remove this constant and use the chain spec instead. The specific timestamp to use is the timestamp of the L1 origin of the newest L2 block in the channel. Technically in derivation the new limit will be applied for channels that get processed after the L1 origin of the CB is past the activation time.The text was updated successfully, but these errors were encountered: