Quant ={Rheo}

All about big numbaz and big booty bishes /./ IYKYK

Building → @rheo_xyz

[The Tinkering Society @TinkeringSoc]

Do you hold a traditional fixed-rate product with a set maturity?

Such as government bonds, corporate bonds, and certificates of deposit…

[Quant ={Rheo} @SizeQuant]

@joel_obafemi Real yield parity isn't the sector weakening – it's the reference rate exposed as a dated curve the sector doesn't host

[Quant ={Rheo} @SizeQuant]

@stacy_muur @Morpho Nice piece. The lack of orderbook means no resting bid-ask, marks on open positions, canonical exits. Not sure we can claim fixed-rate credit is solved just yet tbh

[Quant ={Rheo} @SizeQuant]

@SilvioBusonero Gud breakdown. Rate-native ≠ canonically observable though. No resting protocol queue, no price-time priority, offers off-protocol with zero guarantees. a fill someone routed isn't a bid you can observe/lift

[Quant ={Rheo} @SizeQuant]

@Nomaticcap @kpk_io @eulerfinance If that gets you juiced, check @rheo_xyz

Fixed-rate credit with a visible depth-of-book curve ➦

[Quant ={Rheo} @SizeQuant]

@0xyanshu @Morpho @bobajeanjacques @MerlinEgalite @PaulFrambot @Crotts__ @maccanomics @DAdvisoor @Featherlend WP is tight but "tradable" and "marked" aren't the same claim.

Off-protocol routing gives you an exit event when a counterparty appears. Standing bid and ask at the maturity give you a price you can read between fills. The mark is the part routing can't produce.

[Rheo @rheo_xyz]

https://t.co/3gq5tUENeO

[Quant ={Rheo} @SizeQuant]

@0scaronchain Bond origination has two jobs: clear initial yield, and reprice as info arrives. Auctions handle the first. The second needs continuous depth between issuance and maturity

[Rheo @rheo_xyz]

Any credit desk does four things.

Prices relative value across tenors. Sizes against observable depth. Marks the book between fills. Knows where the exit clears.

An intents-based flow gives you a fill. None of the four.

A two-sided book gives you all of them, before the trade clears.

[Quant ={Rheo} @SizeQuant]

@tiger_research_ You cite October '25 but Resolv doesn't fire. Same curator, same architecture, a different failure mode. Credit risk and liquidity risk require diff structural responses – curation is the answer to one of them

[Quant ={Rheo} @SizeQuant]

@SachinHMx The kink-model failure – rates jumping from 4% to 30–40%, term borrowing breaking, Aave Arc failing – is why RWA gets pitched as the unlock.

What does wrapping a HELOC and clearing it through the same utilization curve actually change?

[Quant ={Rheo} @SizeQuant]

@0xCheeezzyyyy @iris_credit So the duration of the fixed-ness is itself variable? A function of how long the solver's bond can absorb negative carry.

A fixed rate that ends when the bond runs out is a different product to a fixed rate.

[Quant ={Rheo} @SizeQuant]

Tokenized T-bills carry Fed risk. Base DeFi stablecoin pools carry smart contract risk, oracle risk, and governance exposure.

They're now priced the same – Aave USDC base at 3.37%, below the 3M Treasury. The market has stopped charging for the difference.

[Token Terminal 📊 @tokenterminal]

Total RWA market cap: $37.6B

Leading sector: tokenized funds
Leading asset: sUSDS
Leading issuer: @SkyEcosystem
Leading chain: @ethereum

[Quant ={Rheo} @SizeQuant]

@DeFi_Andree @aave @Token_Logic @Matthew_Graham_ Aave's risk engine performed exactly as designed in April.

What didn't function in the same window was depositor-side exit availability. WETH utilisation pinned at 100%. USDT and USDC pinned shortly after.

Two different scoreboards on the same event.

[Rheo @rheo_xyz]

DeFi just rediscovered a 1983 glitch. Twice in four weeks.

The Aave-Kelp cascade wasn't a bridge, curator, or parameter problem. It was Diamond-Dybvig: callable liabilities funding non-callable assets admit a run equilibrium.

Three pieces below. The fourth lands next week.

[Rheo @rheo_xyz]

https://t.co/LSof025JJJ

[Quant ={Rheo} @SizeQuant]

Correct read. Aave/rsETH: liquidation engine worked as specified, but no observable replacement rate. Just vault NAV at amortized cost.

On depth for actionable marking: depends on position size vs visible depth. A $10M credit against a $2M bid stack doesn't have an actionable mark – the exit walks the book and realizes slippage the mark didn't price.

The advantage is transparency. Bid stack is visible before the exit decision, not discovered during it. Vault NAV gives you a number. Orderbook shows the actual fill path. Early exit depends on depth – we don't handwave that.

On origination vs infrastructure: Rheo is venue tier. SellCreditMarket and BuyCreditMarket handle new loan origination and existing position exits vs. the same resting offers. One price-discovery primitive. One liquidity pool to bootstrap.

Midnight is infrastructure tier – different category position.

Gud article on Aave solvency btw. You might want to check Rheo's two Diamond-Dybvig pieces on utilization-as-contagion-vector. The structural remedy you name – liability side carries a maturity – is exactly what the orderbook delivers.

#1 https://t.co/ZSkd5CDKVJ

#2 https://t.co/QTpII3LUcx

[Rheo @rheo_xyz]

https://t.co/Drbvb4nHAm

[Quant ={Rheo} @SizeQuant]

@xBartega Prime USDC pinned at 100% util after Aave's WETH pool. Zero rsETH exposure. Different chain.

The bank run jumped the perimeter. The credit risk didn't have to.

[Quant ={Rheo} @SizeQuant]

10/
We’ve mapped that in our latest @rheo_xyz piece: the third intervention, the dial-at-the-ceiling architecture argument, and the asymmetry beneath a second failure in a completely different risk model weeks earlier.

https://t.co/0MBNvCdxen

[Rheo @rheo_xyz]

https://t.co/Drbvb4nHAm

[Quant ={Rheo} @SizeQuant]

In 1983, Diamond and Dybvig solved a two-century banking puzzle: why do solvent institutions still run?

The proof: any system that pairs callable deposits with non-callable assets admits a run equilibrium – solvency doesn't matter.

DeFi just re-ran the experiment. 🧵

[Quant ={Rheo} @SizeQuant]

9/
Diamond and Dybvig analyzed two interventions for the run equilibrium: suspension of convertibility and deposit insurance (functionally equivalent to LOLR). Neither translates on-chain.

A third was developed later. It's the only one that does – and it isn't parameter tuning.