Sigh, to be honest, while I was organizing this year’s transaction records just now, I almost got scared to the point of breaking into a cold sweat.

I’d always thought that on-chain records were there, and that I could slowly look things up when the time came. But today I wanted to calculate the gas-cost of a cross-chain token swap, and I found that several addresses’ transfer records didn’t store the hash of any contract interactions. When I searched on a block explorer, there were dozens of pending swap-handling records—I couldn’t tell which transaction was which at all.

Later, I remembered that I’ve been using Excel to jot down the time, wallet address, chain, token contract, amount, and gas fees. Every month, I export a txlist from chain and cross-check. That’s when I realized that there was a DEX swap record with an unusually high gas fee. At the time, I thought it was slippage. Turns out the routing of the cross-chain bridge was wrong, and I’d basically lost 0.2 ETH for nothing.

Anyway, with stricter local tax enforcement and increasingly detailed compliance requirements, even if your on-chain actions were correct, if your records are incomplete, you really will go crazy during year-end filing. Now I create a separate sheet for each address, label every interaction with tags like “airdropped task,” “DEX swap,” and “cross-chain bridge,” and then back everything up monthly to my local drive.

Don’t think it’s too much trouble—when you’re truly audited, you’ll know how valuable those 10 minutes are.