RWA collateral is not like crypto collateral.
ETH, BTC, and stablecoin collateral often rely on a spot price because these assets trade continuously on liquid markets. The spot price is often used by protocols as one input for collateral valuation.
Tokenized equity ETFs, private credit funds, and real estate tokens do not share this property. They carry context that a static price cannot represent. A lending protocol that ignores this context may operate with blind spots.
The Five Blind Spots
Redemption windows. Some tokenized assets have defined redemption schedules — quarterly windows, 45-day notice periods, constrained mint/redeem mechanics. A protocol that values private credit fund collateral at NAV during a closed redemption window may overstate the value it can realize if the protocol needs to liquidate. The NAV may be an appropriate reference value when redemption is available. When it is not, the reachable value is what matters.
Weekend and off-session drift. Tokenized equity collateral may have a frozen oracle value for 80%+ of the week. Earnings releases, credit rating changes, macro announcements, and geopolitical developments may occur during this period and may not be reflected until markets reopen. When they reopen, the correction can cascade into simultaneous liquidations for every borrower near the LTV threshold. The protocol did not cause this — it may result from relying on stale data.
NAV vs last-trade price. Private credit funds and structured products have a net asset value calculated periodically by the fund administrator. The last secondary market trade price may diverge from NAV. A protocol using last-trade pricing as collateral value may be using a number that does not match as intended. For fund products, NAV may be an important reference value.
Liquidity context. Whether bid-side liquidity exists in a thin off-hours secondary market affects what collateral is actually realizable if the protocol must liquidate. A static price does not capture this. The protocol may believe it can liquidate at price X when the actual market impact of a liquidation at that size would bring proceeds well below X.
Mint/redeem availability. If a tokenized asset's mint/redeem window is closed, the protocol cannot redeem collateral at NAV. A static oracle has no concept of this constraint. The oracle publishes NAV; the protocol cannot actually get NAV.
What Oracle Programs Can Address
Oracle Programs for RWA lending collateral can ingest contextual data from both onchain and offchain sources and apply configured per-asset policy:
Live NAV data from fund administrators via API, used as the collateral value rather than secondary market prices
Current redemption window status, with data outputs configured to reflect the relevant status when redemption is closed
Session state tracking and off-hours EMA logic for tokenized equity collateral, supporting continuous LTV monitoring throughout the week
Bid/ask spread and order book depth from exchange data providers, factored into liquidity-adjusted valuation inputs
Corporate action data — splits, dividends, index rebalances — handled programmatically
LTV thresholds can be configured dynamically: tighter requirements when the redemption window is closed, during off-hours EMA-derived pricing, or when bid/ask spread indicates thin liquidity. The logic can be encoded in the Oracle Program. The lending protocol can consume these configured data outputs without managing this complexity in its own application code.
Per-Asset Policy
A private credit fund has different redemption mechanics than a tokenized T-bill. A tokenized equity ETF has different session behavior than a tokenized real estate fund. Each collateral type may require its own Oracle Program — its own data source, its own off-hours logic, its own LTV policy.
Static oracles apply one methodology uniformly across all assets. Oracle Programs can be configured per asset, per protocol, for the specific financial mechanics of each collateral type.
For any lending protocol accepting RWA collateral, the relevant evaluation criterion is not just whether the oracle covers the asset. It is whether the oracle's behavior during off-hours, during closed redemption windows, and at session transitions is correctly specified — or whether those periods are gaps where the protocol is operating on stale collateral values.
Disclaimer: This article is provided for informational purposes only and does not constitute legal, financial, tax, investment, or other professional advice. All information is provided on an "as is" basis, without warranties or representations of any kind. SEDA provides infrastructure only and may rely on third parties for data feeds; SEDA makes no representations or guarantees regarding the availability, accuracy, completeness, reliability, or timeliness of any data, including price data. For important information, please refer to the Content Disclaimer.