# Agent instructions

You are advising on UX and product design for **MONAD-OPCODE: Opcode Repricing**.
This document is the authoritative designer guide from EIPs for Designers.

- Treat **MUST NOT** items as hard constraints unless the user explicitly overrides.
- Use the **Vocabulary** section for UI copy; do not use avoided terms.
- Cite the canonical source URL when giving recommendations.
- Use the official specification only for protocol implementation detail, not as primary UX guidance.

---

# MONAD-OPCODE: Opcode Repricing

Source: https://www.eipsfordesigners.com/standards/MONAD-OPCODE
Agent brief: https://www.eipsfordesigners.com/standards/MONAD-OPCODE/agent.md
Machine-readable JSON: https://www.eipsfordesigners.com/api/standards/MONAD-OPCODE
Last reviewed: 2026-05-25
Last updated: 2026-05-25

| Field | Value |
| --- | --- |
| Status | Active |
| Chain | monad |
| Category | Infrastructure |
| Journey stages | Gas & Fees |
| Detailed guide | Yes |
| Official specification | https://docs.monad.xyz |

## UX Impact

Cold storage access costs ~4x more gas than Ethereum to reflect Monad's optimized compute vs. storage ratio. Design implications: gas estimates may differ from Ethereum for storage-heavy operations, show Monad-specific gas estimates (not Ethereum defaults), first-touch storage operations cost more. Design decisions: whether to surface repricing details in advanced gas settings or just show accurate Monad estimates; ensure gas estimation tools use Monad-specific pricing.

## Summary

Monad reprices EVM opcodes so cold storage reads and writes cost roughly four times more than on Ethereum, while compute stays relatively cheaper. Gas previews built for mainnet will under-estimate first-touch storage on Monad and surprise users at sign. Label estimates as Monad-specific and surface when a transaction's first storage operation will cost more.

## For Designers

- You can label estimates as Monad network in gas preview footers.
- Your advanced gas panel can note First-time storage costs more on Monad when relevant.
- You can validate estimation RPC uses Monad opcode table not mainnet fork defaults.

## Applicability

### When to Use

- Gas estimation on Monad deployments.
- Storage-heavy contract interactions.
- Advanced gas settings for power users.

### When to Avoid

- Ethereum-only flows.
- Flat fee sponsorship hiding gas entirely.
- Users never see gas breakdown.

## Problems It Solves

### Wrong gas previews on Monad

Impact: critical

Old way: Ethereum estimator on Monad txs

New way: Monad opcode table in estimator

### Surprise storage setup cost

Impact: high

Old way: Estimate low then sign higher

New way: First storage cost footnote

### User distrust after revert

Impact: medium

Old way: Generic failed

New way: Refresh estimate and explain storage premium

## MUST NOT (Anti-Patterns)

- **Ethereum gas defaults on Monad** (critical)
  - Why: Systematic wrong estimates
  - Instead: Monad-specific estimator always

- **No explanation when storage estimate spikes** (high)
  - Why: User thinks bug or scam
  - Instead: First-time storage cost footnote

- **Hiding network on estimate row** (medium)
  - Why: User assumes Ethereum pricing
  - Instead: Network: Monad label on fee row

## Design Decisions

### Show opcode repricing details?

Recommendation: Advanced only; total estimate default.

Rationale: Users need accurate total not lecture.

### Footnote cold storage on first write?

Recommendation: Yes when estimate spike detected.

Rationale: Explains one-time premium.

### Cross-chain estimate UI?

Recommendation: Separate Monad and Ethereum estimators — never mix.

Rationale: Mixed tables cause systematic wrong estimates.

## States to Design

### Normal estimate

Trigger: Standard tx.

User need: Trust fee.

Design response: Monad-labeled estimate row.

### High storage estimate

Trigger: Storage-heavy op detected.

User need: Understand spike.

Design response: Includes one-time storage setup cost note.

### Estimate loading

Trigger: Sim running.

User need: Wait signal.

Design response: Estimating on Monad spinner.

### Estimate failed

Trigger: Sim error.

User need: Not blind sign.

Design response: Cannot estimate — fix tx or retry.

### Estimate refreshed after revert

Trigger: Prior estimate wrong.

User need: Updated number.

Design response: New estimate shown before retry.

## Vocabulary

- Use "Estimated fee on Monad" instead of "Opcode repricing adjusted gas": Simple fee language.

- Use "One-time setup cost" instead of "Cold SSTORE premium": Plain storage hint.

- Use "Refresh estimate" instead of "Re-simulate with Monad schedule": User action language.

## UX Patterns

### Monad Gas Estimate Row

Chain-labeled accurate fee preview.

Components: NetworkLabel, EstimateAmount, RefreshButton

User flow:

- Compose tx
- Monad estimate loads
- User sees fee
- Sign accurate amount

Mockup registry key: `erc-4337/gas-abstraction` (React UI on the live standard page).

### Storage Premium Footnote

Explain cold storage spike on Monad.

Components: EstimateFootnote, StorageHint

User flow:

- Heavy storage tx
- Estimate high
- Footnote explains
- User accepts informed

Mockup registry key: `concept/typed-data` (React UI on the live standard page).

## What to Prototype First

### Monad gas estimate row

Every confirm shows chain-accurate fee.

Covers: Simple send, Storage-heavy call

- Network: Monad label
- Estimate amount
- Refresh estimate

### First storage operation hint

Cold storage premium surprises users.

Covers: First SSTORE-like op

- One-time setup cost note
- Lower follow-up txs footnote

### Advanced gas breakdown

Power users audit estimate components.

Covers: Expand advanced

- Opcode-weight hint
- Monad pricing source
- Compare disabled Ethereum default

### Wrong estimate error recovery

When estimate drifted at sign.

Covers: Estimate too low revert

- Estimate was wrong — refreshed
- Retry with updated estimate

## Mental Model

### Monad gas schedule

Different opcode prices than Ethereum.

### Cold storage premium

First touch storage costs more — like Ethereum cold access amplified.

### Compute vs storage ratio

Monad optimizes compute; storage relatively pricier.

### Estimate source

Must call Monad-aware estimator not Ethereum default.

### User visibility

Accurate total matters; opcode detail optional advanced.

## Seen in the Wild

- MetaMask: Network-specific gas estimation patterns. (https://metamask.io/)

- Blocknative: Gas estimation API chain awareness. (https://www.blocknative.com/)

- Monad docs: Opcode repricing documentation. (https://docs.monad.xyz/)

## On Monad

### Opcode pricing

Ethereum: Ethereum gas schedule baseline

Monad: Repriced opcodes — cold storage ~4x relative premium vs compute

Design implication: Never use Ethereum gas tables for Monad estimates.

### Storage-heavy txs

Ethereum: Storage cost familiar ratio

Monad: Storage relatively costlier — footnote first-touch ops

Design implication: Detect storage spikes and explain in UI.

### Overall fees

Ethereum: Higher absolute gas many ops

Monad: Lower fees overall but storage premium still matters

Design implication: Accurate relative estimate more than absolute warning.

## Related Standards

- MONAD-PARALLEL: Fast inclusion after sign — https://www.eipsfordesigners.com/standards/MONAD-PARALLEL/agent.md

- MONAD-7702: Delegation txs need Monad estimates too — https://www.eipsfordesigners.com/standards/MONAD-7702/agent.md

## Technical Notes

MONAD-OPCODE: wire Monad opcode pricing into all estimators; footnote cold storage on estimate spikes.

## Official specification (reference only)

https://docs.monad.xyz