This page explains how to use our DeFi (Decentralized Finance) functions.
Support for Sui has started (2025/11/6).
For more details, please refer to the news page linked here.
Sui transactions can be quite complex, so we continuously update our system to support a wide range of protocols. However, for protocols that we have not yet fully implemented, there may be cases where the quantities do not match.
If you notice any discrepancies in your calculation results, please contact the cryptact Support Desk.
We respond to inquiries in the order they are received, but please note that during the busy season (December to March), it may take longer for us to reply.
cryptact supports blockchains, not specific wallets.
Rather than supporting individual wallets, we operate on a blockchain basis. This means that the ability to automatically reflect transactions depends on whether the blockchain used by your wallet is among the blockchains supported by cryptact.
If your blockchain is not supported, you may need to upload your transaction history using a Custom file.
Contents
1.1 cryptact's supported blockchains
1.3 Updates of Our Supported Blockchains
3. What are "Unclassified (To classify)" DeFi transactions
4. How to address "Unclassified (To classify)" DeFi transactions
5. How to edit "classified" DeFi transactions
1. What are DeFi functions
When you add a wallet address, within cryptact's supported blockchain, it will sync the transaction history. The transactions that the system can identify will be automatically recognized, their details will be reflected, and profit and loss calculations will be performed automatically. In contrast, transactions that cannot be automatically identified, and non-DeFi deposit and withdrawal transactions, will be categorized as "Unclassified (To Classify)," and manual classification will be required.
Please note:
It's important to mention that this does not provide 100% automatic support for your DeFi transactions. For transactions that cannot be automatically identified, you will need to manually select the transaction type. However, this should significantly reduce the workload of identifying transactions from deposit and withdrawal records and documenting them in custom files.
1.1 Our supported Blockchains
- Abstract
- Arbitrum
- Astar *We have started to support EVM wallet for Astar.
- Avalanche
- Base
- Berachain
- Bitcoin
- BNB Smart Chain
- Blast
- Celo
- Ethereum
- Flare
- Gnosis
- HyperEVM
- Linea
- Mantle
- Optimism
- Oasys
- Plasma
- Polygon
- Scroll
- Sei *We have started to support Cosmos and EVM.
- Solana
- Soneium
- Sonic
- Sui
- Unichain
- World
- ZKsync Era
We also plan to gradually introduce support for other Blockchains:
If you have already uploaded your transaction history using a custom file because the blockchain was not yet supported by cryptact, but the blockchain later becomes supported, you can use the "Data Locking" feature to lock in their transaction data up to a specific fiscal year-end. This allows you to synchronize only transactions from that point onward via their wallet address.
1.2 DeFi Coverage Test
Check your wallet from this link
You can assess the actual level of manual intervention required before purchasing a plan, ensuring confirmation of the auto-recognition rate for DeFi transactions.
1.3 Updates of Our Supported Blockchains
-
Added Support for Sui on 6th Nov 2025!
We now added support for the above chains. See this news page for details. -
Added Support for Unichain、Sonic、Sei EVM on 11th Sep 2025!
We now added support for the above chains. See this news page for details. -
Added Support for Sei on 29th July 2025!
We now added support for the Sei chain.
-
Added Support for Solana on 18th Feb 2025!
We now support the Solana blockchain. Please see this news page for more details. *If an "Unclassified" transaction on the Solana chain is not resolved even after selecting the suggested transaction type on cryptact, or if a swap transaction does not allow the selection of "Swap/NFT Trade" and remains as "Unclassified," please send the transaction hash to our support team. We will review the details accordingly.
We have confirmed that airdrop or bonus reward histories may not appear during the initial synchronization on the Solana chain. If this happens, please try resynchronizing to see if the history is properly reflected.
-
Started Support for OpenSea for NFT Transactions (as of August 18, 2023)
We have started to support the history of purchasing/selling multiple NFTs in a single payment as of March 4, 2024. However, as there are exceptional cases depending on the transaction, we plan to check and improve on a case-by-case basis if you contact support when an issue arises. For more details, please refer to DeFi: How to handle multiple NFTs purchased/sold in a single transaction in the DeFi transaction.
Others
- Please note that for some transactions, detailed information may not be displayed even if you click the URL of the corresponding transaction hash. Thank you for your understanding.
- We have confirmed an issue where synchronization may fail due to delays in API distribution for Soneium and Flare. However, we have confirmed that synchronization can be completed successfully by trying again after some time. We apologize for the inconvenience and kindly ask you to try synchronizing again after waiting for a while. (Oct 30, 2025)
- We have confirmed that there is a delay in reflecting some histories across multiple chains. As it is expected to take some time for the histories to be reflected, we apologize for any inconvenience this may cause and kindly ask you to try synchronizing after a few days. If it takes more than 5 days for the histories to be reflected, please contact our support desk. (May 7, 2024)
- Regarding the history of NFT exchange, there are no clear rules for calculating profit and losses, so automatic support is not provided.
-
Currently order book based decentralized exchanges like dYdX, and NFT related transactions are not fully supported. Please select "Fee Only" as a transaction type to exclude the transaction and then add transactions by custom file manually.
- Also, as of 16th Mar 2023, we have temporarily suspended support for ERC1155 at Avalanche.
- We've identified an issue where certain Avalanche transaction history information is not available through the API. Our development team is working on a solution, but we can't provide a specific update schedule. If urgent, consider manually editing the transaction history using convert function or excluding it in the DeFi overview and adding necessary details using a custom file.
End of Support Notice
We ended our support for Polygon zkEVM in cryptact’s DeFi functionality on March 17, 2026.
We ended our support for Fantom in cryptact’s DeFi functionality on March 1, 2026.
We ended our support for DeFiVerse in cryptact’s DeFi functionality on October 20, 2025.
- Due to the planned termination of TCG Verse, cryptact's DeFi functionality support will be discontinued from 30th, Sep 2025, at 12:00 (JST).
- Due to the planned termination of DM2 Verse, cryptact's DeFi functionality support will be discontinued according to the following schedule:
End of Support Date: February 12, 2025, at 9:00 AM (JST)
Supported Transactions: Transactions that occurred by December 31, 2024, at 11:59 PM (JST)
- Due to the planned termination of Astar zkEVM, cryptact's DeFi functionality support will be discontinued according to the following schedule:
End of Support Date: April 1, 2025, at 9:30 AM (UTC)
Supported Transactions: Transactions that occurred by above date and time - As of May 6, 2025, cryptact has discontinued DeFi functionality support for Chain Verse, GESO Verse, Saakuru Verse, and Yooldo Verse.
2. Add your wallet address
Let's log in to cryptact and try out the functionality in practice!
First, please add your wallet address that you use for your DeFi. Once this is done, cryptact automatically fetches all historical transactions associated with it. For more details on how to register your wallet address, please refer to this link.
After adding the wallet address, please check your DeFi transactions on the DeFi Transactions page.
You can switch between chain families to view transactions for different chains.
3. What are "Unclassified (To Classify)" DeFi transactions
The system analyzes the transactions associated with the wallet address and attempts to identify the associated smart contracts. The system then attempts to determine the background for each transaction. If it can recognize the transaction type, it updates the transaction detail and run the PNL calculation for it automatically. If the system cannot recognize their transaction types or if they are not DeFi, they will be temporarily marked as "Unclassified (To Classify)". "Unclassified (To Classify)" transactions are excluded from the PNL calculation. To include them, you will need to manually specify the transaction types.
To review "To Classify" transactions, you can go to the "DeFi" page and use the filtering function to select "To Classify" → "All."
There are 4 types of unclassified transactions:
-
Transfer・・unclassified transfers are deposits/withdrawals in your wallets that are not determined automatically for their transaction types.
Examples are:
- Deposits and withdrawals from the exchange to the wallet
- ICO Participation from the wallet
- Received cryptocurrencies that are unrelated to Defi through airdrops, hard forks, etc
- Buying and selling of cryptocurrency through wallets between individuals
- Risky・・Within cryptocurrency users' wallets, risky transactions, such as airdrops intended to lure users to phishing sites, may be deposited without the investor's intent. We have introduced a feature that detects potentially risky transactions as “Risky Transactions.” (* Please note that this feature does not assess the value of tokens. It is only applicable to tokens without a market price, while tokens that do have a price should be treated as “Bonus” for profit and loss calculations. Therefore, please be aware that excluding risk transactions must be done at the own discretion.) Response to Scam tokens
- Unknown transaction type・・unknown transactions are DeFi transactions for which the system could not identify the transaction types. The system refers to the smart contracts associated with the transactions and attempts to identify their transaction types. If the system cannot determine the transaction type, the transaction is flagged as "Unclassified - Unknown transaction type".
-
Others・・others are irregular transactions or transactions that can't be reflected in the PNL calculation properly due to incorrect edits made in "Unclassified - Transfer" and "Unclassified - Unknown transaction type".
Examples are:
- Even though the ASSET MOVEMENTS column only shows "withdrawal" history, "Swap" ( Exchange of one cryptocurrency to another) was selected
- Even though the ASSET MOVEMENTS column only shows "deposit" history, "withdrawal" related transaction type was selected
- Even though there is no "Add Liquidity" transaction, "Remove Liquidity" was selected
*We're enhancing DeFi transaction recognition by expanding our transaction type dictionary and synchronizing wallet addresses, which might change "unclassified" transactions. If you've chosen transaction types for those, the system uses your selections for pnl calculation.
4. How to address "Unclassified (To Classify)" DeFi transactions
Please refer to the below help pages for more details:
How to Address "Unclassified (To classify)" DeFi transactions on EVM
How to Address "Unclassified" (To classify) DeFi Transactions on Solana
How to Address "Unclassified (To classify) DeFi transactions on bitcoin
bitcoin chain transactions are generally considered to be “transfers,” but in practice, there may also be cases where they represent remittances to third parties or payment records.
In order to reduce the manual work by changing or correcting transaction types, cryptact automatically classifies incoming transactions as “Bonus” and outgoing transactions as “Sell.”
As a result, there are no “To classify” transactions on the bitcoin chain.
However, please make sure to review your transactions on the DeFi transaction page to confirm that the transaction types are correctly classified, and adjust them as necessary. (please refer to the below 5. How to edit "Classified" DeFi transactions)
5．How to edit "Classified" DeFi transactions
Please take the following steps if you wish to edit DeFi transactions that are already in "Classified" status. Transactions that were automatically recognized by the system and transactions that you manually recognized (manually selected the transaction types) can both be edited using the following steps.
1. Select the DeFi transaction that you wish to edit. Click "Classified". You can filter transactions by "Auto" (they were automatically classified by the system) or "Manual" (manually selected the transaction types).
2. Click the "Edit" button.
3. Select the transaction type.
4. Click "Sync all".
5. The newly selected transaction type is reflected in the system.
6. Check "Transactions"
Once all the "To classify" transactions are resolved in the "DeFi Transactions" page, proceed to review all transaction history, including DeFi transactions, on the "Transactions" page. If you see the guidance "Some transactions are not included in your profit/loss calculations," it indicates either ongoing "To classify" or "Invalid transactions".
Transactions categorized as "To classify" on DeFi page, or "Invalid" on transaction page are not automatically included in profit and loss calculations (due to insufficient information). In cryptocurrency profit and loss calculations, they are excluded. Therefore, it's essential to resolve these categorizations.
Disclaimer
As stated in the Terms of Use, cryptact is not responsible for the calculated pnl. In addition, the information provided here is only a tentative description and does not take into account individual circumstances. If you have any questions about taxation, please contact your tax advisor.