Solana Meme Coin Scanner Research: Funder Cluster Analysis and Paper Replay Results

The transition of the Pumphouse analysis platform to a paper-only research model highlights the structural difficulty of executing low-latency trades on Solana, where transaction slippage and cluster risk frequently degrade live results relative to theoretical paper models.

Funder Entity Detection and Solana Holder Scanner Roster

Using a Solana meme coin scanner to evaluate these velocity lanes demonstrates that paper performance often diverges significantly from live execution due to on-chain latency and fee drag. To address cluster risks, the Pumphouse platform relies on a database of historical entities to power its Solana holder scanner. The underlying database contains 2,936,172 pump events, 3,501,771 early wallets, and 598,433 scored candidates, which are logged in /root/Pumphouse/pump_events_live.db. Tracking funding pathways is essential for Pump.fun cabal detection, which maps how fresh wallets are capitalized before entering launches. According to the database at /root/Pumphouse/funder_intel.db, the system logs 106,957 wallet funders, 186,122 funder events, and 71,578 funder scores. Among these, the parser identified 22,485 cross-token reused funders and 498 same-token multi-wallet funders. Recent analysis of the canonical token BcHEaaTCvycPwwsJ9yQTXdHP9X2gCLkznDbZ8VySpump revealed a shared funder G2YxRa6wt1qePMwfJzdXZG62ej4qaTC7YURzuh2Lwd3t that also capitalized rapid launches such as GZMzT7RKqyJE1b7WwyoJz1WgkrQcsrwTU84J7pc2pump, which moved from a market capitalization of $1.6k to $132.7k in 68 seconds, and CKb9LF6oMATssc6Kk3hD2V99Tm9Jiy3WzqT1QJt4pump, which rose from $2.0k to $132.0k in 66 seconds. Network analysis details can be reviewed in /root/Pumphouse/reports/fable_funder_copy/FABLE_FUNDER_COPY_20260626.md.

Memecoin Paper Demo Ledger Performance and Replay Analytics

Evaluating historical performance on a memecoin paper demo ledger requires tracking designated velocity lanes. Researchers can consult the Pump.fun docs for baseline mathematical parameters. Following a system reset to a bankroll of GBP 50.0 and a baseline stake of GBP 0.5, paper replication results were:

• BUNDLE: GBP 466.01 (+416.01), 982 of 2093 entered, 11.0% win, best 9797.5%, worst -93.8%.
• VELO: GBP 249.48 (+199.48), 210 of 210 entered, 49.0% win, best 1240.3%, worst -98.9%.
• VELOR: GBP 157.09 (+107.09), 366 of 366 entered, 42.3% win.
• MID: GBP 83.37 (+33.37), 775 of 1463 entered, 27.2% win.
• MEDIA_VELO: GBP 73.16 (+23.16), 31 of 31 entered, 58.1% win.
• CONFLUENCE_V: GBP 37.71 (-12.29), 1155 of 1184 entered, 10.1% win.

Live Execution Halt and Fail Closed Protocol

On 2026-06-26 at 14:10 BST, live execution was suspended, transitioning all operations to a fail-closed status as documented in /root/Pumphouse/EXECUTION_PAUSED. The live execution engines, including pumphouse-exec-mirror.service and pumphouse-mayhem-exec-mirror.service, were stopped and remain inactive. Data ingestion and paper lanes continue to run under strict constraints. The system enforces EXEC_ARMED=0 and PUMPHOUSE_EXEC_LIVE_ALLOWED=0 via the configuration file /etc/systemd/system/pumphouse-listener.service.d/zzzzzzzzzzzzzzzzzzzzzzzz-paper-only-after-stop-20260626.conf. This configuration ensures that while the listener processes incoming events, no real capital is deployed. The status can be verified by querying the public endpoint /var/www/memes/api/exec_live.json, which tracks active wallet cohorts and confirms that direct execution remains disabled. Detail regarding this transition is outlined in the report /root/Pumphouse/reports/pumphouse_shutdown/PAPER_ONLY_RESUME_20260626_141030.md.

Narrative Confluence Models and Data Integrity

The narrative engine at /root/Pumphouse/services/pumphouse_narrative_engine.py processes raw data feeds to isolate topics while avoiding public exposure of private wallet keys. For real-time event streaming, the listener service interfaces with Solana nodes as described in the Solana RPC WebSocket docs. A security audit conducted via the read-only tool /root/Pumphouse/tools/pumphouse_narrative_leak_probe.py scanned public narrative JSON files against private database registries. The probe analyzed 194 private wallets, 117 private mints, and 63 private funders, confirming zero public leaks across the seven public narrative files. However, the system's integration with public networks remains degraded. The GDELT combined adapter responded with an HTTP Error 429 (Too Many Requests), which is detailed in the source health report at /root/Pumphouse/reports/narrative_source_health/latest.json. Research regarding these events and their relation to narrative overlays can be examined in /root/Pumphouse/reports/master_confluence_join/MASTER_CONFLUENCE_JOIN.md.

Methodology and Analytical Constraints

The Pumphouse method relies on isolating early launch parameters to determine structural patterns rather than chasing individual token momentum. Historical backtests, such as the wallet13 exit ladder optimizer, analyzed 29,952 configurations over a 96-hour window using a simulated stake of GBP 5.0 per trade. The optimal configuration derived from this test was a split exit model: selling 90% of the position at a 2x multiple and retaining 10% for a 3x multiple. This configuration produced a theoretical net outcome of GBP 93.05, surpassing the operator's proposed exit ladder of 80% at 2x, 10% at 4x, and 10% at 10x, which generated GBP 74.74. These findings, along with wider network research, are cataloged in the Atlas notes database. The broader research initiative managed by FreedomCore maintains that until low-latency transaction routing can be reliably achieved without significant slippage, all execution strategies must remain confined to paper environments.

Analytical Caveats and Operational Constraints

It is important to state that the results in the memecoin paper demo ledger are simulated outcomes and do not reflect live execution. Real-money mirroring results, when active prior to the suspension, showed significant execution drag. For instance, the actual execution of the token SolidStart AI landed at a real fill of $2.6k compared to the paper trigger of $4.8k, while IPO.fun filled at $13.6k against a paper trigger of $2.8k. These discrepancies arise from transaction latency and stale quote failures, such as router error code 6063 and custom error code 6005, which are logged in /root/Pumphouse/reports/execution_repair_6063/EXECUTION_REPAIR_6063_20260625.md. A proposed low-latency secondary execution architecture, including a Rust or Go hot path and prebuilt transaction routing, has not been designed or implemented, and any such development remains subject to formal operator approval.