Who lends
Anyone holding a position whose real backing is two or three steps away.
- Lending and money markets
- Credit and undercollateralised lending protocols
- Curated and managed vault operators
- Perpetual and margin venues
Every alert answered with the question that follows it. An alert that says this pool is draining is a pager. An alert that says this pool is draining, here is the collateral downstream of it, here are the protocols that follow, in this order, and here is what it is worth, is a decision.
Start with what you hold and follow it down. A wrapped token is a claim on a staked position; that position sits in a lending market; that market has lent against it. Four steps out, your money depends on something you never chose. Exposure Map reads that whole chain of claims out of live chain state and answers what every alert raises and almost none answer: what does this cost me, and who else does it reach? It also measures what getting out would really cost, which is not pool size but the price you would actually receive today, and whether what is supposed to back a wrapped asset is there.
Five surfaces, named. Anything outside this list is not covered by this wall; the perimeter page says which one covers it.
Anyone holding a position whose real backing is two or three steps away.
Anyone who has to defend a collateral factor in a meeting.
Anyone answerable for a balance sheet that reprices when something upstream breaks.
Anyone whose token is collateral in a market they do not control.
Public, dated and sourced. Open a row for what happened and for what would have caught or refused it.
Of the 116,500 rsETH taken from the Kelp DAO bridge, 89,567 was deposited straight into Aave as collateral and borrowed against for $190M of WETH. Aave's contracts were never touched. Aave, SparkLend and Fluid all froze their rsETH markets; at least nine protocols were affected.
Proof of backing is measured on chain for wrapped and bridged assets: minted supply against verifiable backing, continuously. The moment supply outruns backing, every market holding that asset is downstream of a fact the graph already knows, and the look-through query answers who is exposed and for how much.
It takes more than one wall. The clearest case for the compounding argument. Ops Monitor sees the cause, Asset Ratings would have refused the structure, and Exposure Map tells the nine protocols downstream what it costs them.
Chainalysis on the Kelp DAO bridge exploitStream Finance disclosed a $93M loss and froze withdrawals. Elixir's deUSD had lent roughly sixty-five per cent of its backing to Stream through private lending vaults; it fell about ninety-eight per cent and was wound down. Some lending markets had hard-coded the affected collateral at a dollar, so positions could not be liquidated and the bad debt stayed invisible.
This is the look-through question. A deUSD holder held a claim on a loan to a fund manager, two steps removed, and the graph follows the chain of claims to the bottom rather than stopping at the wrapper. Where a price is an assumption rather than a measurement, the surface says so in the same type as the number.
Elixir winds down deUSD after the Stream Finance lossThe protocol priced an asset as the median of eleven sources, which reads as robust. Five of those eleven were Curve pools holding the same pair family, and one flash loan moved all five at once. The median followed, borrowing opened at a manipulated price.
Independence is a property of the graph, not of a count. Reading each source back to the venue state it derives from shows five of eleven collapsing to one dependency. Depth is measured from live venue state, so the cost of moving those pools is a number rather than an assumption.
QuillAudits on the UwU Lend exploitA reentrancy lock that silently did nothing in three versions of the Vyper compiler let attackers drain several stable pools. The direct loss was not the dangerous part: Curve's founder had pledged roughly 427 to 460 million CRV, close to half the circulating supply, against more than $100M of debt across Aave, FraxLend, Abracadabra, Inverse and Silo.
The exposure at risk was a multiple of the amount stolen, and it sat on balance sheets belonging to protocols the exploit never touched. Contagion order answers which of those five markets becomes unhealthy first and at what price; exit depth answers what liquidating into the thinnest book of the year would cost.
Chainalysis on the Curve Finance liquidity pool hackThe attacker used Alpha Homora's leveraged lending to borrow and lend repeatedly against Iron Bank, then walked away. Alpha Homora was the protocol with the flaw. Iron Bank was left holding the debt, and it had done nothing wrong at all.
Two protocols were coupled by a credit line most people reading either dashboard could not see. That coupling is an edge in the graph, carrying its source contract, chain, block and read time, so who is downstream of whom is answered from chain state rather than a vendor's feed.
Halborn on the Alpha Homora hackShared substrate, not features of this wall. Every layer below is already paid for by the first wall in your scope.
The graph is extracted from chain state at a pinned block, with provenance on every edge, never from a vendor feed. Exit liquidity is read as a depth curve from live venue state rather than a headline pool size. Where a number is an estimate, the surface says so in the same type as the number.
Individually, or bundled with the walls beside it.
Look-through exposure to the bottom of the chain of claims, real exit depth at size, contagion order, and proof of backing for wrapped and bridged assets
One subject to everyone downstream, quantified and with the connecting path, plus the whole-position risk feed. Both belong to this wall and arrive with it
It is what turns detection into severity. A response ladder cannot act beyond notify without knowing what is at stake, and this is where that number comes from. It also gives risk committees a collateral parameter they can defend, with the working shown.
Fuga Labs is read-and-attest, never custody-and-execute.
A scoping call maps this wall against what you run and says where it reaches and where it stops. Nothing is provisioned until that is agreed in writing.