# From Custody to Collateral: Tokenized Treasuries in DeFi

> How VBILL, BUIDL, and peers are being wired into Euler, Morpho, and Aave — and what happens when on-chain liquidation outruns real-world settlement.

- Source: https://www.steadyrain.xyz/en/articles/tokenized-rwa-as-defi-collateral/
- Publisher: Steady Rain
- Author: 0xYatha
- Published: 2026-05-29T03:43:25.100Z
- Categories: DeFi
- Language: en

## Introduction

For most of DeFi's history, the collateral set has been narrow and self-referential: ETH, staked ETH, BTC wrappers, a handful of governance tokens, and stablecoins whose backing is itself a black box to the protocols that accept them. The credit stack built on those assets is procyclical by design — when crypto trades down, collateral value falls, borrow demand collapses, and the system contracts in lockstep with the market it is supposed to serve.

The recent move to admit tokenized money market funds — VanEck's **VBILL** onto Euler, BlackRock's **BUIDL** into a growing list of vaults and borrow markets, Franklin Templeton's **BENJI** through various integrations — is being framed in industry coverage as a yield story. We think that framing misses the structurally interesting part. The yield on three-month T-bills is a fact about traditional markets; routing that yield through a transfer agent and an ERC-20 wrapper does not, by itself, change DeFi. What changes DeFi is the moment those wrappers stop being passive holdings and start being **posted as collateral against on-chain borrow**.

That transition introduces a set of design problems the major lending venues have only begun to answer in public. How is the NAV oracle constructed, and what happens between updates? What does "liquidation" mean for an asset that can only be redeemed during the issuer's business hours, in fiat, to a whitelisted wallet? Who eats the loss when on-chain liquidation completes in seconds but real-world settlement takes two days? And how should a protocol price the credit risk of a regulated issuer it cannot legally enforce against?

This piece looks at the mechanics — oracle pipelines, liquidation paths, custody assumptions — and compares the structural choices Euler, Morpho, and Aave are making as they curate this new collateral class.

## What a tokenized treasury actually is

Before we can talk about collateralization, it is worth being precise about what the token represents, because the design space for treating these instruments as collateral collapses or expands depending on that answer.

A tokenized treasury fund is, in almost every current implementation, a **wrapped interest in a regulated fund** — typically a Delaware or BVI vehicle, sometimes a Luxembourg structure — that holds short-duration U.S. Treasury bills, repos, or a money market fund's shares. The token itself is an ERC-20 (or equivalent) whose transfer logic is gated by an allowlist maintained by the issuer or its transfer agent. Holders are KYC'd subscribers of record. The token is not a bearer instrument in the legal sense, even though it behaves like one mechanically; the issuer can, and in practice does, retain the right to freeze, force-redeem, or invalidate transfers that violate compliance rules.

The yield accrues in one of two structural patterns:

- **Rebasing.** The token balance grows over time to reflect accrued interest, while the price remains pinned near $1. BUIDL uses a daily dividend that is paid in additional tokens.
- **Accumulating.** The token supply is fixed and the per-token NAV rises. VBILL and several Franklin Templeton products follow this pattern, which is closer to how a traditional money market share class works for total-return investors.

The distinction is not cosmetic when you are wiring the asset into a lending market. A rebasing token requires the lending protocol to either pass the rebase through to depositors or capture it at the vault layer — both are solved problems, but each has fee and accounting consequences. An accumulating token requires an oracle that tracks NAV between official publication windows; without one, the borrowable LTV has to be set conservatively enough to absorb a day's worth of unobserved drift.

The subscription and redemption flow sits entirely off-chain. A holder who wants cash sends an instruction to the transfer agent, the agent burns tokens after settlement confirmation, and USD wires out of the fund's bank in T+0 or T+1 depending on the cutoff. There is no atomic on-chain redemption, and there is no secondary market on a centralized exchange of meaningful depth. This single fact — that the asset has no fast exit other than a private OTC sale to another whitelisted holder — is the constraint that every collateralization design has to bend around.

## The oracle pipeline

*[Figure: img1]*

An oracle for a tokenized treasury looks superficially trivial: the fund publishes a NAV, the oracle posts it on-chain, the lending market reads it. In practice, three layers of decisions determine whether the resulting price feed is usable for liquidations.

### The reference value

