One economic event — 9 routing legs collapsed, no phantom token exposure.
Aggregator swaps
Aggregator swap accounting — one conversion, not a dozen phantom holdings.
One swap through 1inch, 0x, or Uniswap's router can emit a dozen ERC-20 Transfer logs, routed through pools and tokens you never held for more than a single block. A tool that reads the logs literally books each leg as a holding you bought and sold — inventing assets, counterparties, and gross volume. Intentio collapses the routing noise into the one economic event: the conversion you actually made.
The problem
Routing noise looks exactly like holdings.
An aggregator splits your order across venues for the best price, so the on-chain trace is a fan-out of intermediate transfers. A simple USDT → USDC rotation can surface as 11 Transfer logs; a crvUSD → WBTC trade as 7. Read literally, those intermediate tokens become positions on your books that you appear to have acquired and disposed of in seconds — padding gross volume, fabricating tiny gains and losses, and burying the single trade that actually happened.
What Intentio resolves
The one conversion, with the market as counterparty.
When the transaction goes through a known router — 1inch v6, 0x ExchangeProxy, or Uniswap UniversalRouter — and the transfers net to exactly one token out and one token in for your wallet, Intentio books a single swap: what you sent, what you received, the venue, and how many routing legs it collapsed. No phantom token exposure, no inflated turnover — just the trade.
Real transactions
Verify it on real mainnet swaps.
Not mockups — real Ethereum mainnet transactions run through the same live engine the demo serves (both happen to route via 1inch v6). Open them on Etherscan and count the Transfer logs Intentio collapses into one conversion.
One economic event — 5 routing legs collapsed, no phantom token exposure.
Where the line is
It gets the trade right; you keep the policy calls.
Intentio recovers the conversion and clean, categorized rows. How realized gain or loss is recognized, which cost-basis method applies, and any jurisdiction-specific treatment are policy and tax decisions you keep. It's the evidence and normalization layer, not your accounting brain.
Coverage today is the routers above. A swap through an unlisted aggregator, or a transaction whose transfers don't net to a clean one-in / one-out, isn't force-fit — it abstains, with a reason, rather than mis-book. More routers are next.
The handoff
Into the accounting tool you already use.
The resolved row exports as a standard CSV / journal, ready to review and upload to your accounting service (tool-specific import profiles as we go). It's read-only: public addresses only, no wallet connect, no signing, no custody.