BlogDev sniping
How to Find Dev Wallets on Pump.fun
How to find the dev wallet behind any pump.fun token, how to read a dev's launch history, and how to tell which devs are worth sniping.
By @ceosvex5 min read
Every pump.fun token starts with one wallet. It creates the coin, usually makes the first buy, and decides when to sell. Traders call it the dev wallet, the deployer or the creator.
If you can find dev wallets with a record of launches that go somewhere, you can be in their next token at the start. This guide shows how to find the dev wallet on any token, how to judge it, and how to build a list of devs worth sniping.
Almost every dev fails a strict record check
What a dev wallet is
The dev wallet is the address that signed the transaction creating the token. That is a fact on chain, not an opinion, so it is the one label in memecoins you can fully trust.
Two more terms you will see:
- Dev buy. The dev's own first purchase, often in the same transaction as the launch.
- Bundle. A group of wallets that buy together at launch. Sometimes they belong to the dev, which means the dev holds more supply than the dev wallet shows.
How to find the dev wallet of a token
- Copy the token's contract address.
- Open it in a Solana explorer or your trading terminal. Most terminals mark the creator on the token page and tag the dev's trades in the trade feed.
- If in doubt, go to the first transaction. In an explorer, scroll to the token's oldest transaction. The wallet that signed the creation is the dev.
- Open that wallet. You now have the address. The real work starts here.
How to read a dev's history
One launch tells you nothing. Open the dev wallet and look at every token it has created.
How many launches? One or two is not a record. You want enough launches to see a pattern.
How far do they go? For each launch, note the highest market cap it reached. Pick your own target first: the market cap at which your snipe would have paid. Then count how many of the dev's launches got there.
How fast does the dev sell? Find the dev's sell on each launch. A dev who dumps everything in the first minute ends the token. A dev who holds, or sells slowly, gives the chart room.
How clean is the launch? Look at the first buyers. If the first block is full of fresh wallets buying together, that is a bundle, and that supply will be sold into you. GMGN, for one, documents a token page view for insiders, snipers and the first 70 buyers, which is a good place to look.
Is it one dev or many wallets? Devs rotate wallets. Check where the dev wallet got its SOL. If the funding wallet has funded other deployers, you may be looking at one person with a longer and worse record than this wallet shows.
Which devs are worth sniping
A dev is worth sniping when four things line up:
- Repeat hits. A steady share of launches reach your target market cap, not one outlier.
- Recent hits. The good launches are from the last few weeks, not last quarter.
- Slow hands. The dev does not sell everything before a sniper could exit.
- Clean first block. Few bots and no large bundle sitting on the supply.
And one warning sign beats all four: a dev who launches many tokens a day and kills each within minutes. High count, zero survivors. Skip.
8 of 259,205 devs pass all 4 default checks
| Check | Devs left |
|---|---|
| All devs | 259,205 |
| 3+ launches | 32,175 |
| Reach $20K in half of their launches | 411 |
| First-second cap under $10K | 171 |
| Clean to $20K, drawdown 50% at most | 8 |
Where the manual method hurts
It is slow. A single dev with thirty launches is thirty token pages, thirty first blocks and thirty sell checks.
You find devs after the fact. By hand you start from a token that already ran and work backwards. You only meet devs whose winner you happened to notice.
Wallet rotation hides the record. Linking a dev's wallets through funding takes time and is easy to get wrong.
It ages. A dev who was good last month may have changed behaviour or stopped launching.
A dev record is built launch by launch
By hand
- Find the wallet that created the token
- Open every token it launched
- Note how far each one went
- Check each first block for bundles
- Find the dev's sell on each launch
- Start again with the next dev
From a dev list
- Set your target market cap
- Keep devs who reach it cleanly
- Paste their wallets into your sniper
The faster way
Hood Hunt keeps this record for you. It is analytics only: it does not trade and never connects to your wallet. It gives you profitable Sol wallets to copy and devs worth sniping, and you act on them in your own bot.
On the dev side:
- Which devs keep hitting your target. You set the target market cap. Hood Hunt shows which devs keep launching tokens that reach it.
- How clean the launches are. Every launch shows bots and bundles.
- How fast the dev sells.
- 35 metrics per dev, covering the last 30 days and rebuilt every hour.
So the four checks above are already done, and not only for devs whose tokens you happened to see.
All plans have the same features. See pricing.
What to do with a dev list
- Pick devs whose launches reach your target cap often and recently.
- Drop any with heavy bundles or instant dev sells.
- Put the dev wallets into a sniper. Blizz, for example, documents snipe orders that watch one creator wallet and buy its new launches on selected launchpads, pump.fun included. The full setup is in How to Snipe Dev Wallets on Solana.
- Set a fixed buy amount and an exit rule before the first snipe.
- Review the list weekly.
If you would sooner follow traders than launches, start with How to Find Profitable Sol Wallets to Copy Trade. New to all of this? Read How to Trade Memecoins on Solana first.
The short version
Finding a pump.fun dev wallet takes a minute: it is the wallet that created the token. Finding a dev worth sniping takes a record: many launches, how far they went, how clean they were, how fast the dev sold. Build that record by hand for a few devs, or open a list where it already exists for all of them.
Past results are not a promise of future ones. Memecoins are high risk, and you can lose everything you put in.