First Flight #17: Dussehra

Verifyblock.timestamp reliability on L2

Description:

• Instances ChoosingRam::increaseValuesOfParticipants,ChoosingRam::selectRamIfNotSelected and Dusserha::killRavana

Verifying the reliability of block.timestamp on Layer 2 (L2) solutions is crucial for ensuring the integrity and security of transactions. Unlike Layer 1 (L1), where timestamps are set by miners and are subject to some manipulation, L2 solutions often implement mechanisms to maintain accurate and tamper-proof timestamps. Understanding how timestamps are managed on L2 solutions is imperative for ensuring the correct functioning of time-dependent operations within smart contracts.

For detailed insights into how time is set in L2 solutions, it's recommended to refer to the documentation provided by the respective platforms:

• Arbitrum: Arbitrum's documentation provides insights into how block numbers and time are handled on its platform. Arbitrum Documentation

• zkSync: The documentation for zkSync offers explanations on various concepts within its ecosystem, including how blocks are managed. zkSync Documentation

Recommended Mitigation:

• Before deploying on a rollup, consider checking their documentation on timestamp and check if the time dependent functionality is is safe