gmgn-holder-analysis

BEFORE RUNNING ANY COMMAND: Run gmgn-cli config --check. If exit code is 0, proceed normally. If exit code is 1, run gmgn-cli config and show output, then apply the key with gmgn-cli config --apply <KEY>. If unknown option, tell user to run npm install -g gmgn-cli.

IMPORTANT: Always use gmgn-cli commands. Do NOT use curl, WebFetch, or visit gmgn.ai.

When the user asks to analyze holders for a token, extract --chain and --address from their message, then run the analysis script below. Also detect the user's language: set LANG to 'zh' if the user wrote in Chinese, 'en' if in English (default 'zh').

Analysis Script

Run the following command, replacing the placeholders with the actual values:

python3 ~/.claude/skills/gmgn-holder-analysis/analyze.py <FILL_IN_TOKEN_ADDRESS> <FILL_IN_CHAIN> <FILL_IN_LANG>

• FILL_IN_CHAIN: sol for Solana addresses; for EVM 0x... addresses use auto unless the user explicitly specifies a chain (bsc/eth/base)
• FILL_IN_LANG: zh if user wrote Chinese, en if English, default zh

Output Rule

After the script finishes, paste the complete stdout verbatim into your reply — every line, every section, nothing omitted or summarized. Do NOT add any introduction, commentary, or summary before or after the output block.

Field Reference

All holding percentages the script prints are share of tradeable float (1 - burn - DEX), not share of total supply. amount_percentage from the API is share of total supply; the script re-bases it. Because only the top 100 holders are fetched, a float percentage is a floor when those 100 wallets do not cover the whole float; the footer reports the actual coverage and states which case applies — floors when coverage <99.5%, complete values when the top 100 cover all of it.

When burn + DEX leave less than 2% of supply tradeable (typically a launchpad token before migration), the float denominator degenerates: every / float_share inflates dust wallets to double digits or 100%. The script detects this, prints a banner with absolute token/USD figures instead, and sets the rating to ⚪ Cannot Assess.

The same suppression applies when token holders returns an empty list (token has no active holders left, or upstream stopped indexing it). Every percentage would render 0.00% and every threshold would pass, so the report would otherwise read "✅ Normal — no obvious dump risk". The script prints a no-data banner instead, replaces each "none found 🟢" line with ⚪, and rates ⚪ Cannot Assess. "No data" is never reported as "no risk".

In both cases no float percentage is printed at all — every one renders as n/a (无法评估) and every percentage flag renders ⚪. Printing the number with a caveat was not enough: a divide-by-zero float puts hold 100.00% and hold 0.00% in the same report, and a reader skimming past the banner reads Rat Trader 1 hold 100.00% as a finding. Wallet counts, token amounts, USD values, and market caps still print — they do not pass through float_share. Percentages on a total-supply basis also still print (burn, DEX, float share itself, and the chip-quality buckets), because those denominators are unaffected.

Holder object key fields

Created-tokens response fields

Rating Standard

All thresholds below are share of tradeable float, matching the script. They are not comparable to GMGN's own UI, which reports share of total supply — on a token whose LP holds 56% of supply, the same wallet reads 2.4× higher here.

Entry timing pressure (批次浮盈/出货) does NOT affect the overall rating — it only affects section display.

Per-metric flag thresholds

Diamond hands invert (more is better) and use their own emoji set: ✅ >60% / 🟡 >35% / ⚠️ ≤35%. Diamond hands require buy_tx_count_cur > 0 — a wallet that never bought has no cost to hold through, so zero-cost airdrop recipients are reported separately as "空降未动 / Idle airdrop" rather than being credited as diamond hands.

Linked funding is escalated to at least 🟡 whenever any group was funded within 60s, regardless of size — scripted batch funding is a structural signal, not a magnitude one.

Chip quality (footer)

Three mutually exclusive buckets over the chips held by observed wallets (denominator is normal_pct, i.e. total-supply basis, not float): bought in with no risk tag / zero-cost airdrop / risk-tagged. They are reported separately rather than collapsed into one "healthy chips" number, because a risk tag means a proven-bad address while zero-cost airdrop only means unknown provenance.

Headline flag, first match wins: 🔴 risk-tagged >30% · 🟢 clean ≥50% · 🟡 clean ≥30% · 🟡 when zero-cost airdrop accounts for ≥80% of the non-clean remainder · 🔴 otherwise. So an airdrop-distributed token reads 🟡 with its composition spelled out, not "healthy chips 0.0% 🔴".

The composition is total-supply based, so it survives a degenerate float and its three percentages still print — but the headline flag is neutralized to ⚪ (and the chips' share of supply appended) whenever the rating is ⚪ Cannot Assess, since a 🔴/🟢 verdict over dust-level chips would contradict the rating above it.

Supported Chains

sol, bsc, base, eth, robinhood, arc, stable

Notes

• balance >= 1 threshold avoids dust false positives when identifying dev holdings
• SOL native_balance is in lamports (÷1e9); bsc/eth/base are in wei (÷1e18). Decimals for arc/stable/robinhood are unconfirmed, so the buying-power section reports "not assessed" on those chains rather than printing a converted figure that would be wrong.
• Holder buying power needs a live native-token price, fetched with token info on the wrapped native address (So111…1112 / WBNB / WETH / Base WETH). When that call fails, the section falls back to native units and prints no USD figure.
• total_supply is estimated as the median of balance / amount_percentage across normal wallets
• cur_price is estimated as the median of usd_value / balance across normal wallets
• Entry MC = total_supply * avg_cost, shown alongside unrealized PnL for every Top5 wallet
• Top5 displays Twitter name when available; else first4...last4 format
• Risk-wallet subtotals are per-category and can exceed the deduped total; the script prints how many wallets carry more than one risk tag when that happens.
• creator_ath_info.ath_mc can lag behind the token's current MC after a fast pump (upstream ath_price has been seen equal to price_24h). The script cannot recompute it, so when the reported ATH sits more than 5% below the current MC it prints a staleness warning next to the figure instead of presenting it as the dev's peak.