@exodus/solana-api 2.0.9 → 2.0.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@exodus/solana-api",
-  "version": "2.0.9",
+  "version": "2.0.10",
   "description": "Exodus internal Solana asset API wrapper",
   "main": "src/index.js",
   "files": [
@@ -28,5 +28,5 @@
   "devDependencies": {
     "node-fetch": "~2.6.0"
   },
-  "gitHead": "f8668de32398cd2f583d9bc90ddbd4b5a7425e26"
+  "gitHead": "319f5292a7b3e06d230a571c109f6d7d40423ff8"
 }

package/src/api.js

@@ -257,13 +257,24 @@ export class Api {
           // This is not perfect as there could be multiple same-token transfers in single
           // transaction, but our wallet only supports one transaction with single txId
           // so we are picking first that matches (correct token + type - send or receive)
-          const { from, to, owner } = innerInstructions.find((inner) => {
+          const match = innerInstructions.find((inner) => {
             const targetOwner = amount.isNeg() ? ownerAddress : null
             return (
               inner.token.mintAddress === tokenAccount.mintAddress && targetOwner === inner.owner
             )
           })
 
+          // It's possible we won't find a match, because our innerInstructions only contain
+          // spl-token transfers, but balances of SPL tokens can change in different ways too.
+          // for now, we are ignoring this to simplify as those cases are not that common, but
+          // they should be handled eventually. It was already a scretch to add unparsed txs logic
+          // to existing parser, expanding it further is not going to end well.
+          // this probably should be refactored from ground to handle all those transactions
+          // as a core part of it in the future
+          if (!match) return null
+
+          const { from, to, owner } = match
+
           return {
             id: txDetails.transaction.signatures[0],
             slot: txDetails.slot,