Memecoin
Memecoin comparison is liquidity depth versus holder concentration
Memecoin comparison is most useful when it measures how much of a token can be sold near the quoted price and who controls the sellable supply. Executable liquidity comes from reserves available along a real route, after automated market maker fees and price impact. Holder concentration measures economically related owners, not an unfiltered ranking of addresses. A sound comparison therefore separates decentralized exchange pools, centralized exchange custody, bridge vaults, treasury contracts and ordinary wallets before producing a score. This page develops that narrow method across Ethereum, Solana and Dogecoin markets, then connects fixed protocol limits to the market-dependent quantities an analyst must recalculate.
Key takeaway: It is a market-quality analysis that contrasts executable liquidity with wallet distribution, while pool reserves shape price impact.
Raw totals hide the pool and owner structure
Two raw totals - pooled value and top-wallet share - create false rankings when the assets, venues and address roles behind those totals do not match across tokens in one dataset.
Pool balances need venue labels
Liquidity depth belongs to a specific pair, fee rule and venue. A SHIB/WETH pool on Uniswap does not substitute for a SHIB/USDC pool because WETH and USDC create different quote exposure, reserve sizes and routing options. A 1inch route can draw from several pools, yet the amount available at the quoted price remains trade-size specific. Record each pool contract, token pair, AMM version and reserve block before aggregating. Converting every pool to a common quote unit supports comparison; summing displayed dollar values without route simulation overstates executable depth.
Large wallets need entity labels
Wallet tables need an entity layer because an on-chain address is an account identifier, not a guaranteed owner. Ethereum uses 20-byte addresses, while Solana identifies accounts with 32-byte addresses. Etherscan and Solscan expose account-level balances, but pool contracts, bridge vaults, exchange custody and vesting contracts perform different economic roles. Group known operational accounts, remove pool-held inventory from owner rankings and keep uncertain labels separate without counting the same inventory twice. The classification changes the sellable-supply denominator, so the next decision is which owners can reach the market together.
Holder concentration sets the supply overhang
Ten classified owners provide a reproducible first screen because their combined share reveals whether a small group can meet the pool with substantial supply during one exit.
Holder concentration matters through sequencing. When several large owners sell into shallow pools, the invariant moves the quote before the remaining orders arrive. Report the top-10 classified-owner share, a Gini coefficient from 0 to 1 and the smallest owner count crossing 50% of classified supply at the same block height. A percentage-based Herfindahl-Hirschman Index reaches 10 000 when one owner holds the entire measured denominator. None of these metrics predicts an order, but together they distinguish broad distribution from inventory a few owners can mobilize. That distinction determines how much notional liquidity deserves credit.
How much liquidity survives a real trade?
One quoted reserve is insufficient: executable liquidity is the output a defined trade receives after the pool fee, curve movement and every routed hop during on-chain settlement.
Constant-product depth
Uniswap v2 applies x × y = k to two reserves and charges a total 0.30% swap fee. Its amount-out calculation treats 997 of every 1 000 input units as fee-adjusted input. A probe equal to 1% of the input reserve exposes curve movement in a unit-free way, while repeating it in the opposite direction catches asymmetric quote reserves. Compare final output per input unit, not reserve value alone.
Concentrated-liquidity depth
Uniswap v3 concentrates capital inside chosen price ranges, so only active liquidity at the current tick supports the next trade. The protocol permits ticks from −887272 through 887272 and separates pools by fee tier. An impressive total locked balance can therefore coexist with thin active depth near the market price. Record active liquidity across the tested price path rather than crediting every position in the pool.
Routed depth
Routed depth combines venues only when a router can settle the complete path in one transaction. A two-hop route performs two pool swaps, pays each pool’s fee and crosses both curves. Uniswap and 1inch quotes therefore belong beside direct-pool simulations, while gas remains a separate chain cost. The chosen route becomes the executable-liquidity figure for that trade size.
AMM design turns reserves into different price impact
Four Uniswap v3 fee tiers - 0.01%, 0.05%, 0.30% and 1.00% - show why identical token balances do not imply identical executable depth for the same order size and direction at settlement time.
Uniswap v2 spreads liquidity across the entire positive price curve, while Uniswap v3 places liquidity between selected ticks. Raydium distinguishes constant-product pools from concentrated-liquidity pools on Solana, and Orca Whirlpools also allocates liquidity across price ranges.
These designs change how much reserve inventory supports a particular price interval. A comparison must query the pool implementation rather than infer depth from token balances. Three pools holding the same token quantity can return three different outputs because their quote reserves, ranges, fee rules and route directions differ at the same block height.
Fee tiers also split liquidity for one pair. Uniswap v3 defines four standard tiers, whereas Uniswap v2 has one fixed 0.30% swap fee. Test every material pool and let output, not venue count, decide which path deserves depth credit.
Seven fixed boundaries behind comparable data
Seven protocol fields anchor the normalization step because each defines a hard numeric boundary before live balances, routes and owner labels enter the comparison model.
ERC-20 uses uint256 for total supply and balances, so the storage ceiling is 2^256−1 base units; its optional decimals field returns uint8. The classic Solana Token Program stores supply in u64, capping it at 2^64−1 base units, while decimals occupy one byte and a base mint account is 82 bytes. Uniswap v2 stores each reserve in uint112, permanently locks 1 000 base LP-token units and records the last block timestamp in 32 bits. Uniswap v3 accepts ticks from −887272 through 887272. Ethereum addresses hold 20 bytes; Solana account addresses hold 32 bytes.
| Protocol field | Hard boundary |
|---|---|
| ERC-20 totalSupply and balanceOf | uint256: 0 to 2^256−1 base units |
| Solana Token Program mint | u64 supply: 0 to 2^64−1 base units |
| Uniswap v2 reserve field | uint112: 0 to 2^112−1 units per asset |
| Uniswap v2 initial LP lock | Exactly 1 000 base LP-token units |
| Uniswap v3 tick index | −887272 through 887272 |
| Ethereum account address | Exactly 20 bytes |
| Solana account address | Exactly 32 bytes |
| Normalization rule | Apply each field’s unit boundary before comparing values |
A repeatable scoring method for two tokens
Three trade-size probes and seven ownership snapshots produce a more stable Memecoin comparison than one live quote and one unclassified holder table captured at once.
Liquidity score
Set three probes at 0.10%, 0.50% and 1.00% of the input-side reserve. For each probe, capture received output, fee drag, curve price impact and routed hops at one block height. Convert output into the same quote asset only after executing the route model. Score the percentage of input value retained on a 0-to-100 scale, then keep the raw outputs beside the score so the ranking remains auditable.
Ownership score
Capture seven holder snapshots at fixed block intervals and apply the same address labels to every token. Use the top 10 classified owners, the 0-to-1 Gini range and the count required to cross 50% of classified supply. Score broader distribution higher on a separate 0-to-100 axis. Do not average the two axes until the intended trade size sets their weights: a small order emphasizes route quality, while a large exit gives holder overhang more influence. The ranking decision then follows the order the reader expects to execute, as recorded in Memecoin networks step by step.
Network history explains fragmented markets
Four well-known tokens - DOGE, SHIB, PEPE and BONK - span three market structures, so liquidity and owner data must be read through their underlying networks during one shared observation.
Dogecoin began in 2013 as a native proof-of-work chain whose target block interval is one minute and block subsidy is 10 000 DOGE. Its on-chain holder model therefore differs from ERC-20 tokens. SHIB and PEPE use ERC-20 contracts on Ethereum, where pool and custody contracts appear directly in the same balance ledger as user addresses. BONK uses the Solana Token Program, where token balances live in token accounts and one wallet controls several accounts. Raydium and Orca pools add venue fragmentation to that account model by design.
History created the fragmentation a static market-cap ranking misses. Native DOGE, Ethereum ERC-20 balances and Solana token accounts require different collection rules before their liquidity and concentration metrics meet on one chart. Select the expected trade size, then compare both axes at a shared observation point.
Memecoin comparison: frequently asked questions
Does a burn address belong in the holder-concentration denominator?
A permanently inaccessible burn address should remain in total on-chain supply records but leave the economically controllable holder set. Its balance cannot join a sale, so counting it as a concentrated owner exaggerates supply overhang. Keep two denominators: contract-reported total supply for reconciliation and classified controllable supply for ownership metrics. Apply the same treatment to every token and document any address whose accessibility remains uncertain.
Which observation interval makes holder snapshots comparable?
A declared time window with exact block or slot endpoints makes holder snapshots comparable across chains. Block-based spacing works within one chain, but block production differs between Dogecoin, Ethereum and Solana. Use seven observations over the declared window, retain the exact block or slot identifiers and compare tokens at aligned endpoints. The interval should cover ordinary transfers without merging distinct market regimes into one distribution score.
Can LP token ownership reveal removable liquidity?
LP ownership reveals who controls withdrawal rights in constant-product pools, but the instrument differs by AMM version. Uniswap v2 issues fungible liquidity tokens representing proportional pool claims. Uniswap v3 represents positions as non-fungible tokens with chosen price ranges, so position value and active depth diverge. Classify lockers, treasury positions and independently controlled providers separately, then relate withdrawal authority to the trade-size probes used in the comparison.
When should bridge escrow count as one economic owner?
Bridge escrow should count as infrastructure custody when its balance backs corresponding tokens on another chain rather than discretionary inventory. Removing it from the owner ranking prevents double-counting locked assets as a sell-ready whale, yet the backing balance still belongs in supply reconciliation. Treat each bridge contract, wrapped token mint and destination supply as one linked system only after their accounting relationship is clear.
Is fully diluted valuation useful beside executable depth?
Fully diluted valuation supplies a scale denominator, but it does not measure the output a pool will deliver. Multiplying supply by a market price ignores reserve shape, fee tiers and holder behavior. Use it only as contextual scale beside trade-size-specific price impact, active liquidity and classified ownership. A token with a large valuation still ranks poorly on market quality when accessible reserves remain thin.
Why do fee-on-transfer tokens change reserve-based depth estimates?
Fee-on-transfer logic changes the amount a pool receives, so a quote based solely on the wallet’s submitted input overstates effective input. The token contract deducts or redirects units during transfer before the AMM applies its curve. Simulate the actual transfer path, use router support designed for this behavior and calculate output from the balance change the pool records. Contract-specific fees belong beside the AMM fee, not inside reserve depth.
Do liquidity locks preserve Uniswap v3 active depth?
A position lock preserves withdrawal restrictions for its stated duration, but it does not keep Uniswap v3 liquidity active at every price. Each position supports trades only inside its selected tick range. Market movement outside that range leaves the position inactive even while the non-fungible token remains locked. Compare lock expiry, range boundaries and current tick placement separately before crediting the position as executable depth.