ClaimScan v1.5: Cross-Chain DeFi Fee Tracker Across 4 Chains and 9 Launchpads

Roughly 40 percent of all creator fees across major DeFi launchpads go completely unclaimed. Not because the money is locked or unavailable. Because creators cannot track earnings scattered across 9 different platforms on 4 different chains, each with its own dashboard, its own API and its own claim process.

We built ClaimScan to fix that. One search field. Paste a Twitter handle, a GitHub username, a Farcaster profile or a raw wallet address. See exactly what you have earned, what you have claimed and what you are leaving on the table across 9 launchpads on Solana, Base, Ethereum and BSC. Then claim your fees directly without leaving the app.

Version 1.5 shipped on March 25, 2026. It adds BSC as the fourth chain, hardens the entire claim flow, passes an 80+ point security audit and introduces a CI pipeline. This post covers what changed, why it changed and how it was built.

What Changed in v1.5

BSC: The Fourth Chain

Clanker expanded to BNB Chain. ClaimScan now tracks Clanker fees on both Base and BSC, fetching fees in parallel using chain-specific RPC clients. BNB native pricing was integrated alongside SOL and ETH. The UI shows BSC chain icons, BscScan explorer links and BNB currency labels.

This means ClaimScan now covers 4 chains: Solana, Base, Ethereum mainnet and BSC.

Hardened Claim Flow

The claim system received a full security upgrade. The Bags.fm integration was updated for their latest API version. Bot protection was added as a mandatory verification step before any claim transaction can execute. If verification fails, the claim is blocked entirely.

Priority fees were added to every Solana transaction for congestion resilience. Transaction finalization tracking was upgraded so claim status automatically progresses through the full lifecycle without manual intervention.

80+ Point Security Audit

A comprehensive audit touched security, SEO, performance, mobile responsiveness and accessibility. Dark mode was fixed across all dashboard components by replacing hardcoded color values with proper theme tokens. XSS hardening was applied across input handling. Database migrations were restructured for safer rollback. Duplicate claim submissions are now prevented at the database level.

CI Pipeline and Monitoring

A GitHub Actions workflow now runs TypeScript type checking, ESLint and production builds on every push. Sentry was upgraded with environment and release tracking across client, server and edge configs. The whitepaper was regenerated as V1.5 to reflect the updated platform count, claiming section and security architecture.

The Problem: Creator Revenue Is Fragmented Across Chains

The DeFi launchpad ecosystem exploded. Pump.fun, Bags.fm, Clanker, Zora, Bankr, Believe, RevShare, Coinbarrel, Raydium. Each platform generates creator fees through different mechanisms: bonding curves, transfer fee extensions, protocol rewards, DAMM pools. Each has its own dashboard, its own claim flow and its own wallet requirements.

Now spread that across four separate blockchains. Solana with its own wallet ecosystem. Base and BSC with EVM wallets and smart contract calls. Ethereum mainnet where protocols like Zora accumulate rewards. A creator active on multiple platforms needs to check each one individually, connect the right wallet type, and manually track what has been claimed versus what is still sitting there.

Most creators do not bother. They launch on a platform, move to the next one and forget about the fees piling up behind them. The result is real money going uncollected, not because it is unavailable, but because the fragmentation makes tracking it practically impossible.

The Solution: Search, Track, Claim

Universal Identity Resolution

ClaimScan accepts four types of input: Twitter handles, GitHub usernames, Farcaster profiles and raw wallet addresses. The system automatically detects the input format and resolves it to all associated wallets across chains. A Twitter handle maps to Bags.fm and Bankr wallets. A Farcaster profile bridges to EVM wallets on Base, BSC and Ethereum. A Solana address queries Pump.fun, Believe, RevShare, Coinbarrel and Raydium directly.

This means creators do not need to remember which wallet they used on which platform. They paste one identifier and ClaimScan figures out the rest.

Four Chain Coverage

ClaimScan aggregates data from 9 DeFi launchpads spanning four chains. On Solana: Pump.fun, Bags.fm, Believe, RevShare, Coinbarrel and Raydium LaunchLab. On Base: Clanker and Bankr. On BSC: Clanker. On Ethereum mainnet: Zora protocol rewards. Each platform uses different APIs, different data formats and different fee structures. ClaimScan normalizes all of it into a single, readable breakdown showing earned, claimed and unclaimed amounts per platform with live USD valuations.

Live Fee Polling

Fees are not static snapshots. ClaimScan polls on-chain balances every 30 seconds using Server-Sent Events, so creators see their unclaimed fees update in real time without refreshing the page. If someone buys a token you launched and a new fee accrues, you see it immediately.

Direct Claim Execution

Finding unclaimed fees is only half the problem. ClaimScan also lets creators claim directly from the interface. Connect your wallet, select the fees you want to collect and execute the claim transaction without leaving the app. In v1.5, the claim flow includes bot protection, priority fees for Solana congestion and automatic finalization tracking. The system tracks claim status through the full lifecycle. A 0.85% service fee is applied on successful claims with a minimum of 0.001 SOL.

Creator Portfolio Dashboard

Every creator gets a profile page showing their complete earnings picture: per-platform breakdown, chain-specific totals, USD valuations using real-time pricing from DexScreener, Jupiter and CoinGecko, and full claim history with transaction links. Creators can share their profiles via shareable links for social proof.

