Make your EIP legible

Where this data shows up#

• EIP page, Analysis tab

  Your layman description leads as the TL;DR, followed by benefits, tradeoffs, and stakeholder impacts.

• EIP page, FAQ tab

  Each answer gets its own deep link, so people can cite a single answer in a thread.

• Upgrade page cards

  Expanding an EIP shows your benefits, tradeoffs, and stakeholder impacts.

• Stakeholder view

  Groups every EIP in a fork by who it affects, built entirely from your stakeholder impacts.

How to submit#

1. 1

   Fork github.com/ethereum/forkcast

2. 2

   Edit the file for your EIP, or create it if it does not exist yet.

   src/data/eips/{EIP_NUMBER}.json

3. 3

   Validate that the file parses and matches the schema.

   npm install && npm run compile-eips

4. 4

   Confirm your EIP is no longer flagged as missing data.

   npm run audit-eips -- --fork <ForkName>

5. 5

   Open a PR titled "Add EIP-{number}: {title}", or "Update EIP-{number}" for edits to an existing file.

Field guide#

Every field below is optional in the schema, but the first five are what the site actually renders, and what the data audit checks for.

Annotated template#

The champion-owned subset of the schema. Copy this into src/data/eips/{id}.json, replace the placeholders, and delete any optional block you are not using.

{
  "id": 9999,
  "layer": "EL",
  "reviewer": "expert",
  "discussionLink": "https://ethereum-magicians.org/t/your-thread/00000",

  "laymanDescription": "Two or three plain sentences. What changes, for someone who does not read specs.",

  "benefits": [
    "One concrete, checkable claim, ideally under ~16 words",
    "Another one",
    "Aim for four to six of these total"
  ],

  "tradeoffs": [
    "An honest cost, risk, or burden this introduces",
    "Use null instead of an empty array only if there truly are none"
  ],

  "stakeholderImpacts": {
    "endUsers": { "description": "About 20 words, or 'No impact.'" },
    "appDevs": { "description": "About 20 words, or 'No impact.'" },
    "walletDevs": { "description": "About 20 words, or 'No impact.'" },
    "toolingInfra": { "description": "About 20 words, or 'No impact.'" },
    "layer2s": { "description": "About 20 words, or 'No impact.'" },
    "stakersNodes": { "description": "About 20 words, or 'No impact.'" },
    "clClients": { "description": "Implementation complexity, not user benefit." },
    "elClients": { "description": "Implementation complexity, not user benefit." }
  },

  "faq": [
    { "question": "What's in EIP-9999?", "answer": "Markdown is supported, including **bold**, lists, links, and \n\n for paragraphs." },
    { "question": "What problem does it solve?", "answer": "..." }
  ],

  "supportingDocuments": [
    { "label": "Benchmark results", "url": "https://..." }
  ],

  "forkRelationships": [
    {
      "forkName": "Glamsterdam",
      "statusHistory": [{ "status": "Proposed", "call": "acde/999", "date": "2026-01-01" }],
      "champions": [{ "name": "Your Name", "discord": "@yourhandle" }]
    }
  ]
}

Before you open the PR#

• All eight stakeholder impacts are filled in, including the "No impact" ones.
• tradeoffs is a real list, or deliberately null because there genuinely are none.
• Every benefit and tradeoff is a single claim, ideally under ~16 words.
• The layman description has no jargon and no acronyms, ideally under ~60 words.
• Each FAQ answer stands on its own, because it can be linked to in isolation.
• npm run compile-eips passes.
• npm run audit-eips reports no issues for your EIP.