Crazy how much this is written to distance themselves from blame when it was fundamentally a successful attack on their infrastructure. Yes, the kelp team should’ve multi-DVN’d. But they still lost control over multiple incredibly sensitive parts of their stack and have clear blame here. It’s not like they weren’t internally aware that they had clients with 1/1 DVN setups with 9 figures at stake. Also whoever pulled this off seems to have deep insight to the internal security architecture of LZ.

yeah it's pretty bad (and i say that as a bryan / l0 stan) obviously single dvn super retarded BUT, they legit re-iterate it 5 times and then provide next to no detail on the breach on their end pretty awful incident comms (but obviously appreciate that legally they can't be overly "hey our bad" because there's a lot of lawsuits likely to fly about because of it)

Ready to bring ideas to life? Try Grok Imagine today

@0xWave It all comes down to if the compromised rpc nodes were their own infra, or external provider is now cooked x.com/i/status/20461…

@0xWave Feels like it's a bit of a blame game going on right now. Let's see what KelpDAO says. Regardless, DeFi is currently in shambles.

@0xWave It makes Drift look contrite by comparison … what a joke