For an accumulating token, the natural reference is the fund's official NAV per share, published once per business day after market close. That feed is appropriate for valuing the position but not for triggering liquidations, because it is stale by definition relative to intraday Treasury moves. Most current oracle designs therefore composite the official NAV with a model of accrued interest since the last publication, using a published yield rate as the drift parameter. The output is a price that ticks up smoothly between official prints and snaps to the published NAV when one arrives.

For a rebasing token, the on-chain balance carries the yield and the per-token price target is $1. The oracle's job here is to verify that the redemption value is in fact near par — a check that becomes interesting only in a stress scenario where the underlying T-bills are trading away from par, for example during a debt ceiling episode or a sharp duration shock at the very front end.

### The publication channel

The Block's coverage of the VBILL integration notes that the oracle layer relies on price feeds curated by infrastructure providers rather than the issuer publishing directly to chain. That layering matters. The transfer agent is the source of truth, but the lending protocol does not want to bind its liveness to a single off-chain actor. The intermediate oracle provider takes on the job of reading the agent's data, attesting to it, and writing it on-chain on a schedule the lending market can rely on.

The risk this layering creates is failure of the off-chain-to-on-chain handoff during exactly the moments collateral pricing matters most: a fund administrator pauses publication during a corporate action, a custodian's reporting pipeline lags during a holiday, or a transfer agent's systems are down. The lending market's fallback policy in those windows — freeze, fall back to a stale-but-conservative price, or halt liquidations — is itself a credit decision the protocol is making on behalf of depositors.

### Update frequency vs. liquidation cadence

DeFi liquidation engines were built to operate on price feeds that update at least every few minutes and often every block. A treasury NAV that updates once per business day is, from the engine's perspective, effectively constant. That is not a problem when the underlying instrument's volatility is bounded by Fed policy expectations and a known maturity wall — three-month T-bills do not gap. It becomes a problem when the **collateral asset is paired against a volatile debt asset**, such as ETH or a long-tail stablecoin, because all of the mark-to-market action sits on the debt leg. The liquidation threshold has to be set with that asymmetry in mind, and the close factor — how much of a position a single liquidator can seize — has to account for the fact that the collateral cannot actually be sold into a deep market within the liquidation window.

## How Euler, Morpho, and Aave have curated the markets

*[Figure: img2]*

The three venues most actively building out tokenized-RWA collateral markets have taken visibly different architectural paths. Those paths are not incidental — they reflect each protocol's underlying model for how risk is curated and who bears it.

### Euler's vault-per-asset model

Euler v2's design treats every market as a freely composable vault, with risk parameters set by whoever launches the vault rather than by protocol-wide governance. The VBILL integration uses this structure directly: the vault accepting VBILL as collateral is curated by a third party, parameters are public, and lenders who deposit the borrowable asset into that vault are opting into that curator's risk choices.

The advantage of this model for an asset like VBILL is that the curator can write parameters tightly fitted to the instrument — a high LTV reflecting the low underlying volatility, paired with a long grace period before liquidation that respects the off-chain settlement constraint. The disadvantage is that the curator's competence and economic alignment are now part of the credit stack. A lender depositing into the vault is, in effect, extending unsecured credit to the **curator's risk model**, on top of the secured exposure to the borrower.

For a sophisticated participant this is a feature; the risk surface is legible and isolatable. For a retail depositor expecting Aave-style protocol guarantees it is something else, and the venue's UX has to make that distinction loud.

### Morpho's isolated market primitive

Morpho Blue's primitive is even more atomic: each market is a single collateral-asset pair with its own LTV, oracle, and interest rate model, immutable after deployment. Curation happens at the MetaMorpho vault layer, where allocators choose which underlying markets to expose depositors to and in what weights.

For tokenized treasuries this is, in some ways, a more natural fit than Euler's design, because the isolated-market constraint maps cleanly onto the regulatory reality that the collateral is whitelisted and the universe of borrowers is small. A market accepting BUIDL as collateral against USDC can be sized to the issuer's known holder base, and the MetaMorpho allocator can size its exposure based on its read of the issuer's credit and operational risk. Several allocators have publicly leaned into this design, treating RWA-backed markets as a distinct tranche from crypto-native markets within the same vault.

The structural cost is fragmentation. Each RWA collateral asset, each oracle choice, each LTV setting produces a separate market, and liquidity does not pool across them. For instruments where holder counts may be in the low hundreds rather than tens of thousands, that fragmentation can dominate.

### Aave's governance-curated, monolithic pool

Aave's approach to RWA collateral has been the most conservative of the three. Where Euler and Morpho allow markets to be launched permissionlessly, Aave's monolithic v3 pool requires a governance vote to onboard a collateral type, and the asset has to fit within the protocol's existing risk framework — supply caps, isolation mode, e-mode, and a unified liquidation flow.

For tokenized treasuries this has meant that integrations enter through carefully scoped facilities — Aave's earlier GHO and Horizon-style RWA-focused efforts and the more recent isolation-mode listings — rather than as drop-in collateral in the main pool. The benefit is that the depositors in the main USDC or ETH market are not silently exposed to a new credit assumption. The cost is speed: getting an asset listed is a multi-week governance process, and the parameters that emerge tend toward the conservative tail of the design space.

The three approaches reflect a deeper disagreement about where risk should sit. Euler and Morpho push it outward to curators and allocators; Aave keeps it at the protocol governance layer. Tokenized RWAs, because their risk is fundamentally legal and operational rather than market-driven, may turn out to be the asset class that most exposes the tradeoffs of each model.

## When real-world settlement lags on-chain liquidation

*[Figure: img3]*

The most consequential design problem in this whole arrangement is the **settlement asymmetry** between the on-chain debt leg and the off-chain collateral leg. We want to spend time on it because it is the failure mode least well understood from a crypto-native perspective.

Consider a stylized position. A borrower posts $10M of an accumulating tokenized treasury and borrows $7M of USDC against it — a 70% LTV against an asset that, in normal conditions, has effectively zero volatility. The protocol's liquidation threshold is 80%. The borrow accrues interest. For months, nothing happens; this is exactly the kind of position the asset class is designed to host.

Now imagine the liquidation threshold is breached. There are roughly three ways this can occur, and each has a different settlement profile.

The first is **slow drift**: borrow interest accrues faster than the implicit yield on the collateral, the LTV crosses the threshold, and the position becomes eligible for liquidation. This is the benign case. A liquidator can repay USDC and receive the collateral token at a discount, and as long as the liquidator is itself whitelisted to hold the token, the transfer settles atomically on-chain. The liquidator then carries the collateral until they can redeem it via the transfer agent the following business day, taking T+1 settlement risk and the funding cost of the position in the interim. The liquidation incentive — typically 2–5% — has to be calibrated to compensate that funding cost plus the operational overhead. This is solvable engineering.

The second is a **mark-to-market event on the debt side**: the borrowed asset is not USDC but ETH or a volatile stablecoin, and a price move pushes the position into liquidation territory not because the collateral fell but because the debt rose in dollar terms. Here the same liquidation flow applies, but the velocity of the debt move can compress the time available to act, and a thin liquidator base — because few addresses are whitelisted to hold the collateral — can leave the position underwater before anyone executes. This is the case for tight close factors and large incentives.

The third is the dangerous one: **a discontinuity on the collateral side itself**. The fund administrator suspends redemptions during a stress window — a debt ceiling impasse, a money market fund gating, a custodian operational failure, an OFAC action against a holder. The on-chain token is still transferable on the secondary market, but its true redemption value has decoupled from its quoted NAV, and the oracle is either reporting the last published NAV (now misleading) or has been frozen by its operator (now stale). Any liquidation that occurs in this window transfers a synthetic version of a frozen asset from the borrower to the liquidator, and the liquidator's expected recovery is no longer a function of NAV but of how the off-chain situation resolves.

This is not a hypothetical class of risk; it is the same class that produced the Silicon Valley Bank weekend in March 2023, where USDC briefly depegged because the redemption channel for a small fraction of its reserves was closed for two days. A tokenized treasury fund that ever needs to gate redemptions, even briefly, will produce a similar shock — and unlike USDC, the on-chain debt against the asset cannot be socialized through a sponsor's balance sheet.

### Design responses

The protocol-level responses available are limited and unsatisfying. One is to **cap exposure** — supply caps that ensure no single asset can dominate a vault's collateral base, so that a redemption gating event is a haircut rather than an insolvency. Another is to **shorten the debt-side duration** — limit borrows to stable assets with their own redemption channels, on the theory that the lender of last resort during a real-world stress event is the U.S. Treasury, not the lending protocol. A third is to **lengthen the liquidation grace period** — give the borrower a window measured in days rather than seconds to top up the position before forced sale, accepting more bad-debt risk in exchange for fewer pathological liquidations.

None of these is free, and the fact that the three major venues have made different choices among them is part of what makes this period structurally interesting.

## Custody and the trust stack underneath

*[Figure: img4]*

A point worth being blunt about: when a lending protocol accepts a tokenized treasury as collateral, it is accepting a chain of trust assumptions that the protocol cannot itself verify or enforce.

The chain runs roughly like this. The token's redemption value depends on the fund administrator's solvency and operational continuity. The administrator's reporting depends on the fund custodian — a bank that holds the underlying T-bills in segregated accounts. The custodian's segregation depends on the bank's compliance with the relevant securities regulation. The token's transferability depends on the issuer's transfer agent and the allowlist it maintains. The oracle's accuracy depends on the data provider's pipeline from the administrator. And the protocol's ability to actually recover value in a default scenario depends on whether a court in the relevant jurisdiction would recognize the on-chain liquidation as legally effective.

Each of these layers is, in conventional finance, addressed by a written contract, an insurance policy, and a regulatory backstop. In the on-chain wrapping, most of those instruments are inherited from the underlying fund structure but are not directly available to the lending protocol or its depositors. A depositor in a Morpho vault has a claim against the vault; the vault has a claim against the borrower; the borrower has, in principle, a claim against the fund. There is no privity of contract between the depositor and the fund.

This is not a fatal problem — it is the same legal topology that exists when a prime broker accepts a money market fund share as margin — but it does mean that the credit quality of the collateral is bounded above by the credit quality of the issuer, and the protocol has very few tools to enforce that boundary if the issuer disputes a liquidation. The largest current issuers — BlackRock, VanEck, Franklin Templeton — are large enough that the operational and reputational cost of disputing a liquidation would likely exceed any benefit, which is itself a form of soft enforcement. Whether that soft enforcement holds for the next tier of issuers, who will inevitably enter the market once the integration patterns are proven, is an open question.

## Implications and open questions

*[Figure: img5]*

The integration of tokenized treasuries into DeFi credit markets is being driven by a clear demand: borrowers who hold yield-bearing instruments do not want to liquidate them to access on-chain liquidity, and lending protocols want a collateral asset whose value is not correlated with crypto market cycles. Both motivations are sound, and the supply of these instruments is growing. The structural question is whether the wrapping survives contact with a stress event that originates outside the crypto market.

A few things we will be watching as this builds out.

**The first redemption gating, whenever it happens.** No major tokenized treasury has yet had to suspend redemptions in a way that decouples its on-chain quote from its true value. The first time this happens — and it will happen, even briefly, because money market funds have always occasionally needed to manage liquidity at the gates — will be the first real test of how the on-chain layer handles a discontinuity at the off-chain layer. The protocol that has shortened its grace period, frozen its oracle correctly, and capped its exposure will look prescient. The protocol that has not will socialize a loss.

**The emergence of a tiered issuer market.** The current cohort of issuers is large and bank-grade. As the on-chain demand grows, smaller issuers will enter — both new-entrant fund administrators and existing crypto-native firms wrapping their own treasury holdings. The lending protocols will face a choice about whether to treat all tokenized treasuries as fungible from a risk perspective or to tier them by issuer credit. Our prior is that tiering is correct and that the venues which collapse the distinction will eventually pay for it.

**The legal status of on-chain liquidation.** No major jurisdiction has yet ruled on whether an on-chain liquidation of a whitelisted security token is enforceable against the issuer's records. The convenient assumption is that it is, because the transfer happens within the rules the issuer itself encoded. The inconvenient possibility is that a court in a stress scenario decides otherwise — finding, for example, that the borrower retained a beneficial interest the on-chain transfer did not extinguish. A clarifying ruling, in either direction, would meaningfully reshape the design space.

**The interaction with restaking and looped strategies.** Tokenized treasuries as collateral compose naturally into the kinds of looped yield strategies that dominate current on-chain credit usage. A borrower can post VBILL, borrow USDC, swap into another yield-bearing stablecoin, post that as collateral elsewhere, and repeat. The same procyclicality risk that the asset class was supposed to neutralize re-emerges through the loop. Whether the major venues add policy to discourage this — supply caps that detect re-collateralization, isolation modes that prevent it — is a design choice we expect to see contested.

What we do not expect is for this trend to reverse. The yield is real, the demand is durable, and the operational pieces — transfer agents that can write to chain, oracle providers that can price NAV, custodians that can integrate with on-chain settlement — are now built and being used in production. The interesting work over the next cycle is in the curation layer: who picks the parameters, who underwrites the issuer risk, and who is on the other side of the table when a real-world settlement delay meets an on-chain liquidation queue.