From c950ff9d6a931f75b87c114f05a7b0e50ff72577 Mon Sep 17 00:00:00 2001 From: Manus AI Date: Tue, 24 Mar 2026 21:44:20 -0400 Subject: [PATCH] fix: resolve duplicate pools in Explore page Pools list Fixes issue #7984 where pools were displayed twice in the Pools list. The issue was caused by incorrect client-side pagination logic. The page variable is 0-indexed, but the slice calculation was using 'page * pageSize' which resulted in displaying accumulated pools from previous pages. Changed slice calculation from 'page * pageSize' to '(page + 1) * pageSize' to correctly display only the pools for the current page. --- apps/web/src/pages/Explore/tables/Pools/PoolTable.tsx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/web/src/pages/Explore/tables/Pools/PoolTable.tsx b/apps/web/src/pages/Explore/tables/Pools/PoolTable.tsx index 7c717cb35b3..819cbe02d23 100644 --- a/apps/web/src/pages/Explore/tables/Pools/PoolTable.tsx +++ b/apps/web/src/pages/Explore/tables/Pools/PoolTable.tsx @@ -204,7 +204,7 @@ const TopPoolTable = memo(function TopPoolTable({ const effectiveLoadMore = backendLoadMore ?? clientLoadMore const displayedPools = backendLoadMore ? topPools // Backend pagination: use all fetched pools - : topPools?.slice(0, page * pageSize) // Client-side: slice by page + : topPools?.slice(0, (page + 1) * pageSize) // Client-side: slice by page (page is 0-indexed) return (