Unlabeled Transactions
in Blockpit?

Blockpit lists them as unlabeled, the tip filter says “Missing Label (In/Out)”. TX-Partner assigns them correctly.

Book a consultation

30 minutes · Consultation and quote free

9years Together in crypto accounting
Fixed price Cost certainty upfront
Independent Not tied to any tool
Robert Thorn Johannes Anderl

Robert & Johannes · personally review your data

Common Causes

The 3 Most Common Causes of Unlabeled Transactions

Blockpit recognises standard trades reliably; with DeFi, bridges and unknown tokens the automatic recognition reaches its limit.

01_DEFI_CONTRACTS

DeFi smart contracts

Lending, yield farming and liquidity pools are not read out in full by Blockpit. The contract call gets imported but not classified.

02_BRIDGE_TRANSFERS

Bridges and cross-chain transfers

A transfer is only recognised when outflow and inflow are both in the data. With bridges one side is often missing or carries a different token name.

03_UNKNOWN_TOKENS

Unknown tokens and airdrops

New tokens, airdrops and project-specific rewards are not in Blockpit’s database and stay unlabeled. They still count in the calculation.

What that means

Where a missing label hits the tax report

Crypto tax tools calculate with what is classified. If an entry stays unlabeled, Blockpit treats the outflow as a sale and gives the inflow a cost basis of zero.

Cost basis of zero

Without a matching purchase, Blockpit sets the cost basis to zero. The full proceeds become a gain, even when none was made.

The acquisition date goes with it

The acquisition date disappears along with the cost basis. The 12-month holding period can then no longer be evidenced.

Usually a symptom, not a labelling issue

In more than half of the cases a data gap sits behind the hint: a counter-entry never imported, a missing history, a partly synced wallet.

The expensive shortcut

Linking transfers by gut feeling or dumping everything unclear into one category: the hint is gone, the cost basis stays wrong and travels into every following year.

What TX-Partner makes of it

Cause first, label second.

01

Transaction verified

TX-Partner looks at the entry in the block explorer and reconstructs what actually happened, before any label is set.

02

Counterpart added

If the counter-entry is missing, the source gets added instead of a substitute booked. Only then is a transfer recognisable as one.

03

Recalculated

Blockpit updates nothing by itself. After every change TX-Partner triggers the recalculation before the report is produced.

Ready?

Fix unlabeled transactionsfix.for good.

30 minutes that make the difference.

Book a consultation 30 minutes · Consultation and quote free

If we are not the right fit for your case, we will say so in the call.

Frequently Asked Questions

What We Get Asked Most

Blockpit marks transactions as unlabeled when it cannot automatically recognize the type. This particularly affects DeFi interactions, smart contract calls, and unknown tokens. These transactions are often not correctly considered in the tax calculation.
It depends on the portfolio. With pure exchange portfolios, there are hardly any unlabeled entries. With DeFi usage, 30% and more of transactions can be affected. Each one should be correctly classified, as it can be tax-relevant.