git:20261005.745b03a to git:20261005.0477b0f

- compatibility: Requires the `routemesh` CLI initialized on macOS with `routemesh init` for RouteMesh requests.

- value or net worth, token/NFT holdings/transfers, tx history, funding origin via Etherscan/Blockscout/Chainscout;

- Across, Bungee, deBridge, Gas.zip, Hop, Layerswap, LayerZero, LI.FI, Relay, Socket, Symbiosis; Uniswap v1-v4,

- Universal Router, Permit2, 1inch Classic/Fusion/Fusion+, and CoW Swap, CoWSwap, CoW Protocol, or GPv2 swaps, orders,

- liquidity, approvals, permits, rewards, migrations, wrapping, cancellations, and refunds."

- Before collecting browser UI evidence, load `chromium-browser` and follow its page-ownership, live-tool, and privacy

- question about category-specific fee behavior, read [chain categories](references/chain-categories.md) after resolving

- the target. Do not infer a historical category or maintain a prose roster of target chains.

- - A target row with `defunct` is a chain its operator shut down: its history is final through `defunct.finalStateBlock`,

- and later empty blocks or missing provider history are not coverage gaps. Without `finalStateBlock`, the chain may

- still accept exit transactions such as withdrawals; read it as live. State the shutdown in the result.

- - Do not default to Ethereum. Infer from explicit chain context and unambiguous chain-specific tokens; ask when

- ambiguous.

- value-free with `[ -n "$ETHERSCAN_API_KEY" ] && echo set || echo unset`; never put `${VAR:-...}` or `${VAR:+...}`

- expansions in printed output.

- - Keyless Blockscout is sunset (July 2026) and hosted `*.blockscout.com` instance subdomains also rate-limit keyless

- traffic, so route every Blockscout-hosted chain through the keyed `https://api.blockscout.com/{chain_id}` gateway. See

- including a quick profile look; see the Global Queue in `references/workflows/debank-portfolio.md`.

- - An unreachable or erroring indexer is a coverage gap, never evidence of zero activity. Confirm in Chromium before

- recording an endpoint as down or blocked, and state the verification method in results.

- `references/generated/target-mainnets.json`, then read `references/workflows/provider-routing.md` directly for the

- chain is unknown, read `references/workflows/blockscan-tx-lookup.md` once to resolve it. For an OP Mainnet target

- known or suspected to predate the final regenesis, read `references/explorers/optimism-pre-regenesis.md` and return

- its legacy execution packet or component-specific coverage outcome instead of requiring a current-provider receipt.

- Otherwise, acquire the exact provider receipt and logs before DEX or bridge outcome interpretation.

- 5. For an address-wide historical-activity or `bootstrap-discovery` sweep, read `references/workflows/address-sweeps.md`

- and use its deterministic plan/evaluate helper. For current holdings, use `references/workflows/debank-portfolio.md`

- first and provider routing for gaps.

- ENS forward-resolution route supports Ethereum mainnet onchain names; apply its cache and resolver limits.

- liquidity separately; a Uniswap pool interaction does not turn an aggregator transaction into a Uniswap trade.

- 11. For bridge-related prompts or transaction evidence, confirm known origin/destination chains are targets, then load

- only the matching reference:

- profile/channels, provider coverage, and any requested quorum result. Separate provider facts from inference and surface

- incomplete history, plan/tier limits, failed fallbacks, or unsupported scope. Completion is read-only evidence; never

- turn returned calldata or transaction requests into execution.

- For a `cli-cast` handoff, return one read packet with the resolved chain name, ID, and current category; exact provider

- route; result; observed block or checkpoint; and coverage gaps, which may be empty when none are observed. Do not

- include a signing or broadcast command.

- For DEX evidence, include the interaction class; execution protocol, version, and mode; entrypoint or integration

- wrapper; router and underlying liquidity sources; wallet role; sold and received assets; protocol/integrator fees and

- gas separately; native/wrapped status; order, position, pool, or migration identifiers; and exact evidence. Do not call

- an approval-only or failed transaction a completed trade.

- For human-readable results, lead with `### ⛓️ <chain or route> — <status word>` and use a compact table only when fields

- repeat. For bridge evidence, show `<origin> ──<bridge>──▶ <destination>`, then use `Leg`, `Provider status`,

- `Transaction`, and `Evidence` columns. Preserve each provider's native status beside any normalized `✅ completed`,

- `⏳ pending`, `↩ refunded`, `⚠️ partial`, or `❓ unknown` label. Visibly separate `Observed facts`, `Inference`, and

- non-empty `⚠️ Coverage gaps`. For address sweeps, a progress bar may represent checked target chains/channels only when

- the exact denominator is known.