On Fusaka, CALL ModExp at 0x05 with base, exponent, and modulus each 32 bytes of 0x02 — how much gas does the CALL use?
Look forgasUsed for the CALL to 0x05
Agent will likely call run_bytecode
EIP-7883ModExp Gas Cost Increase
RunnableLive on the hosted MCP — free on Fusaka (mainnet today) and Amsterdam.
Website twin: exploration on feelyourprotocol.org
How are ModExp gas costs changing with Fusaka?
EIP-7883 recalibrates the ModExp precompile (0x05) gas formula so cost better reflects real work — especially for larger exponents. EIP-7823 (same fork) tightens input bounds. The new formula is live on Fusaka (current mainnet EL).
The MCP server runs caller-supplied bytecode that invokes ModExp (typically a CALL to 0x05 with the standard ABI: three 32-byte length headers plus B, E, M bodies). Run on Fusaka to price today’s mainnet; compare Pectra vs Fusaka to see the repricing — or sweep input sizes on Fusaka alone to understand the curve.
The hosted MCP is live (Connect). Copy a prompt into your agent — each quote is self-contained.
Job
On Fusaka, CALL ModExp at 0x05 with base, exponent, and modulus each 32 bytes of 0x02 — how much gas does the CALL use?
Look forgasUsed for the CALL to 0x05
Agent will likely call run_bytecode
Lesson
On Pectra then Fusaka, run the same 32-byte ModExp CALL (base, exponent, and modulus each 32 bytes of 0x02) — how much did gas increase?
Look forthe same payload costing more on Fusaka
Agent will likely call run_bytecode
Check
On Fusaka, CALL ModExp at 0x05 with a 4096-byte modulus — does EIP-7823 reject the input?
Agent will likely call run_bytecode
Confirm the 7883 catalog entry; read the ModExp input layout.
Execute CALL bytecode on fusaka (or pectra then fusaka for a compare).
Fork caveat
EIP-7883 introduced at Fusaka (current mainnet). For before/after, run the same bytecode on pectra (predecessor), then fusaka, and diff gasUsed. The probe derives this pair from eipIntroductions. A Fusaka-only run is enough when you only need today’s ModExp cost.