People are passing this around like Vitalik randomly deployed a contract on BSC today:
https://t.co/mkkKKGMOMA
He didn’t. It’s just a replay of an old Ethereum transaction.
Biggest tell: the exact same tx hash exists on Ethereum mainnet too:
https://t.co/hXXxwO2ogC
That only happens when someone rebroadcasts the exact same signed tx bytes on another EVM chain. In practice, that means this was an old pre-EIP-155 transaction, back before chain ID protection was added:
https://t.co/VCx1noeCGA
So nobody hacked Vitalik and he didn’t “deploy on BSC today.” Someone just found an ancient signed tx of his and replayed it on BSC.
The contract that appeared on BSC is here:
https://t.co/HNiytCzjjy
That address matches because contract creation addresses are deterministic from sender + nonce. Replay the same signed deploy at the same nonce on another EVM chain, and you get the same contract address.
The bytecode also looks ancient — it starts with 0x60606040, which is the old Solidity prefix. Modern Solidity usually starts with 0x60806040. So this really is old stuff, not some fresh Vitalik deploy.
The 4 tiny BNB transfers before the deploy are part of the same trick. The guy replayed older transactions first to walk Vitalik’s BSC nonce up to the right value, then replayed the deploy tx.
And the 25M AUTEST sitting in the contract is almost certainly just bait. Someone sent junk tokens there so they can post screenshots like “Vitalik holds AUTEST” and farm engagement from people who don’t know what they’re looking at.
@RuneCrypto_@NeoCallss@VitalikButerin
🚨defi just got slaughtered again — over $606 million hacked in April 2026 alone (across 12 incidents, already 3.7x the entire Q1 total).
and today Wasabi Protocol joined the bloodbath 😭
~ $5M drained in classic sloppy style — attacker compromised the deployer EOA, snatched ADMIN_ROLE, upgraded the WasabiLongPool contracts with their malicious version, and casually drained the vaults across ETH and Base.
upgradeable contracts + single god-key = the same messy plot twist every single time.
april is eating DeFi alive.
revoke everything if you touched it.
not your keys, not your perps 💅
MEXC sitting on $260m in USDC/USDe debt on aave v3 at 1.01 health factor. $110k daily interest accrual. health factor decays ~0.04% every 24 hours with no action. that's 6-8 days until forced liquidation if ETH doesn't move up and they don't add collateral. $260m in ETH/wBTC collateral hitting the market in a cascading liquidation is the next black swan everyone can see coming on-chain in real time. the kelp exploit was round one
Imagine every pixel on your screen, streamed live directly from a model. No HTML, no layout engine, no code. Just exactly what you want to see.
@eddiejiao_obj, @drewocarr and I built a prototype to see how this could actually work, and set out to make it real. We're calling it Flipbook. (1/5)
So let me start. DeFi is the future of the World Financial System. That's my belief, and this is why we are here.
This amount of absolutely preventable hacks we see in DeFi (with root causes attributable to CENTRALIZED points of failure) is enormous recently. This damages out industry, and I build for this industry. So I cannot remain silent.
Imagine an average grandma (mass adoption is here?) putting her life savings on Aave. And then BOOM, she cannot withdraw her funds on Monday. Aave (the biggest DeFi protocol btw) said it's operating as intended - just rsETH got exploited. rsETH said that all code is safu - just LayerZero bridge got hacked. LayerZero (the biggest bridge securing quarter of a trillion $) said that everything operating as intended. Yet, she cannot withdraw here funds. WTF? Are we industry of clowns?
But here's the thing. All issues like this should be prevented BEFORE they happen, not AFTER. Number of single points of failure should be reduced, not increased. When these points of failure are unavoidable - trust should be split. If there's a reliance on infrastructure - we should share best practices how to configure it. Not to mention that code should be very well checked - everyone gets that already.
We should probably come together and develop safety standards for DeFi. How to build safely, and how to verify safety. Probably everyone should bring their best practices, and the projects, auditors and risk assessment groups should know them. Maybe we need @ethereumfndn and @SolanaFndn bringing all the ecosystem projects to participate and come up with principles, rules and recommendations of safe building. And, perhaps, we can even learn something about protecting the few remaining centralized points of failure from traditional finance who have many more of those.
DeFi will win
Stablecoin security should not sit behind a paywall. That is the conviction Pharos was built on.
What started as a side project by @TokenBrice has become a daily resource for stablecoin users, researchers, and builders across DeFi. In less than two months, Pharos grew to track 205 stablecoins across every major chain, and it has stayed completely free.
During the USR incident, our depeg warning system flagged the risk early. Users who saw it avoided what came next. That is what Pharos exists to do.
Keeping that kind of infrastructure free and independent comes at a cost. Right now, @TokenBrice covers the gap directly out of pocket.
That is why we have opened a public funding page.
You can donate directly via wallet or through Giveth, which also supports recurring donations. Every contribution appears publicly on our donor wall. The funding page shows exactly where every dollar goes. No hidden costs, no surprises.
Our goal is to be fully self-funded by end of 2026. The core dashboard will always remain free. Future paid surfaces will cover high-frequency and heavy API usage only, so the tool that matters most to everyday users stays accessible to everyone.
Pharos exists to make stablecoin security visible to everyone. If that matters to you, here is how to help keep it that way.
defi summer 2.0 isn’t coming.
welcome to the 2026 defi bank run.
on April 18th $292 million vanished from Kelp DAO.
the attacker whispered sweet nothings into LayerZero’s EndpointV2.
fake cross-chain message accepted.
116,500 rsETH (18% of supply) printed out of thin air and dumped straight into aave V3 as collateral.
fake pink dust in.
real WETH out.
by Sunday morning the panic was real.
aave TVL cratered from $26.4B to ~$20B.
stablecoin pools hit 100% utilization.
withdrawals? frozen.
ETH/USDT/USDC liquidity? cooked.
just one bridge getting mogged and suddenly every depositor remembers they’re allergic to unbacked collateral.
tradfi takes weeks to panic.
defi does it in blocks.
The Hermes Agent Creative Hackathon starts now
16 Days, $25k in Prizes
Presented by @Kimi_Moonshot & @NousResearch
For the tinkerers pushing Hermes Agent into creative domains: video, image, audio, 3D, long-form writing, creative software, interactive media and more.
Show us what your Hermes Agent can do.
Details Below ↓
$4 for 150 Seedance 2 videos.
Cheaper than a coffee ☕️
• use HANASUPPORT26 on Mitte for $12 off
• get the Basic plan
• pay $4/mo after discount (instead of $16/mo).
all done via @mitte_ai