BTC $- · ETH $- · SOL $- · BNB $- · XRP $- · DOGE $- · TON $- · ADA $- · AVAX $- · LINK $- · SUI $- · TRX $- · gas - gwei degen 70/100

~/tokens/listings $ cat quid-base-meme-distribution-risk.md

tokens Anuncios $QUID ·5 de agosto de 2026 SKIP 4/10

$QUID is up 25% in the last 24 hours, but the top 10 hold 97%: LP is not locked up

el equipo crptch · mesa de análisis · 4 minutos de lectura

// price · $QUID
― px╌ ma8▮ volH $0.179 · L $0.0454$0.144$0.134$0.115$0.125-13.3%04.08 12:0004.08 18:00ahora

What Happened: A Quick Launch with Limited Liquidity

The Squid token ($QUID) launched on Uniswap Base 32 hours ago with $1.1M in liquidity. In its first 24 hours, it surged +24.5% with $15.3M in trading volume-a 13.8x trading volume-to-liquidity ratio, indicating genuine trading activity rather than an artificial pump. The price is currently $0.124, with FDV inflated to $123.8M given such thin liquidity (112x spread).

At first glance, it’s a typical day-old token with good volume. Upon closer inspection, the red flags start with the distribution.

Distribution: 97% held by 10 wallets

This is where the trouble begins. According to on-chain data:

  • The top wallet holds 65.55% of the total supply
  • The top 10 hold 97.4%-this isn’t dispersion; it’s concentration, just like in scam listings
  • There are only 866 holders total-too few for a token with a $15M daily trading volume
  • The deployer holds nothing (0%)-that’s good, but suspicious (what are they waiting for?)
  • The LP is not locked (0% locked)-the creators can withdraw $1.1M at any time

According to our pattern database: a top-10 holding share > 60% has historically led to a rug pull in 27% of cases and a 2x+ pump in 19%. This isn’t a guarantee of a crash, but the distribution is poor.

Canon: half success, half failure

The launch quality score is 45/100 with a known_ratio of 89%-meaning the data is complete. The good news:

  • The mint has been suspended-the supply won’t be fully minted
  • Zero sales tax
  • No honeypot; sales are working
  • It lasted 33 hours (many gave up earlier)

What’s bad:

  • LP isn’t locked-that’s the main risk
  • Top 10 accounts account for 97% of activity
  • No social media or website-it’s a ghost project
  • First token deployment-no track record

Our crptch engine gave it a score of 35/100-that’s the SKIP zone. Deterministic weights flagged: LP unlocked (cap), top-10 concentration > 60% as a pump signal (but right now this is killing the score, not saving it).

Growth without a social signal: insider trading or bots?

$QUID has no social presence (has_socials: false). At the same time, buys (16.3K) exceed sales (21.3K) over the past 24 hours, but this is a marginal advantage. A 25% increase without mentions in the watchlists of major accounts is either insider-driven top-10 fuel, bot activity, or just the usual daily volatility. There is a complete lack of social context.

Based on our edge-case calibration: an age of 32 hours + $1.1M in liquidity theoretically prevents an immediate collapse by 1-2, but the liquidity status (not locked) is dragging the price down.

Risk Framework

Scenarios:

  • Top-10 sell-off: one large wallet (65%) or several top-10 holders will liquidate their positions-the LP is not locked, so nothing will stop them. The median drop based on our data in this scenario is -60-80%.
  • Consolidation: If the top 10 hold off on selling, volume will remain strong, and there could be a pump to 2x-3x. Based on patterns, the probability is 19% for the top 10 > 60%.
  • Market risk: The token is 1.5 days old; a degen market could swing either way based on insider news or social media activity (which is currently nonexistent).

Verdict

SKIP 4/10-not recommended given the current distribution and age of the token. Half of the “canon” has been completed, but the LP trap, concentration, and lack of social fundamentals make the token a “degen roulette” with bears holding the upper hand. If the top 10 holders start selling off, the drop could be swift and brutal. Monitor for 24-48 hours: either a social signal will appear and the deployer will lock the LP (in which case, reassess), or a dump will occur.

[tg token alerts] ✓ historial