RWA wrapper cascade
- 1Off-chain dependency
- 2Custody opacity
- 3Redemption gate
- 4Thin exit
- 5Forced markdown
visible risk
Risk is not one score. Bathymark reads backing, liquidity, yield, redemption, wrapper, and off-chain dependency as separate questions, then follows how one becomes the next.
What this page answers
Bathymark does not present products as free of risk. It marks what is visible, what the issuer claims, and what open data cannot show, and it reads exploits as the clearest record of where depth was actually taken.
Live readings, not a single score. Exploits from the open DeFiLlama ledger; peg and wrapper stress from the tracked set.
A weakness rarely stays in one box. These are the paths a single problem travels, the part most risk maps leave out.
Read each separately. The tag shows what it most often propagates into.
What the issuer claims the token represents, and what proof is attached.
Where exit depth lives: on-chain, CEX, OTC, redemption, or not visible at all.
Who can redeem, minimums, KYC, jurisdiction limits, and timing.
Where the return comes from and what dependency it adds.
Whether the token is a direct claim, fund share, receipt, note, derivative, or other structure.
When the source was last updated and what it actually covers.
The clearest risk record is where depth was actually taken. Read live from the open DeFiLlama hacks ledger, most recent first.
Source: open DeFiLlama hacks ledger. Amounts are the reported size at time of the exploit, not a live mark. An exploit is a fact about the past, not a forecast.

Risk is not one score. Bathymark separates the asset claim, the visible market, the legal wrapper, and the path out, then watches how a problem in one becomes a problem in the next.