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.

Sign up for GitHub

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

Jump to bottom

Consensus: 2nd tx should not finish before 1st tx #661

Open

kstroobants opened this issue Dec 3, 2024 · 0 comments · May be fixed by #759

Assignees

Contributor

kstroobants commented Dec 3, 2024 •

edited

Loading

For failed appeals close to the end of the finality window

tx1 accepted and tx2 accepted
tx1 processing appeal
tx2 should not be finalized

Quick test in studio:

Set finality window on 30s
Send tx1 and tx to deployed contract
Wait until both are in accepted state
Appeal tx1
Set finality window to 3s
Check if tx2 is finalized after tx1

kstroobants self-assigned this

kstroobants linked a pull request

that will close this issue

fix: consensus 2nd tx should not finish before 1st tx #759

Open

4 tasks

kstroobants linked a pull request

that will close this issue

fix: consensus 2nd tx should not finish before 1st tx #759

Open

4 tasks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment