What is the dev wallet?
A tool generally identifies a creator or deployer address from platform records or onchain transactions. It is not a declaration of every account the creator controls. A token mint or contract address is also different from the creator's wallet. Token accounts, routers, custody services, and liquidity positions require their own interpretation.
The visible dev balance is one attributed address. The economic dev position may include supported side wallets, team allocations, treasury assets, and liquidity rights. Keep token inventory, control rights, and fee income separate.
How can a low balance mislead?
The visible address holds 2%, while four supported side wallets hold 2% each. The attributable group is 10% on the same denominator. If the creator transfers inventory to a side wallet, the visible balance falls without an actual sale. If the links are not established, the group total is a hypothesis, not a proven creator holding.
Fresh addresses do not necessarily belong to the creator. People can create new wallets for privacy or operational reasons. Similar allocation and timing are leads; supported funding, direct transfers, and repeated behavior make the case stronger.
How to investigate it
| What to inspect | Where to look | What it establishes |
|---|---|---|
| Who launched it | Creation transaction or documented launch record | Identified creator/deployer, not all related addresses |
| Who funded a fresh buyer | Initial funding transaction and earlier address history | A funding relationship; common services may serve unrelated users |
| Where inventory went | Outgoing token transfers and recipient balances | Movement of units; a transfer is not a sale |
| Whether it was sold | Completed swaps, quantities, received assets | Observed liquidation, subject to route and account interpretation |
| Remaining group holdings | Current balances of supported linked owners | Attributed inventory with explicit coverage limits |
Click transactions, not just a green/red feed label. Follow directly supported recipient paths and record the evidence for each addition to the group. Stop calling a link confirmed when history disappears into a service or ownership becomes ambiguous.
Common patterns and their limits
Splitting balances can keep each wallet below a holder filter. Relaying transfers can change the top-holder list without reducing inventory. Fresh wallets can buy independently of the primary wallet and produce no bubble-map token links. Small public buys can coexist with larger sales elsewhere.
Transfers are visible onchain; economic ownership is the difficult part. Exchange custody, cross-chain activity, unobserved wallets, and offchain agreements can remain outside your reconstruction. Do not treat a neat ledger as complete merely because it balances.
Practical case — illustrative
The creator moves 8m units to a supported side wallet and retains 2m. The pair still controls 10m until actual sales or outside transfers change it. Ten new recipient addresses receiving pieces of that inventory do not automatically mean ten new independent buyers.
Check your understanding — answered
Concentration falls on the scanner: decentralized? Only if genuine ownership changes are supported. Shared exchange funding: same dev? No. A buyer gets transferred tokens: zero cost basis? Not established; the economic purchase may have happened elsewhere.
Illustrations teach mechanisms; they are not live token assessments. Inspect can orient sampled trades; wallet attribution and control checks may require external evidence.