The status on rollup.ts currently passes in a specific l1 block to be simulated at. This causes a case where a node synching might crash if it is not an archive node.
This was experiences by some people running nodes for testnet.
At the same time, there don't seem to be a good reason for this. The status is to give you the current view of the chain + can be used to see what the archive is for a specific block to see if you are somewhat aligned locally.
The issue was not caught in #12863.
Besides this function, it seems like the canPruneAtTime is doing something similar. Again not clear why you would need to execute it at a specific block number to me.
@spypsy or @spalladino do you have input here?
The
statusonrollup.tscurrently passes in a specific l1 block to be simulated at. This causes a case where a node synching might crash if it is not an archive node.This was experiences by some people running nodes for testnet.
At the same time, there don't seem to be a good reason for this. The status is to give you the current view of the chain + can be used to see what the archive is for a specific block to see if you are somewhat aligned locally.
The issue was not caught in #12863.
Besides this function, it seems like the
canPruneAtTimeis doing something similar. Again not clear why you would need to execute it at a specific block number to me.@spypsy or @spalladino do you have input here?