Aggregation software like Koinly, CoinTracking, and TokenTax works reasonably well for simple portfolios. It fails in predictable ways when your activity involves bridging, wrapping, LP deposits, multi-chain wallets, or any transaction where the software can’t determine whether two events are the same asset moving or two separate taxable events. This post documents the six most common failure modes, explains the mechanism behind each error, and provides the manual reconciliation steps to correct the output.
In this post
- 1. The fundamental problem: aggregation software treats every transfer as a potential disposal
- 2. Trap 1: Cross-chain bridges creating phantom taxable disposals
- 3. Trap 2: Wrapped token events (wETH, stETH, cbBTC) double-counted as sales
- 4. Trap 3: LP deposits and withdrawals misclassified as disposals
- 5. Traps 4–6: Duplicate imports, missing cost basis on migrated assets, incorrect FMV sourcing
- 6. The manual override workflow: when to distrust the software and how to rebuild
1. The fundamental problem: aggregation software treats every transfer as a potential disposal
Aggregation software like Koinly, CoinTracking, and TokenTax works reasonably well for simple portfolios. It fails in predictable ways when your activity involves bridging, wrapping, LP deposits, multi-chain wallets, or any transaction where the software can’t determine whether two events are the same asset moving or two separate taxable events. This post documents the six most common failure modes, explains the mechanism behind each error, and provides the manual reconciliation steps to correct the output.
This section walks through the practical details for crypto holders, traders, and operators. In an engagement, this is the work product Chainblock Financial produces: documented methodology, citation to authority where it exists, and explicit identification of open questions where it doesn’t.
Key considerations
- The specific rule, regulation, or guidance that applies — with citation.
- Where the guidance is silent and a defensible position has to be taken.
- What documentation you need to preserve to support the position at audit.
- How to record the decision in your subledger so future preparers can follow it.
For most clients, this category of decision appears multiple times in a single year. Getting the methodology right once — and applying it consistently — is what distinguishes a defensible return from a guess. This is the work we do every quarter on a Subledger engagement; it is the work we re-do under engagement when a prior preparer left it undocumented.
2. Trap 1: Cross-chain bridges creating phantom taxable disposals
Aggregation software like Koinly, CoinTracking, and TokenTax works reasonably well for simple portfolios. It fails in predictable ways when your activity involves bridging, wrapping, LP deposits, multi-chain wallets, or any transaction where the software can’t determine whether two events are the same asset moving or two separate taxable events. This post documents the six most common failure modes, explains the mechanism behind each error, and provides the manual reconciliation steps to correct the output.
This section walks through the practical details for crypto holders, traders, and operators. In an engagement, this is the work product Chainblock Financial produces: documented methodology, citation to authority where it exists, and explicit identification of open questions where it doesn’t.
Key considerations
- The specific rule, regulation, or guidance that applies — with citation.
- Where the guidance is silent and a defensible position has to be taken.
- What documentation you need to preserve to support the position at audit.
- How to record the decision in your subledger so future preparers can follow it.
For most clients, this category of decision appears multiple times in a single year. Getting the methodology right once — and applying it consistently — is what distinguishes a defensible return from a guess. This is the work we do every quarter on a Subledger engagement; it is the work we re-do under engagement when a prior preparer left it undocumented.
3. Trap 2: Wrapped token events (wETH, stETH, cbBTC) double-counted as sales
Aggregation software like Koinly, CoinTracking, and TokenTax works reasonably well for simple portfolios. It fails in predictable ways when your activity involves bridging, wrapping, LP deposits, multi-chain wallets, or any transaction where the software can’t determine whether two events are the same asset moving or two separate taxable events. This post documents the six most common failure modes, explains the mechanism behind each error, and provides the manual reconciliation steps to correct the output.
This section walks through the practical details for crypto holders, traders, and operators. In an engagement, this is the work product Chainblock Financial produces: documented methodology, citation to authority where it exists, and explicit identification of open questions where it doesn’t.
Key considerations
- The specific rule, regulation, or guidance that applies — with citation.
- Where the guidance is silent and a defensible position has to be taken.
- What documentation you need to preserve to support the position at audit.
- How to record the decision in your subledger so future preparers can follow it.
For most clients, this category of decision appears multiple times in a single year. Getting the methodology right once — and applying it consistently — is what distinguishes a defensible return from a guess. This is the work we do every quarter on a Subledger engagement; it is the work we re-do under engagement when a prior preparer left it undocumented.
4. Trap 3: LP deposits and withdrawals misclassified as disposals
Aggregation software like Koinly, CoinTracking, and TokenTax works reasonably well for simple portfolios. It fails in predictable ways when your activity involves bridging, wrapping, LP deposits, multi-chain wallets, or any transaction where the software can’t determine whether two events are the same asset moving or two separate taxable events. This post documents the six most common failure modes, explains the mechanism behind each error, and provides the manual reconciliation steps to correct the output.
This section walks through the practical details for crypto holders, traders, and operators. In an engagement, this is the work product Chainblock Financial produces: documented methodology, citation to authority where it exists, and explicit identification of open questions where it doesn’t.
Key considerations
- The specific rule, regulation, or guidance that applies — with citation.
- Where the guidance is silent and a defensible position has to be taken.
- What documentation you need to preserve to support the position at audit.
- How to record the decision in your subledger so future preparers can follow it.
For most clients, this category of decision appears multiple times in a single year. Getting the methodology right once — and applying it consistently — is what distinguishes a defensible return from a guess. This is the work we do every quarter on a Subledger engagement; it is the work we re-do under engagement when a prior preparer left it undocumented.
5. Traps 4–6: Duplicate imports, missing cost basis on migrated assets, incorrect FMV sourcing
Aggregation software like Koinly, CoinTracking, and TokenTax works reasonably well for simple portfolios. It fails in predictable ways when your activity involves bridging, wrapping, LP deposits, multi-chain wallets, or any transaction where the software can’t determine whether two events are the same asset moving or two separate taxable events. This post documents the six most common failure modes, explains the mechanism behind each error, and provides the manual reconciliation steps to correct the output.
This section walks through the practical details for crypto holders, traders, and operators. In an engagement, this is the work product Chainblock Financial produces: documented methodology, citation to authority where it exists, and explicit identification of open questions where it doesn’t.
Key considerations
- The specific rule, regulation, or guidance that applies — with citation.
- Where the guidance is silent and a defensible position has to be taken.
- What documentation you need to preserve to support the position at audit.
- How to record the decision in your subledger so future preparers can follow it.
For most clients, this category of decision appears multiple times in a single year. Getting the methodology right once — and applying it consistently — is what distinguishes a defensible return from a guess. This is the work we do every quarter on a Subledger engagement; it is the work we re-do under engagement when a prior preparer left it undocumented.
6. The manual override workflow: when to distrust the software and how to rebuild
Aggregation software like Koinly, CoinTracking, and TokenTax works reasonably well for simple portfolios. It fails in predictable ways when your activity involves bridging, wrapping, LP deposits, multi-chain wallets, or any transaction where the software can’t determine whether two events are the same asset moving or two separate taxable events. This post documents the six most common failure modes, explains the mechanism behind each error, and provides the manual reconciliation steps to correct the output.
This section walks through the practical details for crypto holders, traders, and operators. In an engagement, this is the work product Chainblock Financial produces: documented methodology, citation to authority where it exists, and explicit identification of open questions where it doesn’t.
Key considerations
- The specific rule, regulation, or guidance that applies — with citation.
- Where the guidance is silent and a defensible position has to be taken.
- What documentation you need to preserve to support the position at audit.
- How to record the decision in your subledger so future preparers can follow it.
For most clients, this category of decision appears multiple times in a single year. Getting the methodology right once — and applying it consistently — is what distinguishes a defensible return from a guess. This is the work we do every quarter on a Subledger engagement; it is the work we re-do under engagement when a prior preparer left it undocumented.
This is the work we do.
Every Chainblock engagement applies this methodology to your actual transactions, your actual entity structure, and your actual exposure. If you’d rather have it done than read about how it’s done, schedule a 30-minute intake call.
Schedule a call