Honestly, the more on-chain operations you do, the more you’ll realize that the real “sandwich attack” is flipping through the books at year-end.

My current habit is that after each transaction, I quickly screenshot the transaction hash and the gas fee, then drop them into a folder by month—so I don’t end up staring at scan pages for a dozen-plus addresses later.
Actually, tools like Crypto Tax can automatically pull the data, but when you run into cross-chain transfers, merges, or special contracts, you still have to manually add a few patches—don’t expect fully automatic universal solutions.

Lately, there really have been a ton of rumors about testnet point-quest tasks and mainnet token issuance. I’ve churned out a bunch of tx, but if the records are incomplete, your mindset can easily fall apart during next year’s tax filing.
Anyway, I’d rather save a few more CSV files than have the accountant sitting there trying to guess, “What kind of airdrop is this?”
Oh, and it’s best to put deposits/withdrawals and on-chain interactions into two separate tables—otherwise, reconciling later will make you question your whole life.

For now, that’s it—I’ll keep adding screenshots.