Skip to content
Finality

Crypto protocol and market news

DEX swap tax records: how to build a defensible ledger

How to record DEX swaps for crypto taxes: treat each trade as a disposal and acquisition, price both legs at the timestamp, and keep a row your accountant can verify.

The Finality Desk4 min read#e8077b

DEX swap tax records: how to build a defensible ledger

A complete DEX swap ledger records each trade as a disposal of the token sent and an acquisition of the token received, with both legs valued in fiat at the trade time. The IRS and HMRC generally treat crypto-to-crypto exchanges as disposals, so a swap can create a taxable gain or loss even when no fiat currency enters the wallet.

A token swap creates a disposal and an acquisition

For a trade of 1 ETH for USDC on SyncSwap, record the ETH as disposed of at its fiat value when the swap occurred. Record the USDC received as an acquisition with that same fiat value as its cost basis, subject to the valuation method and rules that apply in your jurisdiction.

The transaction is on-chain: the swap sends one token and returns another. To turn it into a tax record, pull the transaction data from a block explorer, value the legs in fiat at the transaction timestamp, then match the ETH disposed of to its cost basis lot. The resulting row carries the proceeds, basis and gain or loss.

The gain or loss is the fiat value of the disposal minus the cost basis of the token disposed of, using the lot method permitted where you file. In the example, compare the ETH’s value at the swap with the basis of the particular ETH lot or lots assigned to that disposal. The received USDC starts a new holding with its acquisition value as cost basis; it does not inherit the original ETH basis.

A common mistake is to treat a token-to-token trade as a transfer because the wallet received crypto instead of cash. An active trader who swaps ETH for USDC and records only the new USDC balance may expect tax to arise only when the USDC is later sold. The ETH disposal is already a separate event under the general US and UK treatment, and omitting it leaves the ledger without the proceeds or realized gain calculation.

Each ledger row needs transaction data and timestamped values

Each swap row needs the UTC timestamp, network, transaction hash, token contract addresses, amounts in and out, fiat value, and gas fee. The explorer supplies the on-chain identifiers, timestamp, token amounts and gas fee; the fiat values require pricing the trade at its timestamp. Keep the transaction hash as the link between the tax record and the underlying on-chain event.

Record the chain as well as the token contracts. A ticker alone may not uniquely identify an asset, while contract addresses identify the tokens in the transaction. For a SyncSwap trade on zkSync Era, retain the network name and both token contracts alongside the amounts. These fields make it possible for an accountant or tax tool to distinguish the swap legs and trace the row back to the explorer record.

Explorer timestamps are in UTC. Convert them consistently to the time basis used for your tax records, because a trade late on December 31 in UTC may fall on a different local date and, near the year boundary, into a different tax year. Keep the original UTC timestamp even when you also record a converted time. That preserves the source value and makes the conversion auditable.

Wallet history alone may show token movements without the fiat values needed for a gain calculation. Export or copy the explorer data for each swap, then price both legs at the transaction timestamp using a consistent, supportable source. Save the pricing source and any conversion calculation with the ledger so the valuation can be reproduced later.

When reconciling a SyncSwap row with trades on another venue, preserve the chain, token contracts and transaction hash before comparing records. The syncswap vs mute comparison is useful only when the two entries refer to the same kind of trade and their underlying transaction details are clear.

Gas treatment depends on jurisdiction and the transaction’s context. In the US, gas can affect basis or proceeds; check the applicable rules before deducting it separately, since a separate deduction could misstate the result. Record the fee and its asset in the ledger even when you have not yet determined its tax treatment.

Related questions

Is adding liquidity to a DEX pool a taxable event? It can involve different tax treatment from a simple token swap, and the answer depends on jurisdiction and the exact pool transaction. Record the assets contributed, any tokens received, timestamp, network, contracts and gas so the event can be reviewed under the relevant local rules.

Is wrapping ETH into WETH taxable? Treatment can vary by jurisdiction and the details of the transaction. Keep the transaction data and values, and confirm the local rule before treating a wrap as either a taxable disposal or a non-taxable conversion.