[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]  Crypto Tax Made Easy [@CryptoTaxSucks](/creator/twitter/CryptoTaxSucks) on x 15.4K followers Created: 2025-07-23 04:20:58 UTC This is the most psychotic, edge case, power user feature request ever. But hear me out. Our clients with huge txs counts (even >10k) cause tax software to have data ingestion issues. Proposed solution: Once a user locks a tax year: Archive the old transactions, only feed the existing inventory to the tax engine vs. all transaction data, and only sync new transaction data on your RPC calls. I imagine this would both: -Reduce RPC costs for the software -Increase the chances that the correct data is ingested -Reduce calculation times Again, extreme edge cases. Probably a super low priority fix since its a huge change to architecture. But it's super annoying when big wallets are missing data or it takes hours for a huge account to have the tax calculations update. So I'm trying to be solutions-oriented vs. whining 😜 XXXXX engagements  **Related Topics** [sync](/topic/sync) [locks](/topic/locks) [10k](/topic/10k) [tax bracket](/topic/tax-bracket) [crypto taxes](/topic/crypto-taxes) [Post Link](https://x.com/CryptoTaxSucks/status/1947874557538226251)
[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]
Crypto Tax Made Easy @CryptoTaxSucks on x 15.4K followers
Created: 2025-07-23 04:20:58 UTC
This is the most psychotic, edge case, power user feature request ever.
But hear me out.
Our clients with huge txs counts (even >10k) cause tax software to have data ingestion issues.
Proposed solution:
Once a user locks a tax year:
Archive the old transactions, only feed the existing inventory to the tax engine vs. all transaction data, and only sync new transaction data on your RPC calls.
I imagine this would both:
-Reduce RPC costs for the software -Increase the chances that the correct data is ingested -Reduce calculation times
Again, extreme edge cases. Probably a super low priority fix since its a huge change to architecture.
But it's super annoying when big wallets are missing data or it takes hours for a huge account to have the tax calculations update.
So I'm trying to be solutions-oriented vs. whining 😜
XXXXX engagements
Related Topics sync locks 10k tax bracket crypto taxes
/post/tweet::1947874557538226251