EIPs for Designers

Protocol standards, decoded for designers.

Find how each Ethereum and Monad standard affects what users see, feel, and do. Search by ID, browse by problem, or follow the user journey.

Curated for UX impactCross-referenced with official specs

EIP-7702 · One-click batching

One decoded EIP, two disciplines

EIPs are technical by default. Designers get UX standards and patterns without pinging protocol engineering. Developers get the user-impact layer behind each protocol.

Designers

Finally understand EIP standards

Specs are technical by default. Each guide distills protocol detail into flows, patterns, and UX standards you can use in critique and handoff.

  • Technical specs → UX standards

    Read each EIP as flows, states, and patterns you can use in critique and handoff.

  • Patterns with UX consequences

    See what the wallet asks, what the app confirms, and which failure states to design.

  • Stop pinging protocol eng for every EIP

    Each guide explains what the standard does and how it shows up in product UX, in designer language.

Sample UX mockups

swap.demo

Swap

FromBalance 1,247.32 Max
USDC
100.00
$100.00
ToEstimated
ETH
0.0524
$99.65 $0.35 network fee

Intent → wallet → confirm

Intent
Wallet asks
App confirms

Do / don't patterns

Do

Name the user action and the consequence.

Don't

Expose raw method names as UX copy.

Browse by design problem
Developers

Understand the UX impact of EIPs

Bridge from protocol mechanics to what users experience—wallet prompts, app states, and the paths that fail.

  • Protocol → user experience

    See how each standard shows up in UI—not just in contract interfaces.

  • UX consequences spelled out

    States, errors, and vocabulary are explicit—skip reverse-engineering design intent in PR review.

  • Same guide designers read

    One decoded EIP both disciplines reference—aligned language before you ship.

Agent briefs + copy prompts

# Agent instructions

You are advising on UX for ERC-4337: Account Abstraction

## When advising

  • Treat MUST NOT as hard constraints unless explicitly overridden
  • Use Vocabulary for UI copy — do not use avoided terms
  • Preflight with simulation before the user signs

## MUST NOT

  • Expose UserOperation terminology as UI copy
  • Skip paymaster failure or sponsorship-ended states
  • Allow recovery with no security delay (24–72h)
  • Rely on a single guardian for account recovery

## States to design

  • Account not deployed
  • Paymaster quote unavailable
  • Simulation failed
  • Bundler pending
  • Security delay active

## Vocabulary

  • Use "Transaction" — avoid "UserOperation, UserOp"
  • Use "Sponsored" — avoid "Gasless, Free gas"
  • Use "Security delay" — avoid "Time lock"

## Design decisions

  • Who pays gas: show one fee model at a time (sponsored, native, or token)
  • Confirmation copy: summarize the human action first, details behind disclosure
Use with AI agents
Start reading

Popular guides and design tasks

Pick a curated standard or jump to the problem category that matches your current screen.

Popular now

By design task

Common designer questions

Quick answers before you dive into a category.

For checkout and onboarding batching, start with EIP-7702. For account creation or recovery, start with ERC-4337. For wallet picker UX, start with EIP-6963.