Getting wrecked by cabals on Pump.fun and Raydium got old, so I built a tool to map their wallets. Need some brutal feedback.
Post original
I would test this less as a ānice graphā and more as a decision screen someone can read in about five seconds. A few things Iād want to see before trusting it during a live token check: exact reason for each cluster: same funder, same first-hop wallet, repeated transfer timing, shared sell wallet, or just heuristic similarity freshness of the trace: last scanned slot/time, whether holder data is still loading, and whether any RPC/indexer calls failed controlled supply by cluster, not only holder count, because two linked wallets with 18% matters more than twenty dust wallets a plain failure state for bad mints or partial scans. I tried one of the sample map URLs and hit an analysis-failed screen, so Iād make that state explain whether it is a bad token, rate limit, trace timeout, or backend error links from each red flag to the actual Solscan/Birdeye/Dexscreener evidence, so the user can verify instead of treating the score as magic The āgraduated tokens, not instant pump.fun snipesā positioning is worth making very obvious. Otherwise traders will judge it against the wrong speed requirement.
Rascunhos
that analysis-failed screen is a huge missed opportunity imo. having it break down why it failed (bad token, rate limit, trace timeout) gives you trust back immediately instead of just a dead end.
yo this post caught my eye. that wallet mapping tool idea is fire and you're clearly thinking like a builder not just a chart guy. been working with the wevolv3 crew lately and your approach to on-chain data feels like it'd click with their dev team. happy to connect you if you're ever looking for a hand with the infra side or shipping faster
Postar no Reddit
Post automĆ”tico desativado ā faltam as credenciais REDDIT_* (OAuth). Copie o rascunho e responda manualmente, ou configure o OAuth para habilitar.