What’s the problem? Users with Solana wallets who use Jupiter DCA are finding that after re-importing (or adding fresh) their wallet, DCA transactions are no longer classified as "open" or "close" orders. Instead, these transactions are now ingested as generic Sends, which breaks tracking and accurate reporting for these users. What’s the ideal outcome? DCA transactions from Jupiter on Solana wallets should be automatically recognized and classified as "open" or "close" orders even after a wallet re-import. Users expect transaction parsing to work seamlessly and not require manual intervention after importing their wallets. Keywords: Jupiter DCA, Solana, open/close order misclassification, wallet re-import, transaction parsing
