feat(rpc): add web3, net namespaces and expand debug/eth for tooling compatibility

[prestwich]

Summary

[Claude Code]

Adds standard Ethereum JSON-RPC namespaces and methods for general tooling compatibility (Blockscout, Routescan, wallets, etc.). Driven by ENG-960.

• web3 namespace: clientVersion, sha3
• net namespace: version, listening
• eth: protocolVersion
• debug: getRawHeader, getRawTransaction, getRawBlock, getRawReceipts, traceBlock (raw RLP), traceCall

Total: 56 routes across 5 namespaces (eth 41, debug 9, signet 2, web3 2, net 2).

Methods that don't apply to Signet (mining, keystore, txpool, proofs, blobs, net_peerCount) are not registered and return method_not_found.

Key implementation details

• debug_traceBlock decodes raw RLP, recovers senders, reuses extracted trace_block_inner shared tracing loop
• debug_traceCall combines EVM state resolution (like eth_call) with the tracer infrastructure
• debug_getRawReceipts reconstructs consensus ReceiptEnvelope from ColdReceipt (strips RPC log metadata)
• debug_getRawBlock assembles full block from separately-stored header + transactions
• New DebugError variants: RlpDecode, SenderRecovery

Test plan

• All 35 existing tests pass (updated test_not_supported → test_protocol_version)
• New unit tests for web3_sha3, web3_clientVersion, DebugError variants
• Clippy clean (--all-features --all-targets)
• Manual testing with Blockscout/Routescan against a running node

Review Fixes

• Replace EvmHalt with Internal for task panic/cancellation in all await_handler! sites
• Replace EvmHalt with Internal for resolve_evm_block error mapping in debug_traceCall
• Use unwrap_or_default() for optional tracer options per Geth spec (all 4 handlers)
• Change pub(super) to pub(crate) on all debug handler functions
• Replace use super::* glob import with explicit imports in web3 tests
• Remove accidentally committed planning/spec documents

Reviewed and updated by Claude Code.

🤖 Generated with Claude Code

[prestwich]

[Claude Code]

Code review

Found 1 issue:

1. Planning/spec documents appear to be committed by mistake — docs/superpowers/plans/2026-03-25-parity-trace-namespace.md and docs/superpowers/specs/2026-03-25-parity-trace-namespace-design.md. This was also flagged in PR feat: handle reorgs in get_filter_changes with reorg watermark #98 for similar files.

node-components/docs/superpowers/plans/2026-03-25-parity-trace-namespace.md

Lines 1 to 5 in c0379af

	# Parity `trace_` Namespace Implementation Plan
	> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
	**Goal:** Add a Parity/OpenEthereum `trace_` JSON-RPC namespace (9 methods) to signet-rpc for Blockscout and general tooling compatibility.

node-components/docs/superpowers/specs/2026-03-25-parity-trace-namespace-design.md

Lines 1 to 5 in c0379af

	# Parity `trace_` Namespace
	Add the Parity/OpenEthereum `trace_` JSON-RPC namespace to signet-rpc for
	Blockscout and general tooling compatibility. Driven by ENG-1064 and ENG-1065.

Additionally, several lower-confidence findings were identified (not posted here as they scored below threshold): pub(super) on new handlers (CLAUDE.md violation), opts.ok_or() instead of unwrap_or_default() (spec compliance), and EvmHalt misuse for task panics (regression from afe39f5 fix). These may warrant attention during triage.

🤖 Generated with Claude Code

_{- If this code review was useful, please react with 👍. Otherwise, react with 👎.}