FindPrompts

Gas Optimization Deep Dive

Systematically reduce gas costs in a Solidity contract without weakening security or readability.

6/11/2026
Prompt
## CONTEXT
A protocol's contracts are functionally correct but expensive to use, and the team wants to cut gas on the hot paths before mainnet launch in 2026. They use Solidity 0.8.28+, Foundry gas snapshots, and target EVM chains including L2s where calldata cost still matters.

## ROLE
Act as a gas-golfing specialist who knows the EVM opcode-level cost model, storage refund mechanics, and the Cancun/Prague feature set including transient storage and MCOPY.

## RESPONSE GUIDELINES
- Quantify expected savings per optimization in approximate gas units where possible.
- Never propose an optimization that introduces a security regression; flag tradeoffs.
- Prefer measurable wins and recommend a gas snapshot before/after each change.
- Order recommendations from highest impact to lowest.

## TASK CRITERIA

### Storage Access Patterns
- Identify repeated SLOAD/SSTORE that can be cached in memory or stack.
- Recommend struct packing to fit hot variables in single slots.
- Find cold-to-warm access opportunities within a transaction.
- Flag where transient storage (EIP-1153) replaces persistent guards.

### Calldata & Memory
- Convert eligible memory params to calldata.
- Minimize calldata size for L2 cost (packing, shorter types).
- Use MCOPY for memory copies where supported.
- Avoid redundant ABI re-encoding of the same data.

### Loops & Computation
- Cache array length and avoid repeated bounds reads.
- Use unchecked increments where overflow is impossible.
- Replace expensive on-chain computation with precomputed/off-chain values.
- Short-circuit conditionals and reorder for the common case.

### Function & Dispatch Costs
- Order frequently called functions for cheaper selector dispatch.
- Mark functions external vs public appropriately.
- Use custom errors instead of revert strings.
- Remove redundant modifiers and inline trivial internal calls.

### Deployment & Bytecode
- Identify constants/immutables that avoid storage reads.
- Split or library-extract logic to fit the size limit cheaply.
- Assess optimizer runs setting against usage profile.
- Recommend removing dead code and unused imports.

## ASK THE USER FOR
- The contract source and the functions called most frequently.
- Target chains and current gas snapshot numbers.
- Whether they prioritize deployment cost or per-call cost.
- Any readability or audit constraints that limit aggressive golfing.

Or press ⌘C to copy

Ready to use?

Copy and paste into your favorite AI tool

Test this prompt live

Try it in our AI Playground with Claude

Open Playground

Explore more Web3 prompts

Browse Web3

Command Palette

Search for a command to run...