🔗Chain Support

Current Status

Live Now:

• ✅ Helius RPC (Solana)

  • Solana blockchain data

  • Wallet tracking foundation

  • Currently underutilized (prepared for future features)

Planned Integrations

1. BSC (Binance Smart Chain)

Why BSC?

• Large trading community

• Low transaction fees

• Wide wallet adoption

• Many whales operate on BSC

Features:

• Track whale wallets on BSC

• BEP-20 token holdings

• Transaction history

• Cross-chain whale activity

RPC Provider:

• BSCScan API

• QuickNode

• Ankr

---

2. Polygon (Matic)

Why Polygon?

• Polymarket uses Polygon for settlements

• Low gas fees

• Fast transactions

• Ethereum compatibility

Features:

• Polymarket contract tracking

• On-chain bet verification

• Whale wallet balances

• Settlement tracking

RPC Provider:

• Polygon RPC

• Alchemy

• Infura

---

3. Ethereum Mainnet

Why Ethereum?

• Largest DeFi ecosystem

• ENS name resolution

• Whale wallet origins

• Token holdings (ERC-20)

Features:

• Ethereum whale tracking

• ENS domain resolution (0x1ff26...DBBD → vitalik.eth)

• Gas price monitoring

• NFT holdings

RPC Provider:

• Etherscan API

• Alchemy

• Infura

---

Cross-Chain Features (Post-Integration)

Unified Whale Profiles

Track a single whale across multiple chains:

WhaleKing's Portfolio:
├─ Solana:   $127K
├─ BSC:      $89K
├─ Polygon:  $43K (Polymarket)
└─ Ethereum: $212K
Total:       $471K

Multi-Chain Alerts

• "WhaleKing just moved $50K on BSC"

• "Top whale active on 3 chains in last hour"

• "Cross-chain arbitrage detected"

Chain-Specific Filtering

Filter whale alerts by blockchain:

• Solana trades only

• BSC trades only

• Polygon (Polymarket) only

• Ethereum only

• All chains

---

Technical Architecture

RPC Client Structure

core/
├── api/
│   ├── helius.client.ts      // Solana (existing)
│   ├── bsc.client.ts          // BSC (planned)
│   ├── polygon.client.ts      // Polygon (planned)
│   ├── ethereum.client.ts     // Ethereum (planned)
│   └── multichain.client.ts   // Aggregator (planned)

Unified Data Model

All chains return standardized format:

interface ChainWalletActivity {
  chain: 'solana' | 'bsc' | 'polygon' | 'ethereum'
  wallet: string
  balance: number
  transactions: Transaction[]
  tokens: TokenHolding[]
  lastActive: number
}

---

Environment Variables (Future)

# Solana
NEXT_PUBLIC_HELIUS_API_KEY=abc123

# BSC
NEXT_PUBLIC_BSC_RPC_URL=https://...
NEXT_PUBLIC_BSCSCAN_API_KEY=xyz789

# Polygon
NEXT_PUBLIC_POLYGON_RPC_URL=https://...
NEXT_PUBLIC_POLYGONSCAN_API_KEY=def456

# Ethereum
NEXT_PUBLIC_ETHEREUM_RPC_URL=https://...
NEXT_PUBLIC_ETHERSCAN_API_KEY=ghi789

---

Migration Strategy

1. Phase 1: Add Polygon (highest priority - Polymarket native)

2. Phase 2: Add Ethereum (ENS, largest ecosystem)

3. Phase 3: Add BSC (community demand)

4. Phase 4: Add Solana features (utilize existing Helius integration)

---

Why Multi-Chain Matters

For Users:

• Complete whale picture across all chains

• Better trading insights

• More comprehensive tracking

For PolyMarks:

• Differentiation from competitors

• Broader market coverage

• Future-proof architecture

---

Questions? Open a GitHub issue or reach out on Twitter.