transaction_subtype standardises exchange transaction types

Exchanges name the same activity differently — one calls it a trade, another a swap, another a conversion — which makes tax and accounting work painful. A new transaction_subtype field normalises those names across connectors.

What you get

• transaction_subtype on Binance, Coinbase, Kraken, Crypto.com, Gemini and KuCoin
• transaction_type and misc.origin_type are unchanged — the broad type and the exchange's own raw label are both still there

Action required

None — this is additive. If you match on misc.origin_type today, the new field is likely to be the one you want instead, since it does not vary by exchange. More connectors are being added; tell us if one you use is missing a subtype.