protocol

Tracks Ethereum protocol upgrades, EIP lifecycle status, and fork inclusion using primary sources.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/m-faran/genie-markets --skill protocol-m-faran
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: protocol
Source: https://github.com/m-faran/genie-markets/tree/main/.agent/skills/ethskills/protocol
Command: npx skills add https://github.com/m-faran/genie-markets --skill protocol-m-faran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ethereum's roadmap changes constantly, and outdated blog posts or docs often mislead developers about which features are live, scheduled, or abandoned. This Skill provides a verified workflow for checking the real status of any EIP or protocol feature using primary sources like forkcast.org, the EIPs repository, and ACD call archives. ## Core Features & Use Cases - Feature Status Verification: Follow a four-step process (forkcast, EIP status, recent discussion, devnet matrix) to determine if a feature is CFI, SFI, DFI, or deprioritized. - Fork Tracking: Look up what shipped in past forks (Shapella, Dencun, Pectra, Fusaka) and what is scoped for upcoming ones like Glamsterdam. - EIP Engagement Guidance: Learn how to draft an EIP per EIP-1, post to EthMagicians, and request ACD agenda time to propose protocol changes. - Use Case: Your human asks whether Verkle trees are coming in the next fork. Instead of citing a stale 2023 blog post, you check forkcast and report that Verkle was deprioritized in favor of binary trees due to ZK and quantum concerns. ## Quick Start Ask the agent to check whether a specific EIP or Ethereum feature is scheduled for an upcoming fork and report its current status.

Frequently Asked Questions about protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if an Ethereum feature is planned for the next fork?▼

Check forkcast.org first to see if the EIP is marked CFI (considered) or SFI (scheduled) for a specific fork. Then verify recent discussion in ACD call summaries and the devnet implementation matrix to confirm active development.

What is the difference between CFI and SFI in the EIP process?▼

CFI (Considered for Inclusion) means core devs are evaluating the EIP for a fork but have not committed. SFI (Scheduled for Inclusion) means it is confirmed, devnets are testing it, and it ships barring disasters. Both are defined in EIP-7723.

Why do Ethereum roadmap predictions often turn out wrong?▼

Roadmap diagrams and blog posts are aspirational, not commitments. Features get deprioritized when technical requirements change, dependencies slip, or better alternatives emerge, as happened when Verkle trees were replaced by binary trees.

Does an EIP with Final status mean it is live on mainnet?▼

No. Final means the specification is complete, but Core EIPs still need to be scheduled into a hard fork. For the authoritative spec of what is actually live, check the execution-specs or consensus-specs repositories.

How do I propose a new opcode or precompile for Ethereum?▼

First search the EIPs repository for existing proposals, then draft an EIP following EIP-1, post it to EthMagicians for discussion, and request agenda time on an All Core Devs call. Most EIPs never ship, so consider application-layer or L2 alternatives first.