chore: bumping constants

[benesjan]

I needed to modify some constants due to changes in partial notes and I decided to do this in a separate PR from the one up the stack to make it all easier to review.

[benesjan]

• refactor: passing partial note logs through transient storage #9356
• chore: bumping constants #9431 👈
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @benesjan and the rest of your teammates on Graphite

[dbanks12]

I'd hesitate to actually merge a bump to 12 million gas until we confirm

1. where this cost blowup is coming from
2. whether we are anywhere near overflowing the AVM trace
3. and whether we suspect that upcoming optimizations (like to sha256) will bring this cost down

otherwise we might be screwing ourselves

[github-actions]

Changes to circuit sizes

Generated at commit: c0e9a595ccade91e7a1251ce77a00a610c69d161, compared to commit: 7766c8e714185d6e8b9fa392d7f371fb30da8f1a

🧾 Summary (100% most significant diffs)

Program	ACIR opcodes (+/-)	%	Circuit size (+/-)	%
public_kernel_inner	+78,400 ❌	+29.64%	+160,584 ❌	+31.55%

---

Full diff report 👇

Program	ACIR opcodes (+/-)	%	Circuit size (+/-)	%
public_kernel_inner	342,892 (+78,400)	+29.64%	669,595 (+160,584)	+31.55%

[dbanks12]

Approving since there are also external users/devs running into the gas limit. We can revisit lowering this once

1. the sha256 blowup is reduced
2. we have a better way to profile AVM execution
3. we have a better idea of what gas limit will safely prevent AVM trace overflow (or we choose some other way to prevent AVM trace overflow)