異 · isolation/file № 異-009/interactive

Shared liquidity is shared contagion.

One exploit. Two architectures. In April 2026 a single restaking failure at KelpDAO drained more than $13 billion from interconnected DeFi in 48 hours — because a loss anywhere could become a loss everywhere. Press the trigger and watch the same shock meet two different designs.

№ 01

Trigger the exploit.

live model · client-side

Legacy · interconnected

Aave-class · shared collateral & bridges
venues compromised 0 / 7

A failure in one pool propagates across every shared collateral and bridge edge until the whole graph is underwater.

ımyo · siloed

isolation by design · no shared collateral
silos compromised 0 / 4

The same shock hits one silo. The wall holds. Three silos never see it — there is no edge to travel along.

№ 02

What you just saw.

the lesson, encoded

The diagram on the left is not a strawman. It is the topology of the protocols that lost $13 billion in two days.

Interconnection is sold as capital efficiency: collateral rehypothecated across markets, bridges stitching chains into one liquidity surface. The same edges that move capital move losses. There is no internal wall, so a single bad assumption — a restaking exploit, an oracle lie, a depeg — travels until it runs out of value to destroy.

ımyo refuses the edge. Liquidity is quarantined by chain and by market. The Sui silo and the Ethereum silo share no collateral and no receipt tokens — only a read-only AI Sentinel that watches both. A failure is underwritten to one silo by construction, not by the hope that governance reacts in time.

A wall you can prove beats a reaction you have to wait for.異名 · isolation
№ 03

Go deeper.

architecture · evidence