revert.wtf Catalog Research Skillv0.1.0

A developer integrates a newly launched EVM-compatible chain into the revert.wtf catalog, populating shards with chain-specific custom errors from primary sources. They run the enrichment script, validate entries, and ensure selectors match live contracts.

An analyst reviews existing catalog entries to mark protocols as legacy, sunsetting, or renamed based on official announcements and live contract status. Historical entries are preserved for integration usefulness while lifecycle metadata is updated in sources.ts.

A protocol team adds error definitions for x402 payment flows across multiple providers, hand-authoring entries because the errors are not Solidity custom errors. They reference provider API docs and ensure nextSteps guide wallets on retry logic.

A catalog maintainer performs a broad coverage pass for a DeFi ecosystem (e.g., a lending protocol suite), gathering custom errors from verified repositories and generating shards. They run duplicate audits and synchronize generated JSON with source files.

An engineer adds error definitions for multiple blockchain explorer APIs, ensuring entries are integration-useful and specific about retry behavior. They verify current API status and avoid false-positive substring patterns.

The catalog is maintained as an open-source project with contributions from the community and sponsored by ecosystem grants. Revenue is indirectly generated through consulting, support, or premium hosted services.

A commercial entity offers a hosted version of the catalog with advanced search, analytics, and API access on a subscription basis. Free tiers include basic catalog access, while paid tiers provide enrichment and validation automation.

The catalog powers an API that resolves EVM error selectors and provides actionable nextSteps for wallets, dApps, and support consoles. Usage-based pricing is charged per API call or per resolved error.