Technical Architecture

Multi-Source Data Aggregation

The core engineering challenge was integrating 9 data sources that each work completely differently. Some require direct RPC account queries, others expose REST APIs, and some need social identity bridging before any on-chain data can be fetched. Each platform uses different data formats, different fee structures and different chain interactions.

We built a unified adapter layer where each platform has its own data source module that normalizes responses into a common schema: platform, chain, token address, earned amount, claimed amount, unclaimed amount in native units plus USD conversion. All adapters run in parallel so scan results stream in as fast as each source responds. In v1.5, the multi-chain adapters were refactored so Base and BSC share common on-chain read logic without duplication.

Identity Resolution Engine

Mapping social identities to on-chain wallets across multiple platforms required building a resolution pipeline that handles four identity providers. Twitter handles map to wallets via Bags.fm and Bankr APIs. GitHub usernames resolve through Bags.fm. Farcaster profiles bridge to EVM wallets for Base, BSC and Ethereum lookups. The system caches resolved identities in Supabase with wallet verification status and source platform attribution.

Infrastructure Stack

The frontend runs on Next.js 16.2 with React 19, Tailwind CSS 4 and Radix UI components. The backend uses Supabase PostgreSQL with Row-Level Security for data persistence, Redis for caching with in-memory fallback, and dedicated RPC providers for each chain. Pricing data flows through a multi-source waterfall: DexScreener first, then Jupiter for Solana tokens, then CoinGecko for native chain assets (SOL, ETH, BNB).

Caching is aggressive. Standard fee data has a 40-minute TTL. Heavy creators with 500+ fee records get a 2-hour cache to avoid hammering APIs. Live polling bypasses cache and queries on-chain balances directly for real-time accuracy.

Security Layer

The security layer includes rate limiting across all endpoints, bot protection on search and claim flows, wallet validation before claim execution, request signing on real-time streams, and full CSP and HSTS headers. Multiple layers of anti-abuse measures protect against automated scraping and enumeration attacks.

Design Decisions That Shaped the Product

Search First, Wallet Optional

Most DeFi tools gate everything behind a wallet connection. ClaimScan does not. You can scan any handle or wallet without connecting anything. This makes the tool useful for checking fees on public creator addresses, verifying earnings before connecting, and lowering the barrier to first use to zero. Wallet connection is only required when you actually want to claim.

Streaming Results Over Batch Loading

All 9 platform queries run in parallel. Results stream in via SSE as each source responds rather than waiting for every platform to finish. If Zora takes 3 seconds but Pump.fun returns in 200ms, the Pump.fun data is already on screen while Zora loads. This makes the app feel fast even when individual sources are slow.

Per-Platform Granularity

Results are displayed per launchpad with earned, claimed and unclaimed amounts clearly separated. This matters because each platform has different claim mechanics. A creator might be fully claimed on Pump.fun but have thousands in unclaimed fees on Raydium LaunchLab. The breakdown tells them exactly where to go.

Real-Time Pricing with Fallback Chain

Showing fees in native tokens (SOL, ETH, BNB) is not enough. Creators want to know dollar values. We built a three-tier pricing waterfall: DexScreener for the freshest data, Jupiter for Solana-specific tokens, CoinGecko for native assets as the last resort. Prices refresh automatically via cron jobs, so USD valuations stay accurate without manual intervention.

Platform Capability Matrix

Not every platform supports every feature. Some expose identity resolution through their APIs, letting ClaimScan map social handles to wallets. Others only support direct wallet lookups. Some enable token discovery so ClaimScan can find all tokens a creator launched. The current coverage:

Full identity resolution plus handle-based fees: Bags.fm (Twitter and GitHub), Bankr (Twitter), Clanker (Farcaster).

Token discovery enabled: Bags.fm, Clanker, Believe, RevShare, Coinbarrel, Raydium.

Direct claim execution: Bags.fm (with more platforms in progress).

Multi-chain queries: Clanker (Base and BSC), Zora (Base and Ethereum mainnet).

Results

ClaimScan v1.5 is live at claimscan.tech and completely free to scan. It covers 9 launchpads across 4 chains, resolves 4 identity types, polls fees in real time, converts everything to USD and lets creators claim directly from the interface with verified, priority-fee-enabled transactions. The entire scan process takes under 30 seconds.

This is not a prototype or a concept. It is a production tool handling real money for real creators, backed by a full CI pipeline, Sentry monitoring and a comprehensive security audit. The 40 percent of fees that go unclaimed across DeFi represent actual revenue that creators earned and never collected. ClaimScan makes finding and collecting that money as simple as pasting a handle.

Why This Matters for Your Project

ClaimScan demonstrates what a fullstack DeFi product looks like when built properly. Multi-chain data aggregation across Solana, Base, BSC and Ethereum. Identity resolution spanning four social platforms. Real-time on-chain polling with SSE streaming. Direct claim execution with bot protection, priority fees and transaction lifecycle tracking. A multi-layered security system with rate limiting and anti-abuse measures. A full CI pipeline with type checking, linting and builds on every push. All wrapped in a clean interface that a non-technical creator can use in 30 seconds.

If your project needs a utility, a dashboard, a DeFi tool or any kind of on-chain product built from scratch, this is the level of execution we deliver. Not mockups. Not wireframes. Production software that handles real transactions. You bring the idea. We ship it live.