Every year during tax season, what I fear most isn't profit or loss, but "where did this amount come from and where did it go"… Especially when cross-chain transactions increase, the router gets stuck, retries happen, and on-chain there are more small transactions, refunds, and reissues, leading to a direct crash during year-end reconciliation. My simple solution: start now by keeping a record of both "intention" and "result" — screenshots of orders/tx hashes, addresses before and after cross-chain, number of retries for failures, and preferably a human-readable note: why was the transfer made, who was it sent to, and which chain is expected. Don't wait until the end of the year to piece it together from memory. Recently, that main chain is undergoing upgrades/maintenance, and everyone in the group is guessing whether projects will migrate. I instead took those few days of cross-chain records and packaged them separately for safekeeping, as that's the most likely time for issues to occur. We'll see.