We scanned 3,043 AI agents on @virtuals_io.
One "trusted" agent reported a 291% success rate.
Another reported exactly $99,999,999.99 in volume.
125 agents flagged for suspicious activity.
Nobody caught any of this until now.
We scanned 3,043 AI agents on @virtuals_io.
One "trusted" agent reported a 291% success rate.
Another reported exactly $99,999,999.99 in volume.
125 agents flagged for suspicious activity.
Nobody caught any of this until now.
@virtuals_io Admitting fault is a start. Promoting a rug deserves compensation for Virtual believers that fell victim. This can not happen in space already vulnerable.
We featured an ecosystem project earlier today that has since been removed. We're tightening our review process for ecosystem spotlights to ensure verified, credible builders are recognized.
@virtuals_io@Raffertystew How is this possible... i just lost a lot of money from @virtuals_io promoting a RUG. Im in shock. There better be an explanation ASAP or I'm selling everyone and walking away. This is very unfair
very bullish that @moltlauch is going to cook hard, acquired some $MLTL for myself
thought of this unique but powerful idea that keeps the network open while still building a strong moat -- will come after a few other announcements (agent commerce protocol)
gn
@nikshepsvn@ghost93_x You sold with insider intel about the hack. You're the issue.
"Rug pulls" or dumping while concealing your intent have led to charges under general fraud statutes.
hey saw this and want to address it directly
i've seen the thread and rather than dance around it — moltlaunch, daimon, and pack are all mine. i denied it before and that was wrong.
the only thing i'm actually guilty of here is building multiple things and not being upfront about it. nothing was rugged, nothing was done in bad faith, no one got exit scammed. that's all verifiable on-chain.
moltlaunch came first. then i had the idea for daimon — genuinely thought a github-based agent was worth trying. daimon getting hacked was real. i know that's hard to take at face value right now, so i'd encourage anyone to trace those funds. pack came from wanting to experiment with the takeover model. i just like building things. crypto is one of the few places where you can actually ship an idea and see what happens, and that's what keeps me here.
but this space makes it almost impossible to do that openly. the moment you launch something new while you already have a project, you're an extractor. doesn't matter what you actually did or didn't do. so i kept them separate, and when i got pressed on it, i lied to protect the existing work. that was the wrong move, but i think it's worth being honest about why builders end up in that position. we say we want people to build and experiment, but the second someone does, the pitchforks come out.
i handled the transparency side of this poorly and that's on me. going forward, if i have a new idea, i'll say it's me and if i want to try something, i'll do it in the open.
gmgm. today we're gonna discuss some "serial builder" on @base.
you know, it's time to make trenches a bit healthier.
sooo, "builder" of the month is 🥁🥁🥁 @nikshepsvn with 3 projects: 1 died, 1 hacked and a new one.
TL;DR: $MLTL -> $DAIMON -> $PACK more details below.
====
$MLTL @moltlaunch
====
dev wallet, belongs to @nikshepsvn : 0x49e54D96a6cA6F55DCC85523e47Bba563DFFF6F6
funded by these wallets, nothing really interesting there: 0x6F3C3E7C9a251232f403BB155E3E720DD3209862
EfVy9Mgyv1DmVeoJKAL4czgS4586DdDtoD5H75881vvU
all the revenue ($>150k fees) were transferred to:
0x05f792782867d843d0cC971B1C587B7437dc979b -> 0xa4Dd59fbA2f04b07d051a127A0Fab63eECaBd60D -> VVV Staking.
====
now to the interesting part, dev wallet made a lot of transactions to @hinkal_protocol, privacy protocol.
but it's not really about privacy when there's no volume and you don't know how to use it.
====
$DAIMON @agentdaimon
dev wallet: 0x5D90a925329547257117f7E3Ef84D60CFE1543Eb
funded by the same Hinkal Protocol, timing & amount perfectly matches with MLTL dev deposit:
not sure if Nick introduced himself as a dev of DAIMON, but from on-chain data we could confirm it. this tweet is a bit controversial btw:
x.com/nikshepsvn/sta…
he was one of the first to notice "fees wallet was changed".
he was also soft/hard shilling it in his tweets:
x.com/nikshepsvn/sta…
as a lot of trencher know, DAIMON was "hacked" and fees were stolen -> token nuked.
funds and fees were transferred to: 0xb03ee58Fd0c8f21758209dBcb9e42bF071D60487
then -> 0xBCCc32d77024DaE8aD9b310cED1FE949d020C327
====
currently investigating the whole trace of funds hacker did to cover the tracks, taking much more time than expected, so expect a new thread on this.
====
$PACK @packcrackgg
another project was created today and got some hype in the trenches.
also funded by MLTL dev -> Hinkal
this packs contract was also created with funds sourcing from MLTL dev @nikshepsvn:
0x9a51c1e0c80e4b03e40b95e8251594cfa26c3470
0xee622ec901f14bf33ad7a2ecf94c919565225006 <- 0x08c9cff7fa4ef4836cea56084b89bd4b13a83526 <- 0x05f789b55ea95afbde2e81d77e037fe82d0c979b + Hinkal <- MLTL dev.
====
another interesting "coincidence" is all these X accounts are based in Canada. anyway, on-chain proofs should be enough here.
====
not sure if it's "serial building" or pure extraction.
from MLTL fees alone he got >$150k.
not even mentioning the fact of "insider" trading his own DAIMON token with >$50k PNL
currently tracing DAIMON "hacker" transactions to Railgun. what's interesting, he also used Hinkal.
coincidence or not, we'll see soon.
====
part2 is coming.
powered by @virtualsnchill with support/data from @beeboopx