We've spent the past year building DeFade, shipping new features and improving it every single day. We did it for one reason: to make the trencher safe.
Today it's the first scanner with all these modules in one scan. Nobody else puts this much in one place, and nobody else goes this deep.
We were also the first to detect Proxima and Sumo, the launch-bundling tools behind a lot of the coordinated launches that get people farmed.
When a wallet ran one of them on a token, DeFade names the tool right next to the wallet.
One scan shows you the bundles, including delayed sweeps and the real peak exposure. It shows the snipers and sybil bands, meaning wallets funded by the same hand. It traces funding origin across multiple hops, so a rotated wallet still gets caught, and it catches wallets running the same bot config through their fee fingerprints. It pulls the dev wallet and deployer history, so you know if this person has rugged before. And it flags the fresh and virgin wallets farming the chart.
It runs on Solana, ETH, Base, BSC, Robinhood, Arc, HyperEVM and more to come, on the web, in a Chrome extension, on mobile and in a Telegram bot. We also built MCP connectors, so you can plug DeFade straight into Claude or ChatGPT and run a full scan from inside the conversation. Ask your AI about a contract and get the real answer, backed by the same scan.
And yes, we're launching a token. We waited on purpose. Most projects launch a token first and build something around it later. We did it the other way around: a year of building, a working product people already use, and only now the token. It never made sense to us to ask for your trust before there was something to trust.
We're in the trenches too, and we were tired of watching people get rugged by wallets that were obvious in hindsight.
Rugs keep evolving, so we keep shipping.
Paste a contract. Get the truth.
https://t.co/8E3Sk7TVaq
DEFADE is growing up.
We started as a memecoin analyzer because that is where the rugs were. Along the way we built something bigger: an engine that reads wallets. It shows who funded them, which "independent" holders are one person, and where the money came from and where it went.
That engine isn't just for memecoins.
We're working on taking DEFADE across the whole market, from the newest launch to the oldest coin on chain. Any asset, any wallet, any entity: who holds it, who's moving it, and where it's going.
Memecoin scanning stays at the core and keeps getting better.
The team is heads down on this. More soon.
Read the wallets, not the promises.
@WalkDog1984@amaionx 🤦🏼♂️ what? lol ive replied to every single question you (grok) have asked. The worst thing about ai is that it gives people an opinion when without it they wouldn’t say shit. Good night!
Omg bro i’m done. I can’t deal with these long posts from Grok anymore. I’ve replied to this at least 3 times, and you keep asking the same things in different ways. You feed Grok everything and it gives you a reply. I fucking check everything myself and i’ve wasted my entire evening going back and forth with you. It’s actually 3:10 am here in London and im going to sleep. I don’t really want to keep arguing with Grok over a token thats down 90%
I can’t see who holds the keys, nobody can, so i’m not claiming who pressed sell. What i showed is the link and you confirmed it. Both wallets the dev sends his fees to are tied to the launch snipers. 0x9877e7237602e8fb22b6a1b6ea0fcd8def052df7 was first funded by 0xd58bee341b8844b0b195c0e706303e7ace4c8f97 the same wallet that funded the 3% sniper 0xd0c9d75c143bc7e42343a985d3b8cfd8ac2dc144 and launched another robinhood:0xc32ab2e562ade6fba6d3d1e3960d49b0957ef645 27 min before the real one. And 0xe8552d7c925eaa29fd8d44b1e7567937cbe784d1 got ETH from 0x2bc39ffe4a3e746c88381325d38d5344ccf5fb22, the wallet that sold the 1.41% bundle bag. Those snipers sold 74 times between Oct 1 and 4. So the question isn’t for me its for the team: why are the devs fee wallets connected to the launch snipers? You asked for the path, you got it and agreed. Don’t move the goalposts now.
Show me where i said “last month”, you can’t lol. My post was about the launch and the dev linked to the bundle/snipers and you confirmed every point. The dev sends his fees to 0x9877e7237602e8fb22b6a1b6ea0fcd8def052df7, and the very first ETH that wallet ever got came from 0xd58bee341b8844b0b195c0e706303e7ace4c8f97, the guy who launched the other robinhood:0xc32ab2e562ade6fba6d3d1e3960d49b0957ef645, the same guy who funded the 3% sniper 0xd0c9d75c143bc7e42343a985d3b8cfd8ac2dc144. And the 1.41% bundle bag from 0xa2d83134b2f609ae1f9e47cb701c84838c89e8df got sold with the ETH going to 0xe8552d7c925eaa29fd8d44b1e7567937cbe784d1, the other wallet the dev sends his fees to. Bundles linked to the dev’s wallets thats what i said thats what your own Grok confirmed
@amaionx@WalkDog1984@LiegeAgents LMAO what? your own Grok bot agrees with almost everything i says lol. Read it again, it literally calls the claim ACCURATE and calls those wallets a “team-linked EOA cluster”. I know you are now arguing with your bot to come up with something super smart😂😂
Never said those wallets still hold a bag read my post again. I said they dumped thats the whole point they hold 0% because they already sold it to the people who bought the pumps. Your own bottom line say "There IS a verified on-chain graph" and points 1 to 5 are literally my post. We agree on the facts you just don't like what they show lol
You asked for a path from the bundle wallets to a known team wallet, so here it is, every tx is on chain. robinhood:0xc32ab2e562ade6fba6d3d1e3960d49b0957ef645 launched on 1 Oct 2026 at 03:10:49 UTC from the dev wallet 0x12b25cf23e011fb247ac37ffdf559c958e6ddb4d. 27 minutes earlier, at 02:43:55 UTC, there was another robinhood:0xc32ab2e562ade6fba6d3d1e3960d49b0957ef645 launched on the same launchpad by a different wallet, 0xd58bee341b8844b0b195c0e706303e7ace4c8f97, and 17 of the real robinhood:0xc32ab2e562ade6fba6d3d1e3960d49b0957ef645 bundle wallets aped that one too. Less than a minute after launching it, that wallet sent ETH to 0x9877e7237602e8fb22b6a1b6ea0fcd8def052df7 (tx 0xb335c8417e2e96a0c8dfa451a854c43cb6e98cba84e0e875ac0c0d8609385dda), a wallet the dev wallet later sent ETH back and forth with more than 50 times. Then at 02:51 UTC it sended 0.117 ETH to 0xd0c9d75c143bc7e42343a985d3b8cfd8ac2dc144 (tx 0x632ef4779e529a2a9fa545b66ac4e5ca02de92bf66e2b6f726f72f6c9fc93c6b), and 19 minutes later that wallet sniped 3% of robinhood:0xc32ab2e562ade6fba6d3d1e3960d49b0957ef645 supply within 2 seconds of launch. Now follow the money. After launch the dev wallet sent 10 ETH to 0xe8552d7c925eaa29fd8d44b1e7567937cbe784d1. Bundle wallet 0xa2d83134b2f609ae1f9e47cb701c84838c89e8df sniped 1.41% of supply 1 second after launch and moved the bag to 0x2bc39ffe4a3e746c88381325d38d5344ccf5fb22. That wallet dumped it and then sent ETH to the same wallet the dev sends his ETH to, 0xe8552d7c925eaa29fd8d44b1e7567937cbe784d1 (tx 0x1448630aa3795a2975c8d102cc8995d754a88083f8acb17f416f93ba766cd430). None of these are exchanges or bridges, just normal wallets trading memecoins. The dev wallet collected 18.15 ETH in launchpad fees, spent 5 ETH buying back and burning, and sent about 13 ETH to other wallets, 10 of it to 0xe8552d7c925eaa29fd8d44b1e7567937cbe784d1. Lots of bundle wallets came in through bridges, so i can’t say all of them are linked. But you asked for a path to a team wallet, and there it is, all on chain, check it yourself.
You asked Grok, i checked on chain. Your own report confirms every single point, you even call it a “team-linked EOA cluster” yourself lol. At least read what your Grok bot says instead of just posting it blindly. Fair on 0x2bc39ffe4a3e746c88381325d38d5344ccf5fb22, it sold part of the bag before sending ETH to 0xe8552d7c925eaa29fd8d44b1e7567937cbe784d1 and the rest after, it dont change nothing. But “nothing to do with investors”? Those wallets hold 0% because they already dumped on investors, thats the impact. 0xd58bee341b8844b0b195c0e706303e7ace4c8f97, the wallet that launched the other $LIEGE 27 min before, funded 0x9877e7237602e8fb22b6a1b6ea0fcd8def052df7, the same wallet the dev sent ETH back and forth with more than 50 times. Then it sent 0.117 ETH to 0xd0c9d75c143bc7e42343a985d3b8cfd8ac2dc144, at launch that wallet aped 0.115 ETH and sniped 3% of supply in the first 2 seconds, then dumped it, part directly and part through 0x38b48c3ac0e6fda58d50581823da4a579a8db633, for about 1.93 ETH. 0xa2d83134b2f609ae1f9e47cb701c84838c89e8df put in 0.06 ETH and the bag got dumped for 0.52 ETH, with ETH going to 0xe8552d7c925eaa29fd8d44b1e7567937cbe784d1, the same wallet the dev sent 10 ETH to. Supply bought for cents at launch by wallets linked to the launcher and dumped on the chart, guess who was buying them bags. Thats the “every pump got dumped” holders felt. By the way, this is what we are arguing about:
You asked Grok, i checked on chain. Your own report confirms every single point, you even call it a “team-linked EOA cluster” yourself lol. At least read what your Grok bot says instead of just posting it blindly. Fair on 0x2bc39ffe4a3e746c88381325d38d5344ccf5fb22, it sold part of the bag before sending ETH to 0xe8552d7c925eaa29fd8d44b1e7567937cbe784d1 and the rest after, it dont change nothing. But “nothing to do with investors”? Those wallets hold 0% because they already dumped on investors, thats the impact. 0xd58bee341b8844b0b195c0e706303e7ace4c8f97, the wallet that launched the other $LIEGE 27 min before, funded 0x9877e7237602e8fb22b6a1b6ea0fcd8def052df7, the same wallet the dev sent ETH back and forth with more than 50 times. Then it sent 0.117 ETH to 0xd0c9d75c143bc7e42343a985d3b8cfd8ac2dc144, at launch that wallet aped 0.115 ETH and sniped 3% of supply in the first 2 seconds, then dumped it, part directly and part through 0x38b48c3ac0e6fda58d50581823da4a579a8db633, for about 1.93 ETH. 0xa2d83134b2f609ae1f9e47cb701c84838c89e8df put in 0.06 ETH and the bag got dumped for 0.52 ETH, with ETH going to 0xe8552d7c925eaa29fd8d44b1e7567937cbe784d1, the same wallet the dev sent 10 ETH to. Supply bought for cents at launch by wallets linked to the launcher and dumped on the chart, guess who was buying them bags. Thats the “every pump got dumped” holders felt. By the way, this is what we are arguing about:
Respectfully, an AI’s opinion isn’t an audit. DeFade’s full modules are behind PRO, so Grok couldn’t have verified them.
And let’s remember what this is about: robinhood:0xc32ab2e562ade6fba6d3d1e3960d49b0957ef645. We gave it an EXTREME RISK score, and it went from $650K to $48K market cap. Looks like we got it right. In another post I already shared the on chain proof and the tx showing the dev involvement.
Now, Grok’s points one by one.
No risk tool is 100% accurate, which is why every flag shows the on chain data behind it so you can check it yourself.
Our rugs write up looks at tokens that rugged and what our scans showed before the rug. If you know a rug we missed, post the CA.
Yes, the rug probability is interpretive. The reads are facts and the score weighs them. That’s the design.
When data can’t be resolved, we say “unverifiable” instead of guessing.
DEFADE analyzes and flags risk. It’s never a buy or sell signal, and we’ve never presented it as one.
Locked LP and revoked mint don’t mean safe. We agree, and that’s why we look past those checks, at bundles, snipers, fresh wallets dev history and more.
The trade buttons are an option, not advice. The scan is the same whether you trade or not.
You asked for a path from the bundle wallets to a known team wallet, so here it is, every tx is on chain. robinhood:0xc32ab2e562ade6fba6d3d1e3960d49b0957ef645 launched on 1 Oct 2026 at 03:10:49 UTC from the dev wallet 0x12b25cf23e011fb247ac37ffdf559c958e6ddb4d. 27 minutes earlier, at 02:43:55 UTC, there was another robinhood:0xc32ab2e562ade6fba6d3d1e3960d49b0957ef645 launched on the same launchpad by a different wallet, 0xd58bee341b8844b0b195c0e706303e7ace4c8f97, and 17 of the real robinhood:0xc32ab2e562ade6fba6d3d1e3960d49b0957ef645 bundle wallets aped that one too. Less than a minute after launching it, that wallet sent ETH to 0x9877e7237602e8fb22b6a1b6ea0fcd8def052df7 (tx 0xb335c8417e2e96a0c8dfa451a854c43cb6e98cba84e0e875ac0c0d8609385dda), a wallet the dev wallet later sent ETH back and forth with more than 50 times. Then at 02:51 UTC it sended 0.117 ETH to 0xd0c9d75c143bc7e42343a985d3b8cfd8ac2dc144 (tx 0x632ef4779e529a2a9fa545b66ac4e5ca02de92bf66e2b6f726f72f6c9fc93c6b), and 19 minutes later that wallet sniped 3% of robinhood:0xc32ab2e562ade6fba6d3d1e3960d49b0957ef645 supply within 2 seconds of launch. Now follow the money. After launch the dev wallet sent 10 ETH to 0xe8552d7c925eaa29fd8d44b1e7567937cbe784d1. Bundle wallet 0xa2d83134b2f609ae1f9e47cb701c84838c89e8df sniped 1.41% of supply 1 second after launch and moved the bag to 0x2bc39ffe4a3e746c88381325d38d5344ccf5fb22. That wallet dumped it and then sent ETH to the same wallet the dev sends his ETH to, 0xe8552d7c925eaa29fd8d44b1e7567937cbe784d1 (tx 0x1448630aa3795a2975c8d102cc8995d754a88083f8acb17f416f93ba766cd430). None of these are exchanges or bridges, just normal wallets trading memecoins. The dev wallet collected 18.15 ETH in launchpad fees, spent 5 ETH buying back and burning, and sent about 13 ETH to other wallets, 10 of it to 0xe8552d7c925eaa29fd8d44b1e7567937cbe784d1. Lots of bundle wallets came in through bridges, so i can’t say all of them are linked. But you asked for a path to a team wallet, and there it is, all on chain, check it yourself.