ClaimScan V2.5: Real-Time Fees, Visual Redesign and the Bags Hackathon

ClaimScan just shipped its biggest update yet. V2.5 brings a full visual redesign, real-time fee streaming, a public creator leaderboard, BSC chain support and a mobile-first interface rebuilt from scratch. And we are entering the Bags Hackathon with it.

Before we shipped, FINN, the founder and CEO of Bags, looked at what we built and publicly endorsed it. When the creator of one of the platforms you track tells you "nice work," you know the product is headed in the right direction.

This post covers everything that changed in V2.5, the architecture decisions behind the biggest features and why we are competing in the Bags Hackathon.

What Changed in V2.5

V2.5 is not a patch. It is a ground-up rebuild of how ClaimScan looks, feels and delivers data. Here is what shipped:

Real-time fee streaming. Fees are no longer static snapshots from a database cache. V2.5 streams live on-chain balances via Server-Sent Events. If someone buys a token you launched and a fee accrues, you see it update on screen within seconds, no refresh needed.

Full visual redesign. Every page, every component, every state was redesigned mobile-first. Responsive hero headers, skeleton loading screens per route, tap feedback mirroring desktop hover states and currency formatting tuned for readability at every breakpoint.

Public leaderboard. A ranked board of top creators by total fees earned across all platforms and chains. Shareable profiles, paginated results and avatar integration. This turns ClaimScan from a personal tool into a discovery platform.

BSC chain support. Clanker expanded to BNB Chain. ClaimScan now tracks Clanker fees on both Base and BSC, with BNB native pricing, BscScan explorer links and chain-specific icons across the interface. Four chains, nine launchpads.

Mobile-first UI. Every interactive element got a mobile pass. Hover effects have active-state mirrors for touch devices. Filter rows scroll horizontally on small screens without clipping. Leaderboard cards show full creator info including avatars. The entire app works on a phone as well as it does on a desktop.

Real-Time Fee Architecture

The biggest engineering challenge in V2.5 was making live fees work correctly across the entire profile page. The problem sounds simple: show fresh on-chain balances instead of cached data. The reality was far more complex.

In V2, the profile hero showed live SSE data while the platform breakdown table read from the database cache. This created a split where the hero might show "$500 unclaimed" while the table below showed "$0 unclaimed" because the cache had not caught up. The stat was real. The table was stale. Users saw a contradiction.

The first attempted fix restricted the hero stat to only count platforms with cached unclaimed rows. That hid real money. Wrong direction.

The proper fix was architectural. We moved live SSE polling out of the hero component into a dedicated LiveFeesProvider, a React Context that wraps both the hero and the platform breakdown. Both components consume the same live data through a useLiveFees() hook. No split. No contradiction.

The merge logic layers three data sources in order: cached fees from the database, then live overlay from SSE (which re-derives claim status from fresh amounts), then optimistic claimed overlays from pending transactions. Each fee record is keyed by a composite platform:chain:tokenAddress identifier so the merge is precise down to the individual token.

Live-only tokens (fees that exist on-chain but have not hit the cache yet) render as virtual rows so creators can act on fresh fees before the next sync cycle. The system treats the cache as a baseline and the live stream as the source of truth.

Visual Redesign: Mobile-First, Desktop-Polished

The V2.5 redesign was not a CSS theme swap. Every component was rebuilt with mobile as the primary target and desktop as the enhancement layer.

Hero headers scale from 28px on mobile to 40px on desktop using fluid responsive classes. Currency stat cards were stripped of monospace font rendering because Inter at bold weight renders decimal periods with visible side-bearings, making values like "$844.27K" look broken. We switched to tabular-nums and added a formatting regex that drops unnecessary decimals in compact K values.

Every hover effect (.hover-glow, .hover-lift, .card-hover, .row-hover) got a @media (hover: none) :active mirror. On desktop, you hover and see the effect. On mobile, you tap and get the same visual feedback. No dead interactions on touch devices.

