Dev wallet tracking: what to watch after a launch
The Editor·8 min read·Updated 31 Aug 2026
How to track a dev wallet: find the deployer, trace its funding, set alerts, and tell a real sell apart from a creator fee claim that only looks like one.
Find the deployer from the token's creation transaction, trace where that address was funded from, then watch three things: transfers of token supply out of it, sells into the pool, and connections to other launches. The hardest part is not the tracking. It is telling an actual sell apart from a creator fee claim, which looks similar and means something completely different.
Step 1: identify the deployer
On an EVM chain, open the token contract on the explorer. The overview panel shows a "Contract Creator" field with the deploying address and the creation transaction. That address is your starting point — not the token's largest holder, not the address in the project's Telegram bio.
On Solana, open the mint address on Solscan and find the transaction that created it. The fee payer on that transaction is usually the deployer. Also read the metadata update authority, which is a separate address in many launches and often the one that actually matters.
Then look for the split. On most current launchpads the deployer address, the fee-receiving address and the supply-holding address are not the same wallet, and treating them as one is the most common tracking error. Bags, for example, lets creators split fees across up to 100 creators, apps and wallets — there is not necessarily a single "dev wallet" to watch at all.
Step 2: trace the funding back
An address with no history tells you nothing. Where it came from tells you a great deal. Click back through the deployer's first inbound transfers until you reach the source. Three outcomes are common, and each means something different.
A centralised exchange withdrawal. The trail stops there. Exchanges do not publish who withdrew, so this is a dead end on-chain — but it is not useless information, because a fresh wallet funded directly from an exchange immediately before a launch is a wallet with no reputation attached to it and no intention of building one.
A bridge or a mixer. Same effect, more deliberately achieved.
Another wallet with history. This is the useful case. Follow it. If that wallet deployed other tokens, you now have a track record: how many launches, what happened to them, whether supply was sold. A deployer with a history of abandoned launches is the single most predictive signal available on-chain, and it is invisible to every automated safety score, because scanners read the token rather than the person behind it.
The same tracing method exposes bundled buying. If the top ten holders all trace back to one funding source, they are one participant with ten addresses, not ten holders. How bundled launches and sniper wallets work covers the pattern, and reading a token's holder distribution properly covers what the concentration numbers can and cannot show.
Step 3: distinguish a fee claim from a dump
This is where most dev-wallet accusations go wrong.
Modern launchpads pay creators a share of trading fees continuously. Those fees accumulate somewhere and get claimed as a transaction. On a block explorer, a claim is an outflow: value leaves a position and arrives in the creator's wallet. It looks, at a glance, exactly like the beginning of an exit.
On Pons.family, this is explicit and structural. Pons has no bonding curve and no migration — fixed 1B supply, the pool live from block one, buys and sells in the same pool forever. Its fees are 1% on pool trades and a 0.0005 ETH launch fee, split 70% creator / 30% protocol, and the creator's rewards accrue inside the token's locked position and are claimable at any time. When a Pons creator claims, value moves out of that position and into their wallet. No tokens were sold and no liquidity was removed. The Pons.family model in full sets out the mechanism.
Other venues produce the same ambiguity in different shapes. pump.fun takes a 1.25% total trading fee split between creator and protocol; Clanker takes a fixed 20% of the creator LP fee per swap and the creator keeps 80%. In each case the creator receives value periodically without selling a single token.
So the diagnostic question is not "did value leave the dev wallet". It is what asset moved, and where did it go:
| What you observe | What it probably is |
|---|---|
| ETH, SOL or WETH arriving in the creator's wallet from a fee position or claim contract | A fee claim. No supply sold |
| Token supply moving from the creator's wallet into the liquidity pool, with the quote asset moving back | A sell. This is the one that matters |
| Token supply moving from the creator's wallet to a fresh address, then into the pool | A sell, routed to obscure the source. Trace one hop further |
| Token supply moving to a locker, vesting or multisig contract | A commitment, not a sale — verify the destination contract |
| LP tokens moving out of a locker or dead address | Liquidity removal. Rare on venues where liquidity is structurally unremovable |
The rule that resolves almost every case: follow the token, not the value. A creator can be paid indefinitely without ever touching supply, and that is by design on most current venues. How memecoin creators actually make money covers the economics behind this.
Step 4: set alerts rather than refreshing a page
Manual checking fails at exactly the moment it matters, because a sell takes one block and you are asleep. Most block explorers offer address watchlists with email notification, and Solana analytics tools including Birdeye provide wallet tracking directly. Watch the deployer, its funding source, and any address holding a large share of supply.
Separately, monitor what you actually hold: position alerts catch the consequence even when you miss the cause, and The Crypto App's portfolio alerts handles portfolio tracking and price alerts across chains. A sharp move without news is often the first visible symptom of something you would have seen earlier on-chain.
What dev wallet tracking does not catch
Tracking one address gives a partial view, and the gaps matter more than the coverage.
Multiple wallets. A creator who intends to sell quietly does not sell from the deployer. They distribute supply to fresh addresses at launch — often in the same block as the deploy — and sell from those. Tracing that requires cluster analysis rather than address watching. Bubblemaps is the standard tool for visualising wallet clusters and bundled supply, and nothing else substitutes for it.
Pre-launch distribution and OTC sales. Supply allocated before the pool went live may never pass through the deployer at all, and an OTC deal transfers ownership with no pool transaction — you see a transfer between two addresses and no sell.
Intent. A dev wallet that has done nothing for six weeks has done nothing for six weeks. That is not a commitment, and past inactivity does not constrain the next transaction.
Everything that is not the dev. A token can go to zero with a completely inert creator wallet, and most do. Watching one address is a check against one specific failure mode — the slow, quiet exit covered in the difference between a soft rug and a hard rug — not against the base rate.
And attribution is inference, not proof. A wallet cluster is a pattern in transaction data. It suggests common control; it does not establish it. Say "these addresses share a funding source" rather than "the dev is dumping", because the first is a fact and the second is an accusation you cannot support from on-chain data alone.
Frequently asked questions
How do I find the dev wallet for a memecoin?
On an EVM chain, open the token contract on the block explorer and read the "Contract Creator" field. On Solana, open the mint on Solscan and find the fee payer of the creation transaction, then check the metadata update authority separately. The deployer, the fee recipient and the supply holder are often three different addresses.
How can I tell if the dev sold?
Look for token supply moving from a creator-linked address into the liquidity pool, with the quote asset moving back. Value arriving in a creator's wallet from a fee position is a fee claim, not a sale — on Pons, for example, creator rewards accrue in the token's locked position and are claimable at any time without selling anything.
Is claiming creator fees the same as rugging?
No. On most current launchpads creators earn a share of trading fees continuously and claim them as a separate transaction. That is the venue's designed compensation mechanism and involves no token supply and no liquidity. It looks like an outflow on an explorer, which is why it is so regularly misreported.
Does a dormant dev wallet mean the token is safe?
No. It means one address has not transacted. Supply may have been distributed before launch, sold from other wallets, or transferred off-chain. And the most common outcome for a memecoin — losing most of its value on falling demand — requires no action from the creator at all.
The part of this a creator can prove instead of being watched for
Everything above is a buyer inferring intent from transaction patterns because there is nothing better available. If you are launching, you can remove one whole branch of that investigation. Team Finance's liquidity lock — built by TrustSwap, which also builds Meme Central — locks LP tokens for a fixed term on Ethereum, Robinhood Chain, Polygon, Base and BNB and displays as a verified badge on your token's page in the Meme Central's live feed of launches. It applies to a token from any launchpad, including after launch. It does not cover your token allocation, which is exactly what everyone reading this article will be watching.
Nothing here is financial, legal or tax advice. Memecoins are extremely high-risk: most lose most of their value, and the majority of tokens launched never reach a decentralised exchange at all. Never spend money you cannot afford to lose entirely. Meme Central does not recommend any specific token. Data described as Meme Central's own reflects tokens indexed by Meme Central and is not whole-market data.
