About EIPs for Designers

What this reference covers

All Standards covers numbered Ethereum Improvement Proposals (EIPs), Ethereum Requests for Comments (ERCs), and Monad Improvement Proposals (MIPs), including proposals that are not Final. Chain guides explain documented network behavior and are not numbered proposals. Find both through problems, user journeys, search, and the Monad collection. Entries can include UX implications, patterns, states, vocabulary, related guides, official sources, and an agent-ready export.

How to use it

Use this site to frame product decisions and make protocol dependencies visible during planning, design reviews, and implementation. Start with the problem or journey that matches your flow, then open a guide. Numbered proposals show their lifecycle status; chain guides show a review date. Check the official source and implementation support before treating a capability as available. This reference explains implications; it does not replace the canonical specification, documentation, or security review.

• Choose By Problem when the UX challenge is already known.
• Choose By Journey when you are mapping a complete user flow.
• Choose an agent brief when an AI coding or design tool needs explicit guardrails.

Proposal sources

For Ethereum EIPs, use the published EIP pages and the ethereum/EIPs repository. For Monad MIPs, use the MIPs repository for proposal text and status, and the Monad Research Forum for discussion and proposals still taking shape. A forum post alone does not confirm that a proposal is Final or active on a network.

Security responsibility

This reference is educational guidance, not a security audit, implementation review, or guarantee that a protocol, wallet, contract, dependency, or integration is safe. Before you ship a feature, you are responsible for checking the systems you use and the risks your product introduces.

• Check the site's Updated date in the footer, then compare this guidance with the current official EIP or MIP source (or the linked source for a chain guide). The site-wide date reflects the latest recorded update, not a review of every guide. Verify proposal status, network activation, wallet support, and contract support before relying on a capability.
• Threat-model the full flow, including signing, approvals, permissions, account recovery, transaction simulation, failure states, replay, phishing, and compromised dependencies.
• Show and verify the exact domain, chain, recipient, asset, amount, calldata, fee, approval scope, and signature intent before a person confirms an action. A standard, name, or icon is not proof that an action is safe.
• Test malicious and unexpected inputs, failed or partial execution, revoked permissions, network changes, and recovery paths. Have qualified security reviewers audit high-risk code and dependencies before production.
• Never ask people to share seed phrases, private keys, wallet credentials, or signing secrets. Follow secure key-management and incident-response practices for your product.

Who maintains the reference

EIPs for Designers is built and maintained by the Monad Foundation. The project is data-as-code: standards and detailed guidance live in the repository, are serialized into human and machine-readable surfaces, and are updated through reviewable changes. Monad is called out where chain behavior changes the design implication; the reference still distinguishes Monad-specific observations from standards that apply across Ethereum-compatible environments.