Etherscan Flow — Transaction and Business Flow Tracer

Turn a seed transaction hash, wallet/contract address, or resolvable business/entity scope into an Etherscan Flow Case: entities, fund flows, and a JSON payload ready to import into the Etherscan Flow canvas. Use it for any on-chain flow — a plain transfer, a token launch, a DeFi route, an NFT mint, a DAO/business income-and-spending profile — or a full scam/hack investigation (victim → attacker → laundering → CEX). Scam-tracing is one use case, not the only one.

Hard rules (non-negotiable — apply on every run, on every platform)

First principle — grounded or nothing. Every address, amount, token, and txhash in the output must come from a live Etherscan API response fetched in this run. A business/entity prompt may start from a human name such as "ENS DAO", but that name is only a scope hypothesis: before writing a case, resolve it to verified 0x... addresses from user-provided addresses, API-resolved ENS names, or a maintained known-entity scope table in this skill. If you cannot reach the API (no CLI/MCP/key resolved, network blocked), or the entity cannot be resolved to at least one verified address, produce no case: output a single line asking for a real address/entity scope or a working API key, and write no file. There is no offline, educational, or illustrative mode — a plausible-looking case built from memory is this skill's worst possible failure. Rules 12 and 13 make this concrete.