Vault Share Price Oracle
Lending markets that take yield-bearing vault tokens as collateral need a reliable USD price for them at every block. That price has to be read from the vault's balance sheet, not from a market. DIA Fundamental Feeds compute it and deliver it across chains as a verifiable feed.
Pricing Vault Tokens Held as Collateral
A lending market lets a borrower post a yield-bearing vault token as collateral and draw a loan against it. To know whether that loan is still safe, the market needs the token’s USD value, recalculated at every block. That number is the vault share price.
Price it too high and the market keeps lending against collateral that no longer covers the debt, so bad debt builds up. Price it too low and it liquidates borrowers who were solvent. In isolated markets like Morpho’s, the oracle is fixed when the market is deployed and cannot be swapped later, so the methodology choice is permanent. Its price() function runs at every health check and every liquidation.
This flow is already at scale. ERC-4626 vaults concentrate institutional deposits, and the same tokens reach retail through Coinbase, Binance, Gemini, Ledger, Bitget, and Trust Wallet. The curators choosing each market’s oracle carry the bad-debt risk when it fails.
Where Naive Vault Share Pricing Fails
Reading a vault's share price reliably is the hard part, not the formula. The underlying can be spread across markets, nested inside other vaults, or held in illiquid positions, and EIP-4626 warns its own preview methods are not always safe to read directly as oracles. The patterns below recur when vault tokens are priced without verifying contract state.
Underlying positions nested across vaults or hard to value
Single-block share-price manipulation via flash loans
Secondary-market aggregation on thin trading liquidity
Single-node reads without independent verification
Vault donation attack surface left undefended
Stale updates between liquidation events
Pricing Approaches Compared
Data source
Verifiability
Cross-chain delivery
Update frequency
Manipulation surface
Secondary trades
Trade history only
Per-chain feeds
Trading-dependent
Open in thin venues
Issuer reporting
Trust the issuer
Per-chain feeds
Reporting-dependent
Reporting delay risk
Vault contract state
Onchain, auditable
One canonical value
Per-block
Multi-feeder consensus
From Vault State to Verified Price
NAV From Vault Contract State
DIA computes Net Asset Value from vault state: assets minus liabilities, divided by total supply, the value an ERC-4626 contract represents through convertToAssets(). The work is in reading that state reliably, not the formula. Feeders resolve the underlying positions a share is a claim on rather than trusting a single convenience call. No issuer attestation, no external data provider, and the full input chain stays verifiable onchain.
One Verified Value, Every Chain
More than 10 independent feeders read each vault's balance sheet every update cycle. Reports go to Lasernet, DIA's purpose-built ledger for fundamental data, where an aggregator contract consolidates them into a single canonical value. That value is delivered to every chain where the vault token is integrated as collateral.
Price Vault Shares From State, Not Trades
If your protocol accepts ERC-4626 vault tokens as collateral, talk to us about a vault share price feed.
