Skip to content

fix: config limit used for trigger collection, lead to potential underflow#9

Merged
0xgregthedev merged 1 commit intomainfrom
fix/deployment-gas-limit
Jun 10, 2025
Merged

fix: config limit used for trigger collection, lead to potential underflow#9
0xgregthedev merged 1 commit intomainfrom
fix/deployment-gas-limit

Conversation

@0xgregthedev
Copy link
Copy Markdown
Contributor

The higher deployment gas value is used for deployment transactions, but the triggers() execution used the config.assertion_gas_limit - deployment_gas. This resulted in an underflow when the gas in deployment exceeds the configured assertion gas limit.

This limits the total gas consumption in deployment and trigger recording to be the DEPLOYMENT_GAS_LIMIT

Copy link
Copy Markdown
Contributor

@fredo fredo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, nice catch.

A nice test would be to have a deployment + triggers which uses right under DEPLOYMENT_GAS_LIMIT, and another one which uses more and expects it to fail

@0xgregthedev 0xgregthedev merged commit 0b67a02 into main Jun 10, 2025
7 checks passed
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.

2 participants