Improved scanner mode #483
Description
Scanner mode 1 only checks whether the local blob commitments match the on-chain commitments. It’s lightweight but cannot verify the actual data. Scanner mode 2 verifies that the actual blob data matches the on-chain commitments, but it is more resource-intensive.
Would it make sense to introduce a mode 3 that combines both approaches—for example, running mode 1 frequently and mode 2 at a longer interval, such as once every three days?