Two weeks after a $290M exploit drained KelpDAO through a single compromised Decentralized Verifier Network, LayerZero made it official: 1-of-1 DVN configurations are no longer sufficient. Every protocol on the network is now urged to migrate to a multi-DVN setup.

The window is open right now. Ankr is ready to come on as your additional verifier.

Why Choosing the Right DVN Is So Important for Protocols

The KelpDAO attack didn't exploit a smart contract bug or steal a private key. Attackers linked to North Korea's Lazarus Group compromised the RPC nodes feeding data to KelpDAO's sole verifier, fed it forged transaction data, and drained $290M before anyone could stop it. The protocol's entire security posture rested on one DVN. When that DVN was deceived, there was nothing left to catch the mistake.

A properly configured multi-DVN setup breaks this attack entirely. If two independent verifiers must agree before a message is accepted, an attacker needs to simultaneously compromise two organizations with completely separate infrastructure, key management, and RPC stacks. That is a categorically different problem.

But not all second DVNs are equal. If both verifiers share the same cloud provider, the same RPC sources, or the same security stack, a sophisticated attacker still has a single thread to pull. The independence of the second verifier is what creates actual protection.

Ankr’s Ironclad Security Posture

Ankr's DVN runs entirely on Ankr-operated infrastructure with independent RPCs, independent key management, and independent monitoring. A compromise of another operator's security stack cannot cascade into ours. Here is the full security posture:

• SOC 2 Type II certified -- independently audited, not self-attested
• Zero Trust access via Teleport and Tailscale -- every access request verified and scoped to minimum privilege, regardless of origin
• CrowdStrike Falcon with 24/7 managed SOC -- continuous endpoint monitoring and human-in-the-loop threat response around the clock
• KMS-backed worker keys; admin keys in Safe Multi-Sig -- keys are cryptographically segmented from the operational environment; privileged operations require multiple independent signers
• Annual independent penetration testing plus live HackenProof bug bounty -- adversarial pressure applied continuously, not just at audit time
• 99.99% uptime with contractual SLAs -- the nodes stay reachable even when an attacker is trying to knock them offline

With roughly 600 bare-metal hosts, 80-plus chains in production, and billions of RPC requests processed daily, Ankr’s service isn’t stood up in response to the news cycle, but rather an infrastructure foundation that has been running at production scale for years.

Ready to Eliminate Single-DVN Risk?

If your protocol is still running a 1-of-1 DVN configuration, that's a risk worth closing today. Ankr's DVN infrastructure is production-ready, independently operated, and built to the security standard your users deserve.

Reach out to sales@asphere.xyz to get Ankr configured as your second verifier.

Join the Conversation on Ankr’s Channels!

X | Telegram | Substack |  Discord | YouTube | LinkedIn | Reddit