> For the complete documentation index, see [llms.txt](https://guides.smolcompute.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.smolcompute.xyz/1/how-to/crypto-to-crypto-trades.md). # Crypto to Crypto Trades In most jurisdictions, crypto-to-crypto trades are treated as disposals. So if you buy TURBO with ETH, you trigger a taxable event on the ETH you used to purchase TURBO — as though you had first sold it for USD and then used that USD to buy TURBO. When doing crypto to crypto trades, we recommend entering two separate events in the Trade Log. Say you bought some ETH some time ago and entered that trade in the Trade Log. When you now use it to purchase TURBO, I would enter: 1. A SELL event for the amount of ETH you used to buy TURBO, using the current price of ETH. 2. A BUY event for the amount of TURBO you received for your ETH (the price of TURBO should be the USD value of the previous transaction divided by the amount of TURBO you purchased) Doing it like this ensures that your ETH balance stays accurate and that you’re logging the realized P\&L when you swapped it for TURBO. The [Formatter](/1/formatter.md) can also help you convert trades bought with ETH, BNB, SOL, and BTC into USD denominated trades. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://guides.smolcompute.xyz/1/how-to/crypto-to-crypto-trades.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.