Pumphouse · MARKET NOTE
Published 2026-06-21

Solana Meme Coin Scanner Telemetry Resolves Wallet Cohort Cluster Risks Across Pump.fun Launches

Evaluating Solana meme coin scanner metrics on Pumphouse isolates wallet cluster risks and bonding-curve survival across Pump.fun launches, recording a fresh board of 200 tokens with 16 green and 26 red at the 07:31 UTC snapshot.

This analysis utilizes live telemetry and the memecoin paper demo ledger database, rather than recommending live buying or selling actions. All figures represent paper-only outcomes extracted directly from the system state and validated against the live database at 2026-06-21 07:31 UTC.

Indexer Latency and Token Freshness Distribution

The Solana meme coin scanner depends on low-latency data feeds to evaluate new launches. At 2026-06-21 07:31 UTC, the indexer freshness check recorded the latest event as 0.0 minutes old, indicating active live replication status (live=True) before hitting the 30.0-minute stale-after boundary. The fresh board telemetry over the trailing 6 hours tracked 200 tokens. The scanner categorized these launches into 16 green, 158 amber, and 26 red tokens. Concurrently, the trending read-only board captured 30 wallets within a 15-minute window.

Grading logic prevents premature classification: a token must demonstrate at least a 2.5x lift across two fresh, non-overlapping live windows before any claim is allowed, leaving the edge access interface locked (unlocked=False). These metrics confirm that while the vast majority of tokens fall into the amber or red classification, the Solana holder scanner isolates the small cohort clearing the strict green filter.

Solana Holder Scanner and Wallet Cohort Analytics

Evaluating cluster risk and identifying Pump.fun cabal detection patterns requires granular tracing of funder origins. The database tracks a cohort of 74 wallets, all active in the live DB. Funder intelligence is cataloged in /root/Pumphouse/funder_intel.db and /root/Pumphouse/pump_events_live.db. The holder scanner maps wallet edges to identify coordinated purchasing groups.

To capture coordinated purchasing groups distributing capital across fresh wallets, the system matches wallet footprints across /var/www/memes/api/wallet_finder.json and /var/www/memes/api/confluence.json. The narrative engine at /root/Pumphouse/narrative_engine.db tracks structural alignments, while /root/Pumphouse/narrative_media.db correlates media velocity lanes. This identifies cluster risk where a single funder wallet generates multiple downstream participants.

Recent database updates restricted operations to BW_SENTINEL_SOLO, recording only BW_SENTINEL_SOLO|BwWK17...|0.8 in copy_lanes and setting SENTINEL_PAPER_ONLY/live_allowed=0 in copy_wallet_tiers. This quarantine of the BwWK real execution rows isolates historical live-loss evidence, preventing the wallet from acting as a general live-approved sentinel while the solo slice undergoes forward-paper testing. The system listener refreshes these lane maps automatically on a 30-second log cycle.

Memecoin Paper Demo Ledger Replay Analysis

Trade outcomes are evaluated through a capital-constrained replay on a memecoin paper demo ledger. Starting with a GBP 50.0 bankroll, the model executes trades with a GBP 0.5 base stake, allocating a flat GBP 2.5 stake to high-velocity momentum lanes (MEDIA_VELO, MEDIA_VELOR, VELO, and VELOR).

The board figures reflect the cumulative performance since the GBP 50.0 reset:

This illustrates performance variance across filtering lanes. Low-win-rate lanes like BUNDLE rely on outlying tail events to offset base losses, whereas VELO exhibits tighter distribution.

Telemetry Limitations and Execution Guardrails

All execution remains closed and simulated. The real-money execution files /var/www/memes/api/exec_live.json and /root/Pumphouse/exec_status_state.json confirm live trading is disabled, real transactions are blocked, and the public feed is redacted. Cluster risk tracking on PumpSwap post-graduation survival awaits operator review. Telemetry in the memecoin paper demo ledger is based on backtest replays and does not provide purchase instructions.

System health metrics report normal core status. The spine command output at /root/FreedomCore_Tools/data/system_spine/latest.json indicates an overall ok status with no failures, containing only a warning from observability:non_page_events. Funder intelligence from /root/Pumphouse/funder_intel.db maps historical associations rather than active positions.

For details, consult the Pumphouse method. The bonding curve tracker logic references the official Pump.fun docs, and the live feed relies on the Solana RPC WebSocket docs layer. Schema definitions comply with Schema.org BlogPosting standards. Access additional details on the Atlas notes board and the main FreedomCore workspace.

Open the Pumphouse meme-coin research board

FreedomCore Pumphouse →