From eth-rnd-archive
Search the Ethereum R&D Discord Archive for protocol discussions. Use when looking up what was discussed about a specific topic (ePBS, PeerDAS, inclusion lists, etc.), finding decisions made in Eth R&D Discord, or tracking research conversations. Requires a local clone of ethereum/eth-rnd-archive.
How this skill is triggered — by the user, by Claude, or both
Slash command
/eth-rnd-archive:eth-rnd-archiveThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Search through the [Ethereum R&D Discord Archive](https://github.com/ethereum/eth-rnd-archive) — a machine-readable archive of all discussions in the Eth R&D Discord server. Updated weekly by EF DevOps.
Search through the Ethereum R&D Discord Archive — a machine-readable archive of all discussions in the Eth R&D Discord server. Updated weekly by EF DevOps.
Clone the archive repo locally (included in scripts/clone-repos.sh):
git clone --depth 1 https://github.com/ethereum/eth-rnd-archive.git ~/ethereum-repos/eth-rnd-archive
The archive contains daily JSON files per channel: {channel}/YYYY-MM-DD.json
# Find discussions about a topic
grep -rl "PeerDAS" ~/ethereum-repos/eth-rnd-archive/ --include="*.json" | head -20
# Search with context (shows the actual message content)
grep -r "inclusion list" ~/ethereum-repos/eth-rnd-archive/consensus-dev/ --include="*.json" -l
# Read messages from a specific channel and date
cat ~/ethereum-repos/eth-rnd-archive/epbs/2026-02-20.json | python3 -m json.tool
# Recent messages in a channel
ls -t ~/ethereum-repos/eth-rnd-archive/consensus-dev/*.json | head -5 | xargs cat | python3 -c "
import json, sys
for line in sys.stdin:
try:
msgs = json.loads(line)
for m in msgs:
print(f\"[{m['created_at'][:10]}] {m['author']}: {m['content'][:200]}\")
except: pass
"
Threads are stored in _threads/ subdirectories:
# List all threads in a channel
ls ~/ethereum-repos/eth-rnd-archive/epbs/_threads/
# Search within threads
grep -r "keyword" ~/ethereum-repos/eth-rnd-archive/epbs/_threads/ --include="*.json"
| Channel | Topics |
|---|---|
consensus-dev | CL protocol development, client coordination |
execution-dev | EL protocol development |
allcoredevs | Cross-layer coordination, ACD call follow-ups |
specifications | Formal spec discussions |
apis | Beacon/Engine API design |
client-development | Client team discussions |
| Channel | Topics |
|---|---|
epbs | Enshrined proposer-builder separation |
inclusion-lists | Inclusion list design (FOCIL, etc.) |
shorter-slot-times | Slot time reduction research |
data-availability-sampling | DAS / PeerDAS design |
l1-zkevm | CK EVM / L1 zkEVM |
l1-zkevm-protocol | CK EVM protocol details |
| Channel | Topics |
|---|---|
networking | General networking protocol discussions |
libp2p | libp2p protocol development |
peerdas-testing | PeerDAS test coordination |
peerdas-devnet-alerts | PeerDAS devnet status/alerts |
| Channel | Topics |
|---|---|
cryptography | Crypto primitives, hash functions |
formal-methods | Formal verification |
post-quantum | Post-quantum cryptography |
beacon-network | Beacon chain networking |
portal-network | Portal network protocol |
account-abstraction | AA design |
light-clients | Light client protocol |
Each JSON file contains an array of messages:
{
"author": "username",
"category": "Discord category",
"parent": "thread parent (empty if top-level)",
"content": "message text",
"created_at": "ISO8601 timestamp",
"attachments": [...]
}
Use the provided script to check for new messages in configured channels:
bash scripts/check-updates.sh [specific-date]
The script:
scripts/state.json)Edit scripts/config.json to configure which channels to track:
{
"channels": ["epbs", "consensus-dev", "allcoredevs", ...],
"repoPath": "~/ethereum-repos/eth-rnd-archive"
}
ls _threads/ gives a quick overview of discussion threads.grep -r '"author": "vbuterin"') for high-signal content.git -C ~/ethereum-repos/eth-rnd-archive pull before searching for recent discussions.npx claudepluginhub chainsafe/lodestar-claude-plugins --plugin eth-rnd-archiveTracks Ethereum protocol evolution, EIP lifecycle, fork schedules via forkcast.org and EIPs repo. Use for checking feature status, upcoming changes, or proposing EIPs.
Provides real-time analytics on Web3 ecosystems, blockchain repositories, and developer activity via MCP tools. Use for trending projects, top developers, and ecosystem growth data.
Scans HN, Lobsters, Reddit, and tech blogs for community opinions and experience reports on technologies or approaches. Use for gathering perspectives.