Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: implement the update logic for data commitment creation (#1686)
<!-- Please read and fill out this form before submitting your PR. Please make sure you have reviewed our contributors guide before submitting your first PR. --> ## Overview Implements the update logic for data commitment creation. Because, this is changing the state between the two versions and if a validator starts syncing from genesis (even using the new version), it will end up failing. Thus, we need to implement the same mechanism we did for the `threshold` so that new binaries are able to sync from genesis. More information in: #1676 (comment) Note: this will result in missing a block between the updates. But it's okey for BSR. However, we have an issue to update the data commitment creation to support changes in the window: #1685 <!-- Please provide an explanation of the PR, including the appropriate context, background, goal, and rationale. If there is an issue with this information, please provide a tl;dr and link the issue. --> ## Checklist <!-- Please complete the checklist to ensure that the PR is ready to be reviewed. IMPORTANT: PRs should be left in Draft until the below checklist is completed. --> - [ ] New and updated code has appropriate documentation - [ ] New and updated code has new and/or updated testing - [ ] Required CI checks are passing - [ ] Visual proof for any user facing features like CLI or documentation updates - [ ] Linked issues closed with keywords
- Loading branch information