-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor(dal): strong typing for TEE proof status #2733
Conversation
I'm not sure why the CI is erroring out on code I haven't even touched. 🤷♂️
@aon @popzxc @Deniallugo any idea? |
Sorry, it's an update of rust compiler i'll fix it, you could ignore |
I've shared some thoughts on the subject elsewhere. In short, I would love to see what do we gain from this change (considering cons mentioned there) besides having strong typing as a fact. |
@popzxc, PTAL. Re this: I reverted the changes related to adding the zksync-era/core/lib/dal/src/tee_proof_generation_dal.rs Lines 23 to 31 in 2ff41ad
just like we have zksync-era/core/lib/dal/src/proof_generation_dal.rs Lines 20 to 30 in 46a75d4
I also aligned with the |
@perekopskiy could you PTAL? |
nit: it's not chore but rather refactor |
What ❔
Introduce strong typing for the TEE proof generation status in the Rust code only (not in the database). This is a followup for:
This PR also aligns the status types with those implemented in
proof_generation_dal.rs
(specifically theunpicked
status introduced in #2258).Why ❔
Strong typing makes it easier to reason about the code and helps protect against subtle bugs.
Checklist
zk fmt
andzk lint
.