fix: chore subscriber-ts tweaks (#66)

Author: neilcampbell

package-lock.json

@@ -22,8 +22,8 @@
     "pre-commit": "run-s check-types lint:fix audit test"
   },
   "dependencies": {
-    "@algorandfoundation/algokit-subscriber": "^1.3.0-beta.3",
-    "@algorandfoundation/algokit-utils": "^6.0.0-beta.1",
+    "@algorandfoundation/algokit-subscriber": "^1.3.0-beta.6",
+    "@algorandfoundation/algokit-utils": "^6.0.4",
     "@radix-ui/react-dialog": "^1.0.5",
     "@radix-ui/react-dropdown-menu": "^2.0.6",
     "@radix-ui/react-icons": "^1.3.0",

package.json

@@ -151,7 +151,12 @@ const subscribeToBlocksEffect = atomEffect((get, set) => {
                     bc.roles.includes(BalanceChangeRole.Sender) &&
                     bc.roles.includes(BalanceChangeRole.Receiver)
                   const isNonZeroAmount = bc.amount !== 0n // Can either be negative (decreased balance) or positive (increased balance)
-                  return isAssetOptIn || isNonZeroAmount
+                  const isAssetCreate = bc.roles.includes(BalanceChangeRole.AssetCreator) && bc.amount > 0n
+                  // This is technically not the correct handling, as the asset manager (assigned as the address in the balance change) must destroy the asset, however it's the creator who must hold the balance on destruction.
+                  // Unfortunately determining the asset creator is tricky once the asset is destroyed.
+                  // It's fairly common for the asset creator to be the asset manager, so simply assume that.
+                  const isAssetDestroy = bc.roles.includes(BalanceChangeRole.AssetDestroyer)
+                  return isAssetOptIn || isNonZeroAmount || isAssetCreate || isAssetDestroy
                 })
                 .map((bc) => bc.address)
                 .filter(distinct((x) => x)) ?? []