forked from 0xPolygonHermez/zkevm-node
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Backport v0.0.1-RC4 & RC5 to develop (0xPolygonHermez#1483)
* update poe sc to security mechanisms version (0xPolygonHermez#1467) * update poe sc to security mechanisms version * updated names, fix tests and remove ger timestamp and other fixes * fix rlp tool * fix linter * new genesis + fix * new smc * Update executor errors * Update executor errors * Update executor errors * Update executor errors * new l2 contract names * sequencewr unit test commented * fix test Co-authored-by: Alonso <[email protected]> Co-authored-by: ToniRamirezM <[email protected]> * Fix/1472 verify batches timeout (0xPolygonHermez#1473) Closes 0xPolygonHermez#1472 ### What does this PR do? During testing we faced an issue of two consecutive verified batches on L1 without respecting the time spacing. The problem was that we were relying on the timer to check if we can start generating a new final proof. That timer is only reset after the final proof is sent to L1. This means that there's a time window between the generation of a final proof and its verification in which a new proof eligible to be final can be generated and immediately trigger another final proof generation. The fix introduced here is to have a `verifyingProof` flag that gets checked when the final proof generation process begins and released only when the verification phase ends (or in case of errors). Co-authored-by: Thiago Coimbra Lemos <[email protected]> Co-authored-by: Alonso <[email protected]> Co-authored-by: ToniRamirezM <[email protected]>
- Loading branch information
1 parent
ba9a046
commit 1570ef0
Showing
49 changed files
with
2,895 additions
and
1,129 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.