Each route now has its own skeleton loading.tsx so transitions feel instant. The leaderboard pagination scrolls back to rank #1 on page change so users never land mid-list confused about where they are.

Public Leaderboard

The leaderboard turns ClaimScan from a lookup tool into a discovery layer. Creators are ranked by total fees earned across all tracked platforms and chains. Every entry shows avatar, handle, total earned, total unclaimed and platform distribution.

This matters for two reasons. First, it gives creators social proof. A top-ranked creator can share their ClaimScan profile as a public badge of earnings. Second, it makes the ecosystem visible. Anyone can see which creators are generating the most revenue and on which platforms, turning opaque DeFi data into transparent, browsable information.

BSC: The Fourth Chain

Clanker launched on BNB Chain and ClaimScan followed. The integration required adding a new chain-specific RPC client, BNB native pricing through the existing DexScreener/Jupiter/CoinGecko waterfall, BscScan explorer links for transaction verification and chain icons throughout the interface.

The multi-chain adapter architecture we built for V1.5 paid off here. Base and BSC share common EVM read logic without duplication. Adding a new EVM chain is now a matter of configuring the RPC endpoint, chain ID, explorer URL and native token pricing, not rewriting integration code.

ClaimScan now covers Solana, Base, Ethereum mainnet and BSC. Nine launchpads across four chains: Pump.fun, Bags.fm, Believe, RevShare, Coinbarrel and Raydium LaunchLab on Solana. Clanker and Bankr on Base. Clanker on BSC. Zora on Ethereum.

The Bags Hackathon

We submitted ClaimScan to the Bags Hackathon. The reasoning is straightforward: ClaimScan already tracks Bags.fm fees, resolves Bags identities via Twitter and GitHub handles, and executes direct claims on Bags through their API. It is one of the most deeply integrated third-party tools in the Bags ecosystem.

The hackathon submission is not a prototype built for a competition. It is a production tool that has been live for months, tracking real money for real creators. V2.5 represents the most polished version yet: real-time data, a redesigned interface, a public leaderboard and multi-chain coverage that no other fee tracker offers.

ClaimScan solves a real problem for Bags creators specifically. Fees accumulate across launches and most creators lose track of what they have earned versus what they have claimed. ClaimScan surfaces that data instantly and lets them claim directly without leaving the app.

FINN's Endorsement

Before we submitted to the hackathon, FINN, founder and CEO of Bags, saw ClaimScan and publicly commented "nice work!" on the announcement post. This was not a paid promotion or a partnership deal. It was an organic endorsement from the person who built one of the platforms ClaimScan tracks.

That validation matters. When the founder of a launchpad looks at a third-party tool built on top of their platform and approves of it publicly, it signals that the product is legitimate, useful and aligned with the ecosystem. It is the kind of endorsement you cannot buy.

By the Numbers

ClaimScan V2.5 is live at claimscan.tech and completely free to scan.

$2M+ in creator fees tracked across all platforms and chains. 520+ unique wallets scanned. 9 launchpads on 4 chains (Solana, Base, Ethereum, BSC). 4 identity types resolved (Twitter, GitHub, Farcaster, wallet address). Real-time SSE streaming with live USD valuations. Direct claim execution with bot protection and priority fees. A public leaderboard ranking creators by total earnings.

Roughly 40% of all creator fees across major DeFi launchpads still go unclaimed. Not because the money is locked. Because the fragmentation across platforms and chains makes tracking it nearly impossible. ClaimScan fixes that with one search field.

What This Means for Your Project

ClaimScan V2.5 demonstrates what a production DeFi tool looks like when built properly. Multi-chain data aggregation. Real-time streaming architecture with SSE and React Context. Identity resolution across four social platforms. A visual redesign executed mobile-first with hover/tap parity. Direct on-chain claim execution with security layers. A public leaderboard turning private data into social proof.

This is the level of execution we bring to every project at LW. If you need a utility, a dashboard, a DeFi tool or any on-chain product built from scratch, we ship production software that handles real transactions. Not mockups. Not wireframes. Live tools that move real money.