hard20 pts · first answer countslayer-2solidity

Using block.number for time on L2

A staking contract measures lock periods in block.number assuming 12-second blocks, and is deployed unchanged to Arbitrum and Base. What is the problem?

A.block.number is not available on L2sB.block.number always returns 0 on L2sC.Block numbers mean different things on each chain: on Arbitrum block.number returns an approximate L1 block number, and Base produces blocks every 2 seconds, so durations are wrong; use block.timestampD.L2 blocks are always exactly 12 seconds, so nothing changes

Discussion 0

Join free to post in the discussion.

Using block.number for time on L2

Discussion 0

Related questions