How DeFi prices collateral is now a macro policy question
The IMF’s Tokenized Finance note flags pricing of illiquid assets as a systemic risk. What does that mean for oracle infrastructure and institutional DeFi

The IMF published a note this month that deserves close reading from anyone building or allocating in tokenized finance. “Tokenized Finance” (NOTE/2026/001), authored by Tobias Adrian, the IMF’s Financial Counsellor, argues that tokenization is not an efficiency upgrade to existing financial plumbing but a structural reconfiguration of how trust, settlement, and risk management are organized.
The note is 23 pages and it covers settlement finality, governance of code, cross-border resolution, stablecoin risk, and wholesale CBDC design. But one thread runs through the entire document that hasn’t received enough attention: the pricing infrastructure gap for illiquid tokenized assets.
The gap in the IMF's own words
Adrian’s argument starts from a structural observation: Tokenized assets, including fund shares, securities, and programmable financial instruments, are migrating onto shared ledgers where settlement happens atomically and collateral moves in real time. For any of this to work safely, every asset in the system needs continuous, reliable pricing.
For liquid assets, this is solved. Exchanges produce prices and aggregators publish them.
But the asset classes driving institutional adoption don’t fit that model. Tokenized treasuries crossed $11 billion in market capitalization in March 2026, up from under $1 billion two years ago. BlackRock’s BUIDL fund alone holds over $2.1 billion. The broader RWA market (excluding stablecoins) sits at roughly $27 billion according to RWA.xyz.
These assets share a characteristic that breaks existing pricing infrastructure: they don’t trade continuously on liquid markets. Tokenized treasury funds don’t have order books. Fund NAV tokens don’t establish price through supply and demand. Yield-bearing tokens have redemption mechanisms encoded in smart contracts. Their value is defined by what the protocol guarantees you can redeem, not by what the last trade said.
The IMF note is direct about what happens when pricing infrastructure can’t handle this. When financial logic is embedded in smart contracts, automated margin calls triggered by distorted or stale price data force rapid liquidations. Adrian specifically flags faulty price feeds as a vector for cascading failures.
On October 10, 2025, $19 billion in leveraged DeFi positions were liquidated in 24 hours. The IMF note references this event directly as an example of automated liquidation triggers amplifying market stress.
The regulatory dimension DeFi ignores
Adrian’s note also addresses something the DeFi discourse largely skips: regulatory alignment with fair value standards.
Fair value measurement standards, specifically IFRS 13 and ASC 820, explicitly require fundamental valuation methods when markets are inactive. Institutional capital must comply with these standards. When a tokenized treasury fund enters a DeFi lending protocol as collateral, the pricing methodology underneath needs to produce valuations that would survive an audit.
Most of DeFi doesn’t think about this. But the capital it’s trying to attract does. An asset manager allocating to an onchain vault through a risk curator like Gauntlet or Steakhouse Financial needs the pricing layer to align with the same frameworks their compliance teams already operate under.
Adrian’s note connects these dots explicitly. Fair value infrastructure for illiquid tokenized assets is a regulatory precondition for the institutional capital that the entire tokenized finance thesis depends on.
Traditional finance already solved the methodology
The note points out that the pricing problem itself isn’t new. Fund administrators have computed NAV for illiquid portfolios for decades. Banks and auditors routinely model loan book valuations and verify reserve backing for money market instruments. The valuation logic is well-established.
What’s different onchain is that the inputs these methods need are often already available as smart contract state. Redemption rates, reserve balances, yield accruals, portfolio compositions. In traditional finance, collecting these inputs requires trusted intermediaries and batch processes. Onchain, they can be read directly, computed continuously, and verified by anyone.
Governance of the data layer
This is where the note gets most interesting for anyone building oracle infrastructure. Adrian argues that as financial logic migrates into smart contracts, governance must extend beyond institutions to algorithms. The functions that smart contracts perform (executing collateral transfers, initiating default procedures) are systemically important and dependent on the data they consume.
The note’s language is worth paying attention to: formal verification and independent audits should be mandatory for systemically important contracts. Change management must be transparent. And, directly relevant to oracles, the governance challenge concerns not only code quality but the processes that design, validate, modify, and override the data feeds powering execution.
For pricing infrastructure specifically, this means the methodology behind every price needs to be inspectable: the inputs, the computation, the logic connecting them. When a vault liquidation fires because a tokenized treasury was repriced, the risk curator needs to be able to trace that price back to its source and verify the calculation was correct. That’s a governance requirement.
Who governs the price?
The note’s bias is toward permissioned, institutionally governed shared ledgers. Adrian’s preferred scenario has tokenized infrastructures built around wholesale CBDC with coordinated oversight. But the protocols that actually need fair value pricing today, Euler, Morpho, Silo, operate on permissionless infrastructure, with institutional risk curators managing vault strategies on open rails.
This tension matters for pricing specifically. A permissioned model implies designated entities computing and attesting to fair value, similar to how fund administrators operate today. A permissionless model implies transparent onchain computation where anyone can verify correctness. The IMF note doesn’t quite acknowledge this second option, but its own requirements (auditability, governance of data feeds, verifiable correctness) are more naturally satisfied by transparent computation than by institutional attestation.
How DIA Value addresses this
The IMF has now framed the absence of fair value pricing for illiquid tokenized assets as a macro-level risk, a structural vulnerability in the financial system that tokenization is building.
At DIA, this is the problem we’ve been building against. DIA Value prices illiquid tokenized assets by computing fundamental value from onchain contract state, with the full computation verifiable.
When a protocol needs to price a yield-bearing token as collateral, Value reads the redemption rate directly from the issuing contract rather than relying on a thin secondary market. When a stablecoin protocol needs to verify its reserves match circulating supply, Value computes the backing ratio from onchain state.
It’s live across lending protocols and stablecoin infrastructure, and its architecture makes the full computation pipeline verifiable onchain, which is the design constraint the IMF note points to, even if it imagines a different institutional model delivering it.
The broader question is whether this pricing infrastructure will be built by permissioned intermediaries replicating traditional finance with a blockchain wrapper, or by verifiable open systems like DIA that give institutional actors the auditability they need without reintroducing the opacity they’re trying to leave behind.




