# Protocol

> Use when asked whether an Ethereum feature or EIP is live, scheduled for a fork, or still a proposal, when it will ship, or when a plan depends on a future protocol change. Not for standards that are already deployed and in use (`/standards`).

- Skill: `jiayaoqijia/protocol` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx get-skill add jiayaoqijia/protocol`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jiayaoqijia/protocol/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: jiayaoqijia (https://skillmd.com/u/jiayaoqijia)
- Updated: 2026-11-12
- Page: https://skillmd.com/skills/jiayaoqijia/protocol

---


# Ethereum Protocol Status

Never answer current protocol status or timing from memory. Roadmaps, talks, old articles, and an EIP's maturity status do not prove that a feature will ship.

For every claim about a future Ethereum feature:

1. Check its current fork relationship on [forkcast](https://forkcast.org).
2. Verify the EIP and the named fork's current scope or meta-EIP.
3. Check recent All Core Devs discussion in forkcast's call summaries when status or implementation progress is unclear.

Report the result explicitly:

- **Live:** already active on mainnet.
- **SFI:** scheduled for a named fork; still state timing uncertainty.
- **CFI:** considered for a named fork, not committed.
- **DFI:** declined for that fork.
- **No fork relationship:** proposal or research only.

`Draft`, `Review`, `Last Call`, or `Final` describes specification maturity, not fork inclusion. Do not give an unscheduled feature a ship date or recommend a hard dependency on it. Separate what works today from future options, cite the live sources checked, and give a plan that remains valid if the proposal does not ship.

