Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(prover): Remove FriProtocolVersionId (#1510)
This is PR 2 of many to move us to safe Protocol Upgrades (phase 1). `FriProtocolVersionId` was introduced as a cludge to serve as communication between core (which was saved from L1 straight to DB) and prover (which was manually configured from env vars). Whilst in theory it's possible to have an upgrade on core side without affecting prover, I don't envision this happening any time soon. Right now we maintain 2 different protocol numbers that cause confusion. This PR unifies the protocol ids. Other relevant notes: - this is not exactly backwards compatible -- we'll need to deploy both core and prover at the same time, otherwise provers will go in crash loop. We can make it backwards compatible, but at our track record of deployments (and speed of deployments), I'm concerned we will slow everything down for no real reason. I see very small risks here - database tables in prover's end should be renamed to protocol_version as well (to be covered in next PR) - all our code base assumes the old prover's interface to hashes which is confusing and unnecessary. I propose we address those with following PR. The points there are (to be done on both databases and configs): - rename `recursion_scheduler_level_vk_hash` to `snark_wrapper_vk_hash`. This is what it represents today. I believe we can't change `recursion_scheduler_level_vk_hash` without changing `snark_wrapper_vk_hash`. - delete `recursion_circuits_set_vks_hash`; it's all 0.
- Loading branch information
Showing
12 changed files
with
42 additions
and
125 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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,3 @@ | ||
[proof_data_handler] | ||
http_port=3320 | ||
proof_generation_timeout_in_secs=18000 | ||
protocol_version_loading_mode="FromEnvVar" | ||
fri_protocol_version_id=2 |
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
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.