Skip to content

Conversation

@Artemka374
Copy link
Contributor

@Artemka374 Artemka374 commented Sep 9, 2025

What ❔

Verify protocol version and proving mode alignment when receiving a proof.

Why ❔

  • Check whether proof has the same protocol version as the batch it was generated for
  • When getting batch to send validation result for - check whether the batch has proving_mode = proving_network. It prevents sending validation result for the batches that were generated by prover cluster.

Is this a breaking change?

  • Yes
  • No

Operational changes

Checklist

  • PR title corresponds to the body of PR (we generate changelog entries from PRs).
  • Tests for the changes have been added / updated.
  • Documentation comments have been added / updated.
  • Code has been formatted via zkstack dev fmt and zkstack dev lint.

EmilLuta
EmilLuta previously approved these changes Sep 9, 2025
@Artemka374 Artemka374 changed the title fix(eth-proof-manager): verify protocol version alignment fix(eth-proof-manager): verify protocol version and proving mode alignment Sep 16, 2025
Copy link
Contributor

@EmilLuta EmilLuta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please add a description of what's the work going on in here? I don't fully follow along the SQL and it will be very useful for other folks who look through the PRs.

@Artemka374 Artemka374 added this pull request to the merge queue Sep 16, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Sep 16, 2025
@Artemka374 Artemka374 added this pull request to the merge queue Sep 16, 2025
Merged via the queue into main with commit 99e0423 Sep 16, 2025
41 checks passed
@Artemka374 Artemka374 deleted the afo/verify-protocol-version-alignment branch September 16, 2025 16:17
github-merge-queue bot pushed a commit that referenced this pull request Sep 18, 2025
🤖 I have created a release *beep* *boop*
---


##
[29.3.0](core-v29.2.0...core-v29.3.0)
(2025-09-18)


### Features

* **en:** Check commitment allonside with roothashes
([#4492](#4492))
([6e8f526](6e8f526))
* **en:** Improved en commitment generation error handling
([#4483](#4483))
([1bb82d6](1bb82d6))


### Bug Fixes

* **en:** Add check for commitment in diverged batch
([#4493](#4493))
([e693fd0](e693fd0))
* **en:** allow to disable sanity checks for commitment generation
([#4487](#4487))
([7692f31](7692f31))
* **EN:** properly set chain_id for old batch transactions
([#4488](#4488))
([634b6dd](634b6dd))
* **eth-proof-manager:** don't fail component if proof was incorrect
([#4444](#4444))
([daa1161](daa1161))
* **eth-proof-manager:** verify protocol version and proving mode
alignment
([#4473](#4473))
([99e0423](99e0423))
* **eth-sender:** Fix selector for old batches
([#4489](#4489))
([bb42dcf](bb42dcf))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: zksync-era-bot <[email protected]>
Deniallugo pushed a commit that referenced this pull request Oct 22, 2025
…nment (#4473)

## What ❔

Verify protocol version and proving mode alignment when receiving a
proof.

## Why ❔

* Check whether proof has the same protocol version as the batch it was
generated for
* When getting batch to send validation result for - check whether the
batch has proving_mode = proving_network. It prevents sending validation
result for the batches that were generated by prover cluster.

## Is this a breaking change?
- [ ] Yes
- [ ] No

## Operational changes
<!-- Any config changes? Any new flags? Any changes to any scripts? -->
<!-- Please add anything that non-Matter Labs entities running their own
ZK Chain may need to know -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zkstack dev fmt` and `zkstack dev
lint`.
Deniallugo pushed a commit that referenced this pull request Oct 22, 2025
🤖 I have created a release *beep* *boop*
---


##
[29.3.0](core-v29.2.0...core-v29.3.0)
(2025-09-18)


### Features

* **en:** Check commitment allonside with roothashes
([#4492](#4492))
([6e8f526](6e8f526))
* **en:** Improved en commitment generation error handling
([#4483](#4483))
([1bb82d6](1bb82d6))


### Bug Fixes

* **en:** Add check for commitment in diverged batch
([#4493](#4493))
([e693fd0](e693fd0))
* **en:** allow to disable sanity checks for commitment generation
([#4487](#4487))
([7692f31](7692f31))
* **EN:** properly set chain_id for old batch transactions
([#4488](#4488))
([634b6dd](634b6dd))
* **eth-proof-manager:** don't fail component if proof was incorrect
([#4444](#4444))
([daa1161](daa1161))
* **eth-proof-manager:** verify protocol version and proving mode
alignment
([#4473](#4473))
([99e0423](99e0423))
* **eth-sender:** Fix selector for old batches
([#4489](#4489))
([bb42dcf](bb42dcf))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: zksync-era-bot <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants