skills.rest
erigontech
erigontechOFFICIAL
Explore all skills by this author →
WebsiteGitHub

erigon-implement-eip

Implements a new EIP for an Erigon hardfork from spec lookup through tests and wrap-up.

3.6k|1.5k|Updated May 27, 2019
Search Tags:#Ethereum#GO#erigon#eip#protocol implementation#spec tests#hardfork
One-click install
npx skills add https://github.com/erigontech/erigon --skill erigon-implement-eip
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: erigon-implement-eip
Source: https://github.com/erigontech/erigon/tree/main/.claude/skills/erigon-implement-eip
Command: npx skills add https://github.com/erigontech/erigon --skill erigon-implement-eip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing a new Ethereum Improvement Proposal in the Erigon client requires navigating EIP specs, fork meta documents, devnet deltas, and both execution-layer and consensus-layer test suites. This Skill structures that entire workflow so nothing is missed.

Core Features & Use Cases

  • Spec and dependency analysis: Fetches the EIP spec, referenced EIPs, hardfork meta EIPs, and optional devnet specs, then maps them to Erigon packages.
  • Guided implementation and validation: Checks for prior work, implements the change, runs make lint, and executes EEST spec test shards plus CL spectest suites.
  • Documented wrap-up: Produces a summary of touched files, design decisions, and test coverage saved to agentspecs/.
  • Use Case: Ask to implement EIP-7892 for the Amsterdam fork on devnet-3, and the Skill walks through spec analysis, code changes, devnet test shards, and a final summary.

Quick Start

Implement EIP-7892 for the Amsterdam fork using the devnet-3 specification and run the relevant devnet test shards.

Frequently Asked Questions about erigon-implement-eip

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

FAQPage Schema
How do I implement a new EIP in the Erigon client?▼

Provide the fork name, EIP number, and optionally a devnet name. The workflow fetches the EIP spec, maps it to Erigon packages, checks for prior implementations, makes the code changes, runs lint and spec tests, and saves a summary to agentspecs/.

Which tests should I run when implementing an EIP in Erigon?▼

Run the EEST spec test shards via make eest-spec-* targets, prioritizing the -devnet shards for the fork under development. If the EIP touches the consensus layer, also run the cl/spectest suite with the per-fork make target.

Does Erigon EIP implementation cover both execution and consensus layers?▼

Yes. Erigon contains both an EL implementation under the execution package and a CL implementation under the cl package, so EIPs affecting either or both layers are handled, including CL spec tests via cl/spectest.

Why do EEST devnet test shards show unexpected failures in Erigon?▼

A common cause is a stale evm binary when invoking tools/run-eest-spec-test.sh directly instead of the make target, which skips the rebuild. Always run shards via make eest-spec-<shard> so a fresh binary is built first.

What happens when a spec test contradicts the EIP specification?▼

The workflow instructs not to silently fix such tests. Instead it documents the discrepancy, since upstream reference implementations can contain bugs, and asks for review and new guidance before proceeding.

Related Skills

Explore More Software Engineering Skills→
mashharukimashharuki

protocol

Determine Ethereum EIP and fork status by verifying proposal lifecycle and client support.

Community
Intermediate
CAPHTECHCAPHTECH
1

concurrency-observation

Detect data races, deadlocks, and timing-dependent bugs in concurrent programs.

Official
Advanced
warpdotdevwarpdotdev
292

spec-driven-implementation

Enforce product and tech specs before implementation in source control.

Official
Intermediate
sinchsinch
9

sinch-number-lookup-api

Look up E.164 phone number details including carrier, line type, SIM swap, and reassigned-number status.

Official
Intermediate