fixup! feat(wallet): input resolver now searches TX history if input cant be found in current UTXO set

Author: AngelCastilloB

packages/wallet/src/global.d.ts

@@ -0,0 +1,15 @@
+export {}
+
+declare global {
+  interface Array<T> {
+    findLastIndex(
+      predicate: (value: T, index: number, obj: T[]) => unknown,
+      thisArg?: any
+    ): number;
+
+    findLast(
+      predicate: (value: T, index: number, obj: T[]) => unknown,
+      thisArg?: any
+    ): T | undefined;
+  }
+}

packages/wallet/src/services/WalletUtil.ts

@@ -66,10 +66,7 @@ export const createInputResolver = ({ utxo, transactions }: InputResolverContext
       }
     }
 
-    // Input resolver is also used to resolve inputs for historical view, so it is possible that client code is trying to resolve an input that
-    // was already spent, we need to look at the tx history to find it. We search here as last resort since this is more expensive
-    // that searching through the UTXO set for wallets with big TX History.
-    const historyTx = txHistory.find((entry) => entry.id === input.txId);
+    const historyTx = txHistory.findLast((entry) => entry.id === input.txId);
 
     if (historyTx && historyTx.body.outputs.length > input.index) {
       return historyTx.body.outputs[input.index];