By Year
Watch the timeline breathe.
Compare proposal traffic year by year to find active eras, quiet stretches, and the moments when standards work picked up speed.
Best for spotting long-term cycles and release-era surges.
Documentation Hub
Track Ethereum Proposals
and Governance
Real-time documentation for proposal lifecycle, upgrade progress, and editorial activity across EIPs, ERCs, and RIPs, with structured guides and references for contributors and developers.
EIPs Indexed
Complete standards archive
1,152
All tracked standards across the docs hub
Active Upgrades
Current upgrade windows
12
Coordinated network changes in flight
Active Proposals
Hover for breakdown
1,152
Draft 349 · Other active states 803
About
EIPInsight turns Ethereum standards activity into something people can actually navigate.
We build an operational view of EIPs, ERCs, RIPs, proposal workflows, and governance movement so builders, editors, researchers, and newcomers can understand what is changing and why.
Mission
Make Ethereum standards and governance legible, explorable, and operationally useful.
What We Track
EIPs, ERCs, RIPs, PR activity, editor workflows, contributor graphs, and status transitions.
Why It Exists
Because governance data is public, but still too fragmented for most people to work with efficiently.
Built By
Avarch with support from the Ethereum ecosystem and partners close to standards operations.
Why We Built This
Standards and governance should not require institutional memory to follow.
Ethereum governance happens across repositories, pull requests, review queues, forum threads, upgrades, and informal coordination. The data is public, but the workflow is still hard to inspect as a system.
EIPInsight exists to reduce that gap. We aggregate the moving parts, normalize them into product surfaces, and help people answer practical questions: what changed, what is stuck, who is active, what upgrade work depends on what, and where to go next.
The goal is not just more charts. The goal is operational clarity for anyone trying to understand or participate in Ethereum standards.
How People Use It
From reading standards to working with them.
Search and discovery
Search proposals, people, and governance events with structured filters instead of manual repository digging.
Analytics and monitoring
Track lifecycle movement, editorial load, PR activity, and standards composition through dashboards and timelines.
Workflow tooling
Use boards, dependency maps, builder, and explorer views to move from reading governance to working with it.
Context and commentary
Pair raw data with commentary, docs, videos, and news so the platform stays useful for both learning and operations.
Standards & Proposals
EIPs Explained
EIPs are the primary mechanism for proposing changes to the Ethereum protocol. They follow a standardized process from initial discussion through community review to final implementation.
// Example: EIP-1559 (Fee Market Change)
{
"number": 1559,
"title": "Fee market change for ETH 2.0 compatibility",
"status": "Final",
"type": "Standards Track",
"category": "Core"
}
ERCs Explained
ERCs define standards for tokens and smart contract interfaces. The most well-known is ERC-20 (fungible tokens), but there are many others including ERC-721 (NFTs) and ERC-1155 (multi-token standard).
RIPs Explained
RIPs provide a standardized way to propose and discuss improvements to rollup solutions and scaling solutions built on Ethereum.
Proposal Lifecycle
📋 Idea
Initial discussion and feedback gathering from the community
✍️ Draft
Formal proposal writing with specification details
🔍 Review
Community and core developer review and feedback
✅ Final
Accepted and ready for implementation
Explore
Explore views turn the standards feed into focused lenses, helping you spot spikes, stalls, ownership patterns, and category shifts without digging through raw lists.
By Status
See where work is moving.
Track Draft, Review, Last Call, Final, and Deferred states as a funnel so you can instantly see what is progressing and what needs attention.
Best for triage, bottleneck hunting, and progress checks.
By Role
Map the people behind each change.
Follow authors, editors, reviewers, and implementers to understand who is shaping the proposal, who is reviewing it, and where responsibility sits.
Best for ownership, collaboration, and workload visibility.
By Category
Compare what kind of work it is.
Group standards by category to separate Core work from ERCs, interfaces, and other tracks so the mix of proposal types stays easy to read.
Best for understanding where the pipeline is concentrated.
Upgrade Watch
Follow how Ethereum upgrades move from proposals into coordinated network change. This section ties together EIP inclusion, client readiness, and the major milestones that shape each upgrade cycle.
Upgrade Features
Upgrade sequence
Follow previous upgrades, current focus, and next planned fork windows in one row.
EIP composition
Inspect how included, soft-frozen, deferred, and dropped EIPs evolve across checkpoints.
Author and editor context
See who authored and reviewed key proposals to understand ownership and bottlenecks.
Readiness tracking
Monitor readiness signals before activation so teams can plan releases and audits.
Previous Upgrades
Pectra
Fusaka
Glamsterdam
Hegota
Next TBD
How to Read Upgrades
Step-by-step: read upgrades properly
Start from the timeline row, then drill into EIP composition and status transitions. Use this order to quickly understand what changed, why it changed, and what is likely to ship next.
Step 1: Identify the upgrade window
Find the target upgrade (for example Glamsterdam) and note its position between previous and upcoming forks. This gives you immediate release context.
Step 2: Read timeline milestones left to right
Track milestones chronologically to understand dependency order. Earlier milestones usually represent prerequisites for later activation decisions.
Step 3: Check EIP status composition
Review included, review, blocked, deferred, and removed groups. This tells you what is stable versus still moving in governance discussions.
Step 4: Verify execution and consensus impact
Map each major EIP to execution-layer, consensus-layer, or cross-layer behavior so implementation teams can estimate testing scope and risk.
Step 5: Watch readiness and movement weekly
Compare weekly snapshots to detect movement in EIP buckets. A shift from review to included is usually the strongest signal of likely inclusion.
What to monitor first
Included EIP count, blocked proposals, and editor comments are the fastest indicators of upgrade health.
When to dig deeper
If an upgrade row stalls, inspect PR activity and unresolved review notes before assuming timeline slips.
How this helps teams
Developers, researchers, and operators can align implementation and communication plans using the same source of truth.
Upcoming: Glamsterdam
EIPInsight uses the upgrade timeline to keep the next phase of Ethereum visible, from current standards work through the proposals expected to land in Glamsterdam and beyond.
Analytics
Analytics is designed for decision making, not just reporting. Use the guides below to understand what each view is for, which controls matter most, and how to read the visuals correctly.
EIPs Analytics
Use this to read proposal health.
Start here when you need a top-level pulse on standards flow, backlog risk, and which proposal categories are dominating the system.
Key features
- Governance health cards for active, stalled, and largest-status-group signals.
- Pipeline status bars for Draft, Review, Last Call, Final, and stalled buckets.
- Proposal composition donut to compare Core, ERC, and smaller tracks quickly.
- Status transition flow for tracking where proposals move next.
How to read properly
- Check stalled versus active first to measure current decision pressure.
- Read the pipeline bars for bottleneck stage, not only total count.
- Use composition only as context for the backlog, not as success rate.
- Confirm with transition flow before concluding momentum changed.
PR Analytics
Use this to monitor delivery pace.
This view shows how quickly work enters and exits review. It is best for spotting merge slowdowns, seasonal load, and review throughput changes.
Key features
- Open, created, merged, and closed counters for current context month.
- Monthly trend chart combining created and merged bars with open-PR line.
- Category breakdown by process and participant state.
- Time-range and repository filters to isolate a specific scope.
How to read properly
- Compare created versus merged in the same period before reading backlog.
- Use open line trend to detect accumulation, not one-off spikes.
- Cross-check category bars to see where waiting time is concentrated.
- Change repo filter to confirm whether the pattern is global or local.
Issues Analytics
Use this to track blockers and support load.
The Issues page helps you inspect unresolved friction, recurring labels, and where open problem volume may slow standards progress.
Key features
- Open and active counters for fast issue-pressure checks.
- Monthly trend chart for created, closed, and open end-of-month trajectory.
- Label distribution chart to identify recurring problem types.
- Open-issues table with repo, author, and comments for triage.
How to read properly
- Watch open end-of-month trend first to see if debt is compounding.
- Use label distribution to prioritize issue classes, not individual tickets.
- Then drill into the table for owner and repo-specific action.
- Recheck after filter changes to avoid overfitting a single repository.
Board View
Use this to execute day-to-day triage.
The board is your operational workspace for selecting exact PR subsets and moving from dashboard insight to concrete follow-up actions.
Key features
- Search plus multi-select filters by status, process type, and track.
- Stackable filter chips for precise working sets.
- Table view with author, wait time, process, labels, and open status.
- Export actions for CSV, markdown, and direct link sharing.
How to read properly
- Start broad, then narrow with one dimension at a time.
- Sort by wait and status to surface the most delayed items first.
- Use labels as context after selecting process and status scope.
- Save and share filtered links for repeat weekly reviews.
Editors
Track editorial throughput, response time, and concentration of review ownership.
Reviewers
Measure reviewer cycles, leaderboard balance, and review latency distribution.
Authors
Understand repeat versus new author mix and proposal outcome patterns.
Contributors
Read contribution heatmaps and activity types to detect participation trends.
Insights
Insights helps you move from metrics to interpretation. Each module below explains how to use the view, what controls matter, and how to read outcomes without misinterpreting short-term noise.
Monthly Insight Label
Year-Month Analysis
Track how governance changes month to month.
Use this when you want trend direction: whether proposal flow is accelerating, slowing down, or rotating between EIP, ERC, and RIP tracks.
Main features
- Status transition summary by standards type for a chosen month.
- Change-mix donut to split status, content, and metadata movement.
- Editorial activity leaderboard showing who touched the most proposals.
- Draft-vs-Final history line to compare early-stage versus finalized output.
How to read it properly
- Pick month and repo scope first so all panels share one context.
- Read status-transition table before the donut to understand what moved.
- Use leaderboard as participation context, not quality score.
- Confirm with Draft-vs-Final history to avoid overreacting to one month.
Governance Label
Governance & Process
Measure process speed and friction.
This view is your operational health report: it shows decision speed, process stage conversion, and where waiting states are accumulating.
Main features
- Open pipeline, merge rate, median decision time, and stalled counts.
- Process flow bars from opened to reviewed, merged, and closed.
- Current governance state panel with waiting-on-author/editor splits.
- Decision speed table by repo for quick benchmark comparison.
How to read it properly
- Start with merge rate plus median decision time as the core health pair.
- Use process flow conversion rates to spot stage-by-stage drop-off.
- Check governance state legend to identify whether delays are author- or editor-side.
- Compare EIPs and ERCs in the decision-speed table before escalating conclusions.
Editorial Commentary Label
Editorial Commentary
Generate lifecycle intelligence for a proposal.
Use this module for a deep read on one proposal. It converts raw status history and PR context into an editor-style narrative of momentum and risk.
Main features
- Proposal search (EIP, ERC, or RIP) with direct lifecycle analysis trigger.
- Narrative summary of stage durations, transition cadence, and churn.
- Context cues for PR activity intensity and likely readiness signals.
- Focused single-proposal lens for review calls and contributor alignment.
How to read it properly
- Search a specific proposal, then read stage durations before commentary tone.
- Treat churn markers as risk indicators, not automatic blockers.
- Cross-reference PR intensity with current status to judge real readiness.
- Use the report to prepare review notes and next-step ownership.
Tools
Productivity tools support day-to-day standards operations, from drafting proposals to tracking dependencies and upgrade windows.
EIP Builder
Use guided templates and validation hints to draft cleaner proposals faster.
Timeline
Track changes chronologically with milestone-level context for upgrades and proposal states.
FAQ
Quick answers about standards, governance workflow, and how the platform works.
Get Started
Basics (6)
What is an EIP?
An EIP (Ethereum Improvement Proposal) is a design document that introduces a feature, process change, or environment change for Ethereum. EIPs are the main mechanism for proposing and documenting protocol and ecosystem improvements.
What is an ERC?
An ERC (Ethereum Request for Comments) is a category of EIP focused on application-level standards such as token interfaces and contract conventions. ERC standards help wallets, apps, and tools interoperate consistently.
What is a RIP?
A RIP (Rollup Improvement Proposal) is a standards document for Layer 2 rollup systems. RIPs define improvements and shared conventions for rollup implementations and ecosystem coordination.
What is the difference between an EIP, ERC, and RIP?
EIP is the broad proposal framework for Ethereum improvements. ERCs are application-level standards within that framework. RIPs are rollup-focused standards for Layer 2 ecosystems. They share proposal mechanics but target different scopes.
Where should I start if I am new to Ethereum standards?
Start with EIP-1 to understand the proposal process. Then read a few widely used standards such as ERC-20 and ERC-721, and track current drafts to see how review and governance shape proposals over time.
How do I contribute to the EIP process?
You can contribute by drafting proposals, reviewing open drafts, commenting during Last Call, improving specifications, and helping with implementation feedback. Many contributors begin by improving existing drafts before opening a new proposal.
Workflow
Process (7)
How does an EIP move from Draft to Final?
An EIP moves through statuses such as Draft, Review, Last Call, and Final. In Draft, the proposal evolves. Review and Last Call gather final feedback. Final means the proposal is accepted and considered complete from a standards perspective.
Who are EIP Editors?
EIP Editors maintain process quality. They review formatting and process compliance, coordinate status changes, and keep the repository organized. Editors do not unilaterally decide technical acceptance of proposals.
What is Last Call?
Last Call is the final review window before an EIP can become Final. It gives the community a final opportunity to comment and raise objections before status advancement.
How long does review usually take?
There is no fixed duration. Simple proposals can progress quickly, while complex or controversial ones can take months or longer. Review speed depends on technical complexity, editorial feedback, and community consensus.
What usually blocks a proposal from moving forward?
Common blockers include incomplete specifications, unresolved objections, weak implementation plans, missing test coverage, and unclear ecosystem impact. Coordination with upgrade timing can also delay status progression.
Who decides whether a proposal is accepted?
Acceptance is not controlled by one person. Editors manage process and quality, while technical acceptance depends on broad alignment across researchers, implementers, client teams, and community stakeholders.
Why does a proposal sometimes move backward in status?
Status can move backward when new issues are discovered, important objections arise, or substantial spec changes are needed. This is normal in open governance and helps prioritize correctness over speed.
Platform
Platform (7)
What does EIPInsight track?
EIPInsight tracks EIPs, ERCs, and RIPs across their lifecycle, plus pull request activity, governance signals, editor activity, contributor behavior, and proposal-level analytics to explain how standards evolve.
How often is data updated?
Core status and repository data are synchronized frequently from source repositories. Some aggregated analytics are cached and refreshed on intervals to balance freshness and performance.
Can I download data?
Yes. Most analytics and standards views support export workflows such as CSV or JSON so teams can run custom analysis outside the app.
Which EIPInsight pages should I use for different tasks?
Use Standards for proposal details, Analytics for trends and workload, and Governance for process context. The best path depends on whether you are researching, building, or coordinating reviews.
Does EIPInsight cover pull requests and issues too?
Yes. EIPInsight links standards data with pull requests, issue activity, review metadata, and governance context so you can understand both proposal text and implementation discussion.
Do I need an account or persona to use EIPInsight?
No. Most content is available without sign-in. Personas are preference presets that tune navigation and defaults for different workflows such as developer, editor, or researcher.
How current are analytics and board views?
Operational views are designed to stay close to source activity, while heavier analytics may use short-lived caching. This keeps dashboards responsive while preserving trustworthy trend reporting.