The KelpDAO exploit is a useful reminder that cross-chain risk is not only about bridge UI. A forged message or weak verifier setup can turn into ecosystem-wide contagion very quickly.
The part that stood out to me was how far the blast radius went: rsETH exposure did not stay isolated to one app. Markets around Aave, SparkLend, Fluid, and others had to react because one cross-chain failure changed the risk profile of the asset itself.
That is why I think the infrastructure conversation has to move from "bridging assets" to "verifiable execution across networks." Messaging security, solver design, monitoring, and pauser logic all matter.
SODAX is one project I have been watching in that context because it frames itself more as a cross-network execution layer than a simple bridge flow. It is live across 18 networks, which makes the design question more interesting: how do we route liquidity without recreating the same trust assumptions that keep causing bridge blowups?
Curious where people land on this. Are intents/solver networks a safer direction, or do they just move the trust problem somewhere else?
The KelpDAO exploit made cross-chain risk feel structural
byu/hazy2go inCryptoTechnology
Posted by hazy2go