Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →austintgriffith/protocol
How Ethereum evolves — EIP lifecycle, fork process, where decisions happen, and how to track upcoming changes.
Passed 21 of 22 test cases with the skill, and 14 of 22 without it.
and 6 more in the full report
7 fixed14 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before launching an application that relies on an upcoming hard fork feature, an engineer wants to verify whether consensus and execution clients actually support the feature on multi-client devnets. Recommend the primary resource to check for devnet implementation matrices.
| Checked | Without skill | With skill |
|---|---|---|
| The response designates forkcast.org as the source for devnet matrix tracking. | Missed | Passed |
The instructions your model reads when the skill loads.
"Ethereum is a static platform." No. Ethereum upgrades roughly every 6-12 months via hard forks. Features you read about in old tutorials may have changed. Features your human wants may be shipping next fork.
"EIPs are just proposals." An EIP (Ethereum Improvement Proposal) is the canonical specification for every protocol change. But "EIP" doesn't mean "not implemented" — EIP-1559 shipped in 2021. Check the status.
"The Ethereum Foundation decides what ships." No. Protocol changes are decided through the All Core Devs (ACD) process — a rough consensus among client teams, researchers, and the broader community. The EF has influence but not control.
"I'll just check the docs." Ethereum.org docs lag behind the protocol. For what's actually live or coming, check the primary sources below.
"Verkle trees are planned for the next fork." Maybe, maybe not. Roadmap diagrams are aspirational. Blog posts go stale. "Planned" features get deprioritized all the time. Verkle was the leading statelessness candidate for years — then in 2024-2025, concerns about ZK-compatibility and quantum resistance shifted focus to binary trees instead. Always check current fork scope, not old announcements.
This is where AI agents mess up constantly. Here's how to not be wrong:
Ethereum's roadmap evolves. A 2023 blog post saying "Verkle is coming" doesn't mean Verkle is still coming. A conference talk from last year may reference plans that have since changed. Vitalik's roadmap diagrams show direction, not commitments.
Features get deprioritized when:
Step 1: Check forkcast first Go to forkcast.org and search for the feature or EIP. This shows:
If forkcast shows it's SFI → it's actually scheduled.
test cases passed, vs 14 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.