Are block.timestamp and block.number still problematic under Proof of Stake?

Magicians Primordial Soup
1

As stated in the SWC116 (SWC-116 - Smart Contract Weakness Classification (SWC)) using block.timestamp and block.number in Smart Contracts under Proof of Work was problematic.

  1. Block.timestamp could be influenced by the miners up to 15s
  2. Using block.number as proxy for time is inaccurate since the time between block depended on the difficulty i.e. was not fixed.

Do those two issues still exists under Proof of Stake? If not, are there any other/new concerns about using block values as a proxy for time?

2

The issue is still there, and as long as Miner Extractable Value (MEV) attacks are possible, will continue to be an issue. Just don’t use block.timestamp for anything critical.