We’ve completely redesigned the Italian tax report to make it clearer, more structured, and easier to use.

This update makes it significantly easier to understand and work with your crypto tax data in Italy.

Starting in 2025 (reporting in 2026), US custodial crypto brokers (e.g. Coinbase) are required to report transactions directly to the IRS via Form 1099-DA.

During the transition phase:

We’ve therefor we introduced a new Reconciliation Page:

For Custodial US brokers (1099-DA) → Reconciliation workflow applies

For Non-custodial wallets & foreign exchanges → Form 8949 is still pre-filled as before

The Stellar (XLM) integration now supports the import of Stellar-based tokens, as well as associated transactions and balances.

> DeFi import solution for Stellar (XLM)-based applications (dApps)

​

We are pleased to introduce the following new transaction labels:

Transactions of the following blockchain can now be automatically imported into your Blockpit account:

🔗 Linea (LINEA) Blockchain added 🔗

Swissborg is now supported as a CSV integration in Blockpit. This allows the manual upload of the following data:

✅ Deposits & Withdrawals
✅ Fees
​✅ Trades (incl. Auto-Invest & Bundles)
✅ Converts

✅ Cashback
✅ Swissborg Card Transactions
​​✅ Earn: Rewards & Distributions (Staking, Lending, Airdrops, Bounties, Hard Forks)

> How to import data via Swissborg CSV file?

Bitunix is now supported as a CSV integration in Blockpit. This allows the manual upload of the following data:

✅ Deposits & Withdrawals
​✅ Spot Market Trades
​✅ Fees

✅ Converts
✅ Card/P2P/Third-Party Purchase
✅ Copy Trading

✅ Cashbacks
✅ Dual Investment
​✅ Futures Trading P&L (Profit, Loss, Fee, Funding)

✅ Earn: Rewards & Distributions (incl. Rebates, Bonuses)

> How to import data via Bitunix CSV file?

It is now possible to upload the new CSV/Excel format (V3) provided by BingX into your BingX integration. This new format is now based on two separate CSV/Excel files (Transaction_History & Order_History) and is an adaptation of the old format (V2). Maintenance of the old format has therefore been discontinued.

Please note that Wealth (Earn, Loan, Dual Invest), RewardsHub, and LaunchHub (Launchpool, Launchpad, Xpool, Airdrops) transactions are currently no longer supported in this new format. Combining the new and old formats may therefore result in a discrepancy in balances.

> How to import data via BingX CSV/Excel file?

A new full update of our TRON (TRX) integration has been released.

As part of the update, many challenges in connection with incorrectly imported transactions and balances have been successfully addressed and resolved.

✅ All native transactions (Deposits, Withdrawals, Bridging, Trades, etc.)
​​​✅ All Tokens (TRC10 + TRC20) & NFTs (TRC721 + TRC1155)
​​​✅ All synced balances

✅ JustLend (incl. energy rentals)

✅ Sunswap (all versions)
✅ SocialSwap

✅ JustSwap
​✅​ + Many more dApps

> DeFi import solution for Tron (TRX) based applications (dApps)

Product updates provided by Blockpit have no direct effect on existing transaction data in your Integration (precautionary measure to avoid changing existing transaction histories through automatic product updates), so creating a new Integration could bring it up to date and solve your problem (Tips) already.
​
Therefore you can temporarily create a second Integration to be able to compare the new and old Integration. Then delete the Integration that you do not want to keep.
​
​> How to create, sync, edit, convert, group, delete and deactivate Integrations?
​

Alternatively, it is possible to re-synchronize missing or incorrectly imported transactions. Please note that re-synchronization of existing Bitget Integrations due to a new Bitget ID structure will most likely cause duplicate transactions. In order not to damage existing transaction histories and to avoid new duplicate transactions, we recommend the following article:
​
​> How can to synchronize integrations or re-synchronize missing/incorrectly imported transactions?
​

Transactions of the following blockchain can now be automatically imported into your Blockpit account:

🔗 Bittensor (TAO) Blockchain added 🔗

Our Bitpanda integration has received a new update, which was rolled out on Dec. 4, 2025, for existing and new Bitpanda integrations.
​

This update is based on the new Bitpanda margin trading product and the associated subwallet structure:

Due to the high complexity of the margin trading product (which makes manual data entry very difficult), all associated automatically imported transactions in existing Bitpanda integrations were specifically updated and thus retroactively updated. Further manual adjustments should therefore not be necessary.

Important note: Balances that are “locked in margin trading” will temporarily not be displayed in the synced balance of your integration. The resulting “Tip: Mismatched Balance” can be ignored. Loaned assets from margin trading may also cause temporary increases in value in your portfolio graph, which will be offset again after the position is closed.

For more details on handling the new Bitpanda integration, please refer to our guide:

> How to import data via Bitpanda OAuth connection or API key?

Transactions of the following blockchain can now be automatically imported into your Blockpit account:

🔗 Unichain (UNI) Blockchain added 🔗

Transactions of the following blockchain can now be automatically imported into your Blockpit account:

🔗 HyperEVM Blockchain added 🔗

We’ve simplified the sync process: From now on, you can refresh each integration directly using the new Individual Sync button—no need to navigate through the submenu.
​

> How to synchronize integrations or re-synchronize missing/incorrectly imported transactions?

Transactions of the following blockchain can now be automatically imported into your Blockpit account:

🔗 ZORA Blockchain added 🔗

You can now upload MEXC transactions directly via CSV/Excel file into existing MEXC exchange integrations. It’s also possible to create a new MEXC integration by initially uploading a CSV/Excel file and later converting it into an API integration.

Before uploading your MEXC CSV/Excel file, please make sure that any already imported transactions are removed from the file to avoid creating duplicates when re-uploading.

For more details on how to use the new MEXC CSV/Excel upload feature, see our guide:
​
​> How do I import data using the MEXC Global API key or CSV file?

We are pleased to introduce two new transaction labels "Receive Loan" and "Repay Loan".

The Transaction-Label Receive Loan is used to record the incoming Asset/Loans that are meant to be considered as tax neutral. Receive Loan transactions do not trigger taxable gains or losses and will be rated at market value at the time of inflow.

> Transaction Label "Receive Loan"

The transaction label Repay Loan is used to record outgoing assets or loan repayments that are to be sold at market value at the time of the outflow. Please note that this label is classified differently in Austria and therefore does not result in a taxable outflow, but rather a tax-neutral outflow.

> Transaktions-Label "Repay Loan"

A new full update of our KuCoin integration has been released.

As part of the update, many challenges in connection with incorrectly imported transactions have been successfully addressed and resolved.

In addition, transaction data dating back up to 2 years can now be imported via API (previously there was a restriction of 3 months).

Newly supported products:

> How to import data via KuCoin API key?

Product updates provided by Blockpit have no direct effect on existing transaction data in your Integration (precautionary measure to avoid changing existing transaction histories through automatic product updates), so creating a new Integration could bring it up to date and solve your problem (Tips) already.
​
Therefore you can temporarily create a second Integration to be able to compare the new and old Integration. Then delete the Integration that you do not want to keep.
​
​> How to create, sync, edit, convert, group, delete and deactivate Integrations?
​

Alternatively, it is possible to re-synchronize missing or incorrectly imported transactions. Please note that re-synchronization of existing Bitget Integrations due to a new Bitget ID structure will most likely cause duplicate transactions. In order not to damage existing transaction histories and to avoid new duplicate transactions, we recommend the following article:
​
​> How can to synchronize integrations or re-synchronize missing/incorrectly imported transactions?
​

Tax reports and advanced Blockpit features are now available independently of each other.

> The new Blockpit pricing model

The new “Large” transaction package with up to 3000 transactions is now available.

Our new Blockpit Plus subscription gives you access to all of Blockpit's advanced features:

> More information about Blockpit Plus
​

Please note that existing 2025 licenses and associated features will remain active until the end of the year during the transition to the new pricing model.
​

Thank you for your trust!

Team Blockpit