oasysgames / oasys-opstack

Layer 2, named Verse, built on top of the Oasys gaming blockchain utilizes Opstack.
MIT License
0 stars 1 forks source link

Investigate what happen when op-proposer stop more than 256 L1 blocks #122

Closed tak1827 closed 7 months ago

tak1827 commented 7 months ago

During the build of the OpenStack version of Sand Verse, I discovered that L2 state submission will fail if the operation-proposer attempts to propose a state older than 256 L1 blocks. The critical detail here is that the L2 state root submission includes the L1 block hash, which is verified by the L1 contract. However, it appears that the L1 contract cannot access block information older than 256 blocks, as indicated by the comments here:

https://github.com/oasysgames/oasys-opstack/blob/develop/packages/contracts-bedrock/src/L1/L2OutputOracle.sol#L198-L206

Could you please clarify the threshold for the blocks? Is it actually 256 blocks, or does it even older?