[mainnet]: Increase Gas Limit to 31.25Mgas/s

[jjtny1]

Increase our gas limit to 31.25Mgas/s

[cb-heimdall]

✅ Heimdall Review Status

Requirement	Status	More Info
Reviews	✅ 2/2	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 2 if repo is sensitive 0 From .codeflow.yml 2 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 2 2 1 if commit is unverified 0 Sum 2

[jackchuma]

If we aren't using the signer tool for the rollback, please update the expected state diff below

[leopoldjoy]

I had understood that we are using the Signer Tool for this task, is that right @jjtny1? If so, the README can look something like this (except that the Signer Tool can now be used for the Rollback direction also).

[jjtny1]

It's tricky to use the validation tool for the rollback as well because it requires switching the TO/FROM environment variables. Im not sure there is an easy way to tell the signing tool "switch the variables" without manually switching them OR modifying the SetGasLimit script in base-contracts to accept a TO_ROLLBACK/FROM_ROLLBACK env variables

[leopoldjoy]

Yes, this is possible now in a straightforward way with the latest version of the Signer Tool. Here's a working example of it with the Signer Tool: #491

[jjtny1]

Got it, going forward we can use this

[leopoldjoy]

We can generate the validation file for the rollback case too as I mentioned here.

[leopoldjoy]

There should be a second (generated) validations file for the rollback.

[leopoldjoy]

Why do we need both the OLD / NEW and the FROM / TO format here?

[jjtny1]

This was because the signer tool was being used for the upgrade and the rollback was the normal way. For some reason the template sets FROM/TO to OLD/NEW

[leopoldjoy]

I had understood that we are using the Signer Tool for this task, is that right @jjtny1? If so, the README can look something like this (except that the Signer Tool can now be used for the Rollback direction also).