~$ crypto-under-the-hood

# How crypto payment infrastructure actually works

~/notes / swap

How to Convert Crypto to Crypto Without Touching Fiat

The three routes between two crypto assets, what each costs, and which one to use depending on whether the assets share a chain.

Ivan Kruse · · 3 min

There are three ways to get from one crypto asset to another. Which one is correct depends almost entirely on whether the two assets live on the same chain, and the cost difference between the right choice and the wrong one can be an order of magnitude. Read against a crypto swap platform, the distinctions below stop being academic.

Route one: a swap

Send asset A, receive asset B, one quoted price. Works same-chain and cross-chain. Costs 0.3 to 1 percent all-in typically.

Use this when the assets are on different chains, when the pair is not deeply liquid, or when you do not want to think about it. It is the default for a reason.

Route two: two trades on an exchange

Sell A for a common quote asset, buy B with the proceeds. Two fees rather than one, but each fee is an exchange fee rather than a swap margin.

On a venue charging 0.1 percent, two trades cost 0.2 percent, which beats most swap quotes. This is the cheap route for liquid pairs, and it is the correct choice when you are moving meaningful size between two majors.

The catch is that both assets have to be listed on the same venue with adequate depth, and you have to actually execute two orders.

Route three: a direct pair

If the venue lists A/B directly, one trade. Cheapest of all when it exists. It usually does not exist for anything other than majors against majors.

The decision in practice

Same chain, both liquid, both listed on one venue: two trades or a direct pair. Cost around 0.2 percent.

Different chains: swap. The alternative is bridge plus two trades, which means two network fees, bridge risk, and an interval of exposure. The swap margin is cheaper than the bridge complexity for almost any size. For a business the calculation inverts, which is the gap crypto rails built for fintech companies fills.

Thin asset: swap, because routing across venues aggregates depth you cannot easily reach yourself.

What the bridge route actually costs

People underestimate this consistently, so it is worth spelling out. Moving from chain X to chain Y manually means: a transaction to approve the bridge, a transaction to deposit, waiting for the bridge, a transaction on the destination chain, and then the trade itself.

That is three to four network fees. On a busy chain those can dominate the trade entirely. Add the time during which you hold a bridged representation of the asset rather than the asset, and the bridge protocol risk that goes with it.

A cross-chain swap collapses all of that into one operation with one quote. The provider absorbs the bridging and prices it in. For any size where the network fees are not trivially small relative to the trade, this is clearly better.

Tax and record keeping

In most jurisdictions a crypto to crypto conversion is a disposal and a taxable event. That means you need, for each conversion: date and time, asset out with quantity, asset in with quantity, and the fiat value of both at the moment of the trade.

A swap gives you this in one record. Two trades give you two records that have to be matched. A bridge plus two trades gives you several records where only some are disposals and working out which is genuinely annoying.

This is a real argument for swaps that nobody mentions. The cleaner record is worth something at the end of the year.

How to compare providers

Take the same conversion to three providers, convert each quoted output into an implied rate against mid-market, and compare the percentages. Do it at the same moment, because comparing quotes taken an hour apart measures the market, not the provider.

Providers running a crypto swapping service across chains will quote without an account, which makes this comparison a five minute exercise rather than an onboarding project.

# Corrections and technical nitpicks are welcome. Send them over. They get published with the fix.

swapconversionbridging

# related notes