Skip to content
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(protocol): fix guardian prover bug #15528

Merged
merged 4 commits into from
Jan 19, 2024
Merged

fix(protocol): fix guardian prover bug #15528

merged 4 commits into from
Jan 19, 2024

Conversation

adaki2004
Copy link
Contributor

The blelow code section.If transition is correct but contested AND guardian came with the (same) correct proof, this check would not allow it to execute properly.

            // When contestBond is zero for the current tier, it signifies
            // it's the top tier. In this case, it can overwrite existing
            // transitions without contestation.
            if (tran.blockHash == ts.blockHash && tran.signalRoot == ts.signalRoot) {
                revert L1_ALREADY_PROVED();
            }

Copy link

vercel bot commented Jan 19, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
bridge-ui-v2-a6 ✅ Ready (Inspect) Visit Preview Jan 19, 2024 9:01am

@dantaik dantaik changed the title fix(protocol): Stuck guardian fix(protocol): fixed guardian prover bug Jan 19, 2024
@dantaik dantaik changed the title fix(protocol): fixed guardian prover bug fix(protocol): fix guardian prover bug Jan 19, 2024
@davidtaikocha davidtaikocha merged commit ff8690e into alpha-6 Jan 19, 2024
16 checks passed
@davidtaikocha davidtaikocha deleted the stuck_guardian branch January 19, 2024 09:10
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.

4 participants