An attempted exploit on @ParallelMoney’s vaults was stopped automatically today. Hypernative detected the pattern and paused the relevant contracts within seconds. No funds lost. This comes after a brutal stretch for onchain security. April alone saw major incidents at Drift and KelpDAO, part of a wider surge in successful exploits. Attackers are coming prepared. The difference, increasingly, is whether the protocols are too. Credit to the Parallel team for having the monitoring and automated response in place before it was needed. That’s the work that doesn’t make headlines until it does.

Building your own monitoring sounds like a reasonable option. It isn't, and @gbvpzffd2r, Hypernative's CTO, made the case On The Cap Room. He walked through the math: even a basic balance-drop alert requires RPC aggregation, failover across multiple node providers, always-on sampling of every block, and infrastructure that never sleeps. Build it with a small team and it will be down 10-15% of the time. That's 10-15% of the time when your protocol is exposed and you won't know it. In the recent Parallels prevention, Hypernative detected and paused in seconds, coming before the attacker. The hacker fired. They missed. There is no grace period in this kind of infrastructure. On June 17, Dan is walking through the biggest attacks of 2026 in a session built around what was detectable beforehand and what would have stopped it. Register: buff.ly/FC1PsUg

The near-term opportunity in onchain finance is not exotic. It is stablecoins sitting in corporate treasuries with nowhere safe to go. Dan Caspi, CTO at Hypernative, mapped the trajectory at Consensus Miami: companies are getting paid in crypto, holding stablecoins, and discovering that moving them back offchain is more friction than it's worth. So the funds stay onchain. And once they stay onchain, the question becomes how to put them to work safely. That creates demand for everything from secure yield strategies to institutional-grade settlement rails. Two years from now, that infrastructure will not be a niche. It will be table stakes. On June 17, Dan is walking through the biggest attacks of 2026. The session is built around what was detectable beforehand and what would have stopped it. Register: buff.ly/FC1PsUg

The source chain held about 49 rsETH. The bridge message claimed 116,500. Every downstream check passed. Our research team walks through the whys of Kelp DAO attack on June 17, and what reconciliation at the policy layer looks like: buff.ly/FC1PsUg

Security vendors can curate their alert libraries after the fact. They can't curate what customers post on X during a live attack. A collection of real-time reactions from Hypernative customers, in their own words, at the moment it mattered. On June 17, the security team behind these successes is walking through the biggest attacks of 2026. The session is built around what was detectable beforehand and what would have stopped it. Register: buff.ly/FC1PsUg

Here is @GalSagie, CEO & co-founder of Hypernative, on what separates the institutions winning in digital assets from those that aren't. Full piece in the @ZodiaCustody ecosystem spotlight 👇 buff.ly/6Rb0LeM

The most unsettling fact about the Drift exploit has nothing to do with the $285M figure. It's the calendar. The attacker operated in the open for nine days. Wallet funding, nonce staging, a council migration that replaced four of five signers and zeroed the timelock. All of it onchain, all of it observable, none of it watched. The nine frames below walk the timeline day by day, then show where monitoring and enforcement would have cut it short. On June 17 at 2:00 PM UTC / 10:00 AM EDT, our research team does the full version live, with Hyperbridge and Kelp DAO alongside: buff.ly/FC1PsUg

One billion tokens minted against a circulating supply of 356,000. The mint passed the protocol's own verification. June 17: where the chain of checks should have broken, and didn't. buff.ly/FC1PsUg

Crisis post-mortems from asset managers don't usually go public. KPK's account of the April rsETH exploit does: roles, decisions, where automation stopped and humans took over, and every process change that shipped after. Hypernative is in their monitoring stack.