$HAI powered security prediction market · Real DYOR is a skill. Learn it at Trust Army · DYOR Digest every Friday 👇

Joined November 2022
767 Photos and videos
Pinned Tweet
DYOR researchers, this is your time to shine⬇️
Think you can break down @centrifuge $CFG better than CT experts? Prove it. We’re hosting a PoV Report Tournament with @Core3io. Best @centrifuge report wins a speaker slot in our upcoming AMA X Space. Deadline: June 12, 12PM UTC Submit in PoV Chat➡️ bit.ly/CORE3chat
1
4
181
🚨JUST IN: xStocks $SPCX allocation came in tighter than demand. @krakenfx says unfilled $SPCX orders will be refunded. Users report filled accounts got ~4.2 $SPCX. CEXs like @Bybit_Official @binance @bitget and @MEXC are refunding the users' deposits. DYOR before FOMO.
2
1
5
284
World Cup season is here. Great for football. Still dangerous for your wallet. Every big event brings “official” coins, fan tokens, fake hype, and charts that look fun until they don’t. DYOR before the whistle blows on your bags.
2
5
67
Congrats to all $HAI stakers on the NEYRO win. No critical vulnerabilities were found. Your staked $HAI and $USDC rewards are now available to withdraw. Claim here👉 hackenio.cc/FlashPools ⚠️Flash Pools are high-risk, high-yield instruments in security prediction markets.
2
7
251
@SUPRA_Labs got hacked,” you already fell for the wrong headline. @DexlynLabs says malicious activity hit protocol liquidity wallets, not user funds. @SUPRA_Labs says the L1 stayed operational. So why did 192M $SUPRA move, who got hit, and what actually broke? 👇
2
3
11
550
What happened: two protocol-operated liquidity wallets were hit for about 192M $SUPRA. @DexlynLabs paused swaps, pulled protocol liquidity from affected pools, and started tracing the wallet path. The investigation is still ongoing👇
1
2
4
251
The recovery angle: return 85% within 48 hours, keep 15% as a white-hat bounty. If not, @SUPRA_Labs and @DexlynLabs say tracing, exchanges, and law enforcement continue. The real takeaway: don’t let CT collapse every exploit into “chain hacked.” Remember to always DYOR.
2
4
114
The uncomfortable @Raydium detail: the drained pools were not active. $1.34M loss came from five legacy AMM V3 pools phased out in 2021 and hidden from the official UI. Most people are focused on the exploit itself. The more interesting detail is where it happened. 👇
2
1
4
236
The bug was simple and brutal: fake LP tokens passed withdraw checks because the old program didn’t verify the real LP mint. @Raydium says current users are unaffected and treasury will cover losses. DYOR lesson: dead contracts can still hold real money.
1
1
141
Claude Fable 5 is out. Good news for DYOR: check a project's team, read the docs, and understand how the token works. Bad news for crypto security: smarter phishing, faster scams, and more convincing fakes. After months of exploits, is AI a shield or a weapon? Drop your take⬇️
3
2
10
149
How bull market feels when the whole groupchat got DYOR certified during the bear. Start trusting your own DYOR, not CT shills⬇️ ➡️hackenio.cc/WebTrustArmy

2
8
89
ethereum:0xfdffb411c4a70aa7c95d5c981a6fb4da867e1111 didn’t need a hack to lose 55% in under an hour. A $600M token move hit the bridge, traders saw a project-linked wallet, and panic did the rest. @SaharaAI says there are “no security issues” with token contracts or products. The chart heard the transfer first. 🧵⬇️
2
2
7
538
Context matters here. @SaharaAI says the 600M ethereum:0xfdffb411c4a70aa7c95d5c981a6fb4da867e1111 transfer was planned bridge liquidity for @chainlink CCIP, with another 150M still pending. No team or investor tokens moved, according to the team. Bad timing still creates real damage.🧵⬇️
1
2
2
240
The DYOR lesson: transfer can be planned and still wreck the market if nobody understands it. Before calling it a rug or buying the dip, check bridge contracts, unlock dates, liquidity depth, and official wallet movement. Learn to DYOR before reacting to headlines⬇️ hackenio.cc/WebTrustArmy

2
2
100
$HAEDAL is not another confirmed 8-figure drain like you thought it was. The @HaedalProtocol team reported an “unusual liquidity decline” in a small number of Haedal Vault pools and paused related contracts. That’s when DYOR matters: before the post-mortem fills in the blanks.
2
2
6
600
Haedal’s own line matters: “All direct losses related to this Vault matter will be fully covered by Haedal.” Good signal, but not the full answer. A paused vault still raises the real questions: which pools, what root cause, and how liquidity accounting failed.
1
219
Don’t read “limited impact” as “no risk.” Vaults are where users outsource strategy, liquidity, and execution. If that layer breaks, the token chart is the last place to look. For $HAEDAL, DYOR starts with the post-mortem, affected pools, and contract changes. DYOR before post-mortems are out⬇️ hackenio.cc/WebTrustArmy

188
$H got hit for $30M and it wasn’t some genius exploit. It looks like the oldest crypto failure in the book: private keys leaked. @terencekwok said keys tied to a Humanity Foundation member were compromised. That turns this from a price crash into a permissions story. 🧵⬇️
1
2
7
495
What happened: 17 project-linked wallets were drained. Attackers swapped $H into ETH/BNB, then a 100M $H mint on BNB Chain added fresh sell pressure. That’s the part retail should care about: private keys can become supply control if the setup allows it.
2
2
298
Humanity’s take: don’t interact with the bridge or liquidity pools until all-clear. @zachxbt also called the incident “possibly staged.” If a project’s key can drain wallets and mint supply, DYOR starts with admin permissions. Want to be ahead of the exploit game? ➡️hackenio.cc/WebTrustArmy

164