fix: revert to using nominationPools config key to access nomination …

…pools details (#1730)
TalismanSociety · Dec 6, 2024 · 0e2f457 · 0e2f457
1 parent 869ed0c
commit 0e2f457
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/apps/extension/src/ui/domains/Staking/hooks/nomPools/useDetaultNomPoolId.ts b/apps/extension/src/ui/domains/Staking/hooks/nomPools/useDetaultNomPoolId.ts
@@ -7,7 +7,7 @@ export const useDetaultNomPoolId = (chainId?: ChainId | null | undefined) => {
   const remoteConfig = useRemoteConfig()
 
   return useMemo(() => {
-    if (!chainId || chainId === "bittensor") return null
-    return remoteConfig.stakingPools?.[chainId]?.[0] ?? null
-  }, [chainId, remoteConfig.stakingPools])
+    if (!chainId) return null
+    return remoteConfig.nominationPools?.[chainId]?.[0] ?? null
+  }, [chainId, remoteConfig.nominationPools])
 }