protocol

Verify Ethereum feature upgrade and EIP readiness via forkcast and specs.

7|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/Zodomo/DrandVerifier --skill protocol-zodomo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: protocol
Source: https://github.com/Zodomo/DrandVerifier/tree/main/.opencode/skills/ethskills/protocol
Command: npx skills add https://github.com/Zodomo/DrandVerifier --skill protocol-zodomo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid stale or incorrect assumptions about Ethereum upgrades by showing how to verify whether a feature or EIP is genuinely planned, scheduled, or already implemented.

Core Features & Use Cases

  • Forecast with real status signals: Determine whether a feature is scheduled vs considered by using forkcast’s fork relationships and EIP status.
  • Find canonical specs quickly: Jump from an EIP to the fork-scoped implementation specs in execution-specs and/or consensus-specs.
  • Validate recency of work: Cross-check discussion recency via forkcast calls and eth-rnd-archive to distinguish active work from outdated claims.
  • Use Cases: answering “is it coming?”, planning integrations that depend on future protocol capabilities, and preparing proposals with correct context for where decisions happen.

Quick Start

Ask: “Is Verkle or EIP-XXXX planned for the next Ethereum fork, and what’s the most authoritative source for 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 EIP is scheduled for the next fork?

Ethereum upgrade status is determined by checking forkcast.org for fork relationships and the EIP repository for its lifecycle stage, distinguishing whether a feature is Scheduled for Inclusion (SFI) or Considered for Inclusion (CFI).

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

SFI means Scheduled for Inclusion, CFI means Considered for Inclusion, and DFI means Declined for Inclusion. These EIP lifecycle stages determine whether a protocol feature is actively shipping, being evaluated, or rejected.

How do I find canonical execution specs for an Ethereum EIP?

Find canonical protocol behavior specs by locating the EIP's lifecycle state, then jumping directly to the fork-scoped implementation details within the execution-specs and consensus-specs repositories for authoritative protocol behavior.

How can I verify if an Ethereum protocol upgrade is still being actively worked on?

Validate Ethereum protocol upgrade recency by cross-checking discussion timelines via forkcast calls and eth-rnd-archive, which helps distinguish active development work from outdated or stale feature claims.

Does checking Ethereum protocol readiness require consulting forkcast.org first?

Yes, checking Ethereum protocol readiness requires consulting forkcast.org first to verify fork relationships, then reviewing EIPs for lifecycle state, and finally checking execution-specs and consensus-specs for canonical protocol behavior.

When do I need to validate Ethereum roadmap readiness for protocol features?

You need to validate Ethereum roadmap readiness when planning integrations that depend on future protocol capabilities, preparing proposals with correct context, or answering whether a specific feature is actually coming in the next upgrade.