Recently organizing transaction records, I really don't want to go crazy waiting until the end of the year… My current clumsy method is: every time I switch positions / cross chains / claim airdrops, I conveniently record the time, chain, amount, a screenshot at the time, and the Tx hash into a spreadsheet. Don’t think it’s troublesome; later, you’ll thank yourself. Last week, I even found a cross-chain transaction with 0x7c3…a91. The bridge was stuck for a long time, and with recent bridge theft incidents, I was even more anxious. I could only follow the consensus of “waiting for confirmation,” but the same transaction showed different times on different browsers, and if I didn’t record it, it would be completely chaotic.

And for oracle anomalies, where the transaction price suddenly spikes or drops, if you don’t keep the on-chain state or order book at the time for reconciliation, it’s impossible to explain clearly. Honestly, I don’t fully understand how taxes are calculated in different regions, but keeping the evidence chain complete, keeping positions light, splitting into batches, and clearly writing stop-loss instructions at least makes it less like solving a case during reporting. That’s all for now.