-
Notifications
You must be signed in to change notification settings - Fork 25
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
Wait for a minimum amount of time since parent assertion was created to post a new assertion #714
base: main
Are you sure you want to change the base?
Conversation
…to post a new assertion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lookin nice! thanks for putting this together
Would just fix up the default for the time since parent and then can merge |
Need to think about how it affects overflow assertions
Hi @ganeshvanahalli , is the e2e test flakey only on this branch? |
@rauljordan I'm not sure, seems like a bunch of merge commits to main are failing on build and test step, example commit d59df31 https://github.com/OffchainLabs/bold/actions/runs/12354512151/job/34476031390 |
Hi @eljobe PTAL when you are back before merge just to have your approval for overflow assertions |
Earlier if assertion manager fails to create an assertion, it'd wait an hour before trying again. This PR fixes this by allowing immediate retries but inside the assertion creation we enable waiting for a minimum amount of time (configurable) since the parent assertion was created.
Corresponding nitro PR- OffchainLabs/nitro#2825
Part of NIT-2961