At a glance
▸ Label: Hard Fork ▸ Direction: 📥 incoming (inflow) ▸ How the app describes it: “You received assets because of a hard fork.” ▸ Where to find it: + Transaction › Transaction Label › group Incoming ▸ Do not confuse with: Airdrop, Bounty, Gift (In), Cashback, Other Income |
The Transaction Label Hard Fork is used to record incoming assets from hard forks in your integration. If you participated in a hard fork, you will receive new coins, which are either automatically recorded in Exchange or Wallet Integrations or have to be entered manually in Manual Integrations.
The tax treatment is also described in the chapter Tax Report & Optimization.
🎓 More details on the tax implications and categorization of all transaction labels can be found in the tax results under the menu item “Reports” and in the appendix of your tax report.
How do I create a Hard Fork inflow?
1️⃣ In your Blockpit account, click the Transactions menu item.
2️⃣ Then select + Transaction.
3️⃣ Enter the date and time of the transaction.
ℹ️ For a transaction created manually directly in the web app, use your local time.
ℹ️ For a transaction imported via CSV/Excel, use the standard exchange time UTC.
4️⃣ Now select the Transaction Label Airdrop.
5️⃣ Now enter the integration, asset and amount. If you paid fees, enter them with asset and amount as well.
💡 Tip: In the asset field, enter the short name (BTC) or the long name (Bitcoin) to narrow down the list. If you cannot find your asset, this overview will help.
6️⃣ Finally, click Save to complete the process and show the transaction in the integration.
❗ If you received assets as the result of a hard fork, the inflow should be recorded in the integration that held the original asset at the time of the hard fork. If the original asset is missing at the time of the hard fork, a corresponding Tip will be displayed in your transaction list.
What happens to my balance?
How a manually created transaction affects your balance depends on the type of integration:
Integration | Effect |
Manual integration (CSV/Excel) | directly changes the displayed balance of the integration |
Automatic exchange or blockchain integration (API) | does not change the imported Synced Balance, but it does change the calculated balance and therefore your tax report |
How are fees considered for Hard Forks?
Example: Hard Fork inflow of 1 BTC with 0.0001 BTC fee.
Fees are mostly considered on the withdrawal side, but can also occur on deposits.
Fees, if paid in the incoming asset, are considered as follows:
▸ If fees are paid in the incoming asset:
Case 1: No additional fee on the deposit side.
Incoming amount: net transaction amount (amount excluding fees)
Fee paid: enter nothing or 0
Case 2: Additional fee on the deposit side.
"If the fee is paid in the incoming currency, the incoming amount must be increased by the amount of the fee. The fee is treated as a separate outflow."
Incoming amount: net transaction amount (amount excluding fees) + fee
Fee paid: enter the fee separately
Different approach of exchanges to Hard Fork?
A hard fork is generally a split of an existing blockchain (coin) into two independent blockchains (coins). This usually occurs when changes to the blockchain protocol are introduced that are not compatible with previous versions.
Hard forks take place on the blockchain itself (not on exchanges). However, exchanges must adapt to these events and may implement the technical handling of a hard fork differently depending on its outcome.
If a hard fork results in two independent assets that continue to exist, it is important to note that many newly created forked assets are not immediately supported by enough network participants (miners or validators) or may never be listed by exchanges.
If both assets continue to exist and are supported by an exchange, the technical implementation often follows a pattern similar to the following:
Example: Bitcoin Cash (BCH) hard fork on Binance (15.11 November 2018)
▸ Redistribution of BCH
▸ Redistribution of BSV
Although BCH continued to exist as a separate asset, some exchanges re-credited the BCH balance to users’ wallets as part of their internal migration. In addition, the newly created asset BSV was credited.
As a result, the transaction history may seem to show a duplicate BCH credit, even though the actual BCH holding did not increase economically.
The repeated BCH credit only serves the technical processing of the hard fork in this case and should be taken into account or excluded accordingly when creating the tax report.
This duplication must be excluded from the tax report by the user afterwards!
Blockpit does not provide tax advice. For specific legal questions, please contact a tax advisor.

