This page explains the procedures for handling when a blockchain that was previously unsupported by cryptact becomes a supported blockchain.
Example
Solana was an unsupported chain on cryptact, so until the 2024 fiscal year, transactions were uploaded as custom transactions. Later, cryptact added support for the Solana chain. You want to keep the Solana transaction history that has already been uploaded via a custom file and start adding Solana history via wallet address synchronization from the 2025 fiscal year onward. Is it possible to reflect only transactions from a specific date onward using wallet address synchronization?
Solution
By using the DeFi feature and adding the wallet address to the Solana chain, you will be able to retrieve the transaction history.
・ How to use DeFi (Decentralized Finance) functions
・ How to connect to a wallet address
However, since all past transaction history within the wallet address will be reflected in cryptact, if you have already uploaded the Solana history as custom transactions for previous years, there may be a risk of double counting.
Since the system is designed such that new history cannot be added to locked data for a specific fiscal year, by locking the data for the 2024 fiscal year, you can add the wallet address. This will allow you to import transaction history starting from the 2025 fiscal year onward, without affecting the previously locked data.
Note1．Since the system does not allow adding or editing history for locked fiscal years, please make sure to
complete the calculations before locking the data.
2．Data locking can be set on a per-year basis and cannot be done mid-year. In some cases, this may lead to double counting.
Example
If the fiscal year-end is set to December 31st, and data for the 2024 fiscal year was locked, followed by adding the wallet address, the Solana history was uploaded via custom files until January 2025. As a result, the transactions for January 2025 were double-counted.
SolutionIf you uploaded a custom file containing only Solana history using the
subcategory feature, you can delete the custom file for each subcategory.
If a custom file containing both Solana history and other transaction histories has been uploaded without using the subcategory feature, and there are duplicate entries, you can either manually delete the duplicate transactions or delete all transactions uploaded after January 2025. After deleting, modify the custom file to only include Solana transactions and re-upload it, excluding the non-Solana history.
How to add/edit/delete transactions manually from the screen