Block re-computation for validators on L2

Hi folks, I’m getting to know about the tech stack of Movement, especially the postconfirmation mechanism. I’ve read a Movement’s blog saying that “To incentivize validators to do some actual verification, we can ask them to provide a proof that they have re-computed the new block (if no ZKP exists yet, this is the only way to check the correctness of a block).”, but then in the next paragraph, it said “…Validators can broadcast a positive attestation together with a ZKP…” My question is, how do validators on Movement L2 actually re-compute the new block? Do they use ZKP? If so, how can it be faster than the ZK mechanism implemented by the ZK rollup?

Here’s the blog I’m talking about: Exploring Postconfirmations to Improve L2 UX

Any explanation about this is much appreciated! Thanks!

1 Like