DeFi Documentation
LP, Staking & Bridges
Swaps, LP positions and bridges no tool reads cleanly. TX-Partner reconstructs them on-chain.
30 minutes · Consultation and quote free
Robert & Johannes · personally review your data
Why DeFi accounting is especially complex
The on-chain data is available. The work lies in reading it correctly.
One contract, several operations
What runs bundled inside one smart contract on-chain is often read out wrongly: sometimes the trade is missing entirely, sometimes it is booked against the fee.
Only one side arrives
With bridges and aggregators the outflow is captured, the inflow is not, or carries a different token name. The report then shows a sale without proceeds.
Every chain is its own source
The same address has to be captured per chain. The “Import all wallets” function is unreliable; after every import each chain gets checked separately.
Four operations that need evidence of their own
The same on-chain operation is not self-explanatory. Its class decides what ends up in the report.
Liquidity pool
Entering against LP tokens, the running rewards and the exit are three operations. Each needs its own assignment, otherwise the cost basis of the position breaks.
Lending and staking
Deposit and repayment have to be linked, interest counts as income. On-chain staking and exchange staking that is de facto lending are treated differently.
Bridges and cross-chain swaps
Two sides, one often under a different token name. Linked as a transfer the cost basis carries over, otherwise a phantom sale appears on the source chain.
Deposits routed through a router
Deposits to perp DEXes often run through a router. On-chain only the router is visible, the venue itself emerges from the conversation.
Where an unrecognised DeFi entry hits the report
Tax tools calculate with what is classified. If an entry stays without a type, the tool treats the outflow as a sale and gives the inflow a cost basis of zero.
Cost basis of zero
Without a matching purchase the full proceeds become a gain. In Blockpit the entry then carries the Missing Label tip (formerly Unlabeled).
One operation, several failure modes
The tool reads the contract call wrongly. Sometimes the trade is missing, sometimes it is booked against the fee, sometimes one side is absent.
Wraps and mergers as two rows
Migrations and wraps sometimes land as an outflow plus an inflow instead of one trade. The receiving side then starts with a cost basis of zero.
The expensive shortcut
Dumping everything unclear into one category makes the hint disappear. The cost basis stays wrong and travels into every following year.
The operation first, the label second.
Addresses and chains collected
Every wallet address goes on the list per chain, together with every protocol used. A bulk import does not replace that.
Operations reconstructed on-chain
Every contract call is checked in the explorer and mapped the way it actually happened. If a side is missing, the source is retrieved.
Filed in the tool
The entries are brought into import format and classified. Then TX-Partner triggers the recalculation before the report is produced.
Complete DeFi history for good.
30 minutes that make the difference.
Book a consultation 30 minutes · Consultation and quote freeIf we are not the right fit for your case, we will say so in the call.
You might also like
Reconstruct Exchange History
Missing trading history from open and closed exchanges, retrieved and imported cleanly.
Learn moreReconstructing crypto records at a glance
Which data is missing, where it comes from and in which order it goes back into the tool.
To the overviewReconstruct Crypto History
The long route in detail: which source applies when, and where a reconstruction runs into its limit.
Read article