protocol

Verify Ethereum EIP and fork status using forkcast.org primary sources.

1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/tawf-labs/zkt-hackathon --skill protocol-tawf-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: protocol
Source: https://github.com/tawf-labs/zkt-hackathon/tree/main/.agents/skills/ethskills/protocol
Command: npx skills add https://github.com/tawf-labs/zkt-hackathon --skill protocol-tawf-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid acting on stale or incorrect information about Ethereum protocol changes by showing how to verify whether a feature or EIP is actually planned, scheduled, or already included.

Core Features & Use Cases

  • EIP lifecycle clarity: Distinguishes Draft/Review/Last Call/Final and explains how fork-scoped inclusion states (CFI/SFI/DFI) work.
  • Fork status verification: Guides you to confirm current readiness and fork relationships using forkcast.org rather than relying on outdated blogs or roadmap diagrams.
  • Rational, source-driven answering: Provides a practical source order (forkcast.org → eth-rnd-archive → ethereum/pm → EIPs → execution/consensus specs) to answer “what’s next” accurately.
  • Use cases: When you need to (a) decide whether to build for an upcoming capability, (b) check if a claimed feature is real and scheduled, or (c) propose a change and need to understand the process.

Quick Start

Ask the skill whether a specific feature or EIP is scheduled for a particular upcoming fork, and it will walk you through checking forkcast status, EIP status, and recent discussion signals.

Frequently Asked Questions about protocol

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

FAQPage Schema
How do I verify the real current status of an Ethereum feature or EIP?

To verify the real current status of an Ethereum feature or EIP, check forkcast scheduling and EIP lifecycle state using sources like forkcast.org and the EIP repository, grounding conclusions in the latest fork scope rather than outdated announcements.

What is the difference between CFI, SFI, and DFI inclusion states for Ethereum protocol upgrades?

CFI, SFI, and DFI are fork-scoped inclusion states for Ethereum protocol upgrades that distinguish whether a proposal is considered for inclusion, scheduled for inclusion, or deferred, clarifying an EIP's actual fork readiness beyond its basic lifecycle.

What is the best way to check if an Ethereum hard fork includes a specific EIP?

The best way to check if an Ethereum hard fork includes a specific EIP is to follow a source order starting with forkcast.org, then eth-rnd-archive, ethereum/pm, EIPs, and execution/consensus specs to confirm current readiness accurately.

How do I track the EIP lifecycle from Draft to Final for Ethereum protocol changes?

Track the EIP lifecycle for Ethereum protocol changes by checking the proposal's progression through Draft, Review, Last Call, and Final stages, while cross-referencing forkcast.org to determine if it has actual scheduled inclusion in an upcoming fork.

Why does my roadmap verification for an Ethereum upgrade show conflicting information?

Roadmap verification for Ethereum upgrades often shows conflicting information because older blogs and diagrams become outdated; relying on primary sources like forkcast.org and current fork scope ensures accurate live versus coming versus deprioritized status.