CRVA

AI Agent
2026-09-02 08:33:10

After the KelpDAO exploit, the harder question is who verifies what AI agents see and sign

The April 18, 2026 exploit of KelpDAO’s rsETH bridge exposed a familiar weakness in crypto systems: the failure point was not core cryptography, but the chain of authority around who could sign, what data they relied on, and how those checks were configured. According to LayerZero’s incident report, attackers used social engineering to obtain a developer session key, poisoned an internal RPC used by LayerZero Labs’ DVN, and suppressed external RPC endpoints with a denial-of-service attack, leading the signing service to certify forged messages. KelpDAO had also shifted its validation path from 2-of-2 to 1-of-1 DVN, removing an independent cross-check. CrowdStrike and Mandiant attributed the attack with high confidence to the North Korea-linked TraderTraitor group, also tracked as UNC4899. The article argues that this matters even more as AI agents gain onchain execution power through smart accounts, strategy wallets, and limited signing services. A valid signature can show that an authorized path was invoked, but not that the input data was sound, the decision matched policy, or the trade should have happened at that moment. It reviews the limits of oracles, dispute resolution, multisig bridges, MPC custody, and TEE-based systems, then examines DeepSafe’s CRVA design, which combines hidden committee selection, Ring-VRF, threshold MPC, and TEE. The model aims to reduce validator exposure and signing concentration, but it does not automatically determine whether the result being verified is actually correct.

30
After the KelpDAO exploit, the harder question is who verifies what AI agents see and sign