Use this when the wallet story spans chains. A single export is rarely enough if the user bridged, minted, staked, or moved assets across networks.
The useful output is not a perfect tax answer. It is an exception table: what looks complete, what looks missing, and what needs a human review.
Use this when
- The same wallet has activity across several chains.
- You need a reconciliation checklist, not only a CSV.
- An accountant or analyst needs to see where the uncertainty is.
What the workflow should produce
- Multi-chain export grouped by network.
- Exception table for missing transfers, unsupported assets, or suspicious gaps.
- Chain coverage notes and sample transaction counts.
- Questions for follow-up with the client or data provider.
Minimum setup
- Create a GoldRush / Covalent API key or bearer token.
- Check the current supported-chain documentation and whether the needed endpoint has parity on the selected chains.
- Use the multi-chain transaction endpoint as the first candidate when the goal is reconciliation, not a single-chain CSV.
Skill to package next
multi-chain-exception-table: input addresses and chains, fetch rows, group by network, compare transaction counts, and output exceptions.csv plus a short review memo.
GoldRush also documents an MCP server for Claude/Cursor-style workflows. That makes the article a good candidate for two tracks: API-key script first, MCP-assisted exploration second.
Check before trusting it
Verify current GoldRush / Covalent naming, endpoints, supported chains, limits, and pricing before a production tutorial. Keep provider data gaps separate from tax interpretation.
