revertwtf

Run evidence-locked enrichment passes over existing revert.wtf catalog errors, preserving good entries while improving generic explanations, actions, references, and helper metadata.

Use revert.wtf safely from agents, tools, browsers, or integrations through bounded HTTP APIs, MCP tools, and lightweight package subpaths without downloading the full catalog into client bundles.

Add or update precise revert.wtf catalog entries, fixtures, source metadata, and matcher tests for one or a small set of EVM/RPC/provider/wallet/protocol errors.

Perform broader source-backed catalog enrichment for new EVM ecosystems, protocols, providers, standards, or deprecated/renamed/sunsetting coverage.

Work on the revert.wtf Next.js frontend as a distinctive error-forensics product surface, not a generic SaaS or stock brutalist page.

Maintain or use the read-only revert.wtf MCP server that exposes bounded catalog search, parser, selector lookup, AA explanations, x402 entries, and Blockscout registry tools to agents.

Modify or debug revert.wtf normalization, revert-data extraction, trace extraction, ABI decoding, catalog matching, selector lookup, or ERC-4337 decoding behavior.

Run production-readiness checks for revert.wtf packages, catalog data, MCP server, frontend, Docker/Coolify deployment, docs, and generated artifacts.