You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After completion of state diff check and proof of equivalence, we should have stabilized the public inputs (PIs) necessary to verify an L2 block execution proof (no more inputs should be needed for now).
The current implementation of verify() takes 3 different fields of the public inputs for each proving backend / zkvm. After stable PIs, all PI data will be available as fields of the block commitment, so no PI argument should be necessary in the verify() function (we can retrieve PIs from the committed block).
After completion of state diff check and proof of equivalence, we should have stabilized the public inputs (PIs) necessary to verify an L2 block execution proof (no more inputs should be needed for now).
The current implementation of verify() takes 3 different fields of the public inputs for each proving backend / zkvm. After stable PIs, all PI data will be available as fields of the block commitment, so no PI argument should be necessary in the verify() function (we can retrieve PIs from the committed block).
The function will only take as arguments: