-
Notifications
You must be signed in to change notification settings - Fork 9
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
fix: consensus 2nd tx should not finish before 1st tx #759
Open
kstroobants
wants to merge
35
commits into
main
Choose a base branch
from
661-consensus-2nd-tx-should-not-finish-before-1st-tx
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
fix: consensus 2nd tx should not finish before 1st tx #759
kstroobants
wants to merge
35
commits into
main
from
661-consensus-2nd-tx-should-not-finish-before-1st-tx
Conversation
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
…inalized rollup transaction
…op when appeal failed and succeeded
…ed state and add button also to modal
- Add N+2 validators, remove leader - Use latest data of transaction when in pending state and not the old one from the crawler - Write consensus data before setting status to have it updated in frontend when going to transaction info modal - Do not deploy contract when transaction was in the undetermined state
…eals-implement-sequential-appeals-fail
…8-appeals-undetermined-transactions
…sation of transaction
…undetermined-transactions
…nly check in appeal_window
…king on finalized state gave a small delay in showing when appeal failed and finality window was exceeded
Quality Gate failedFailed conditions |
@kstroobants please solve the conflicts |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #661
What
Why
Testing done
Decisions made
Checks
Reviewing tips
Try in the studio
User facing release notes
The transaction can only be finalized if the previous transaction is finalized.