Fix bug with relevant changedTxs set

Only transactions that have been streamed are relevant for the
changedTxs set because we _always_ stomp the changed tx onto the
streamedTxs array.

Author: samholmes

CHANGELOG.md

@@ -14,6 +14,7 @@
 - changed: Replace Thorchain Savers quoting with an information modal about the shutdown.
 - fixed: Show correct staked balance for deprecated Velodrome pools
 - fixed: Crash when retrieving `exchangeRates` in some situations when no internet is available
+- fixed: Transaction metadata loading bugs.
 
 ## 4.21.1 (2025-01-28)
 

src/hooks/useTransactionList.ts

@@ -84,8 +84,10 @@ export function useTransactionList(wallet: EdgeCurrencyWallet, tokenId: EdgeToke
     // but just overlay the new transactions over the old ones:
     const cleanupChanged = wallet.on('transactionsChanged', txs => {
       let relevant = false
+      const existingTxidsSet = new Set<string>()
+      streamedTxs.forEach(tx => existingTxidsSet.add(tx.txid))
       for (const tx of txs) {
-        if (tx.tokenId === tokenId) {
+        if (tx.tokenId === tokenId && existingTxidsSet.has(tx.txid)) {
           relevant = true
           changedTxs.set(tx.txid, tx)
         }