Turning a Treasury Fund into Stablecoin Collateral Without Trust Gaps

Traditional finance prices funds based on what they hold. Money market funds and mutual funds redeem at net asset value, struck daily by an administrator who values the underlying assets and reconciles them against custody records. Even ETFs, which trade freely on exchanges, are created and redeemed against the fund's actual holdings at NAV. The methodology has survived a century of market stress because it answers the question that matters for collateral: what is this asset actually backed by? For most of its history, onchain finance has answered the pricing question differently. The dominant model prices assets by observing where they trade. This works well for onchain-native assets, whose value isn't anchored to any underlying assets. It is less appropriate for stablecoins, tokenized funds, and other instruments whose entire value proposition rests on the underlying assets backing the onchain token.

Two ways to build a price feed

Market-based feeds aggregate trading prices across centralized and decentralized venues and fuse them into a single reference price. They are straightforward to build and answer a real question: what does this asset sell for right now. The weakness appears when liquidity goes thin. During volatility, market makers reduce exposure and withdraw liquidity, so manipulating the price becomes cheapest at exactly the moment protocols are most sensitive to it. A liquidation engine reading a manipulated price does not know it is being lied to. It simply liquidates. NAV-based feeds take the fund administrator's approach: the price comes from the value of the underlying asset, not from secondary market liquidity. A thin pool on a stressed venue has no influence on the feed, because the feed never looks at it. This is why these feeds are also called fundamental-based feeds, the price reflects what backs the token, not where it trades.

The honest caveat

It would be convenient to stop there and declare the problem solved. Anyone with experience in traditional finance knows better. NAV pricing has its own dependency: the quality, freshness, and verifiability of the data behind the underlying asset. A NAV feed built on stale or unverified reporting doesn't remove the trust problem, it relocates it, from trading venues to fund managers. That is the residual risk of a NAV feed, and it's worth naming precisely: reserve-data trust, the risk that the numbers describing the backing are wrong, delayed, or taken on faith. A NAV oracle doesn't have a pricing problem. Its output is only as good as the verification behind it. So the verification has to be real. A NAV-based oracle should independently check every attested NAV, cross-referencing reserves and prices against the fund administrator and the additional sources the administrator discloses. The value only reaches the oracle contract if the token is adequately collateralized and the NAV holds up against those checks. The two feed types answer different needs. For most onchain-native assets, a market-based price is the natural fit. For tokenized assets, collateral valuation, reserve verification, and the logic that governs minting and redemption for stablecoins, fundamental-based pricing is better suited.

Where Chronicle sits

That verification is exactly what Chronicle's Proof of Asset is built to provide. Proof of Asset verifies reserves continuously, cryptographically, and onchain rather than through periodic attestations. It operates across the full tokenization stack: it can verify a tokenized fund's underlying holdings, and it can verify the collateral behind a stablecoin minted against that fund. The following example shows what this looks like in practice. Chronicle serves as a validator for the M0 ecosystem: for every stablecoin built on M0, Proof of Asset verifies collateral before any mint or burn event takes place. The verification is pre-transactional: supply cannot expand or contract until the reserves backing that change have been checked. And because Chronicle sits inside the system as a validator, it accesses the reserve data firsthand rather than through someone else's reporting. That direct access to data is what uniquely positions Chronicle to build a NAV-based oracle for these assets: the oracle prices from the same primary data the validator already verifies.

A unified data layer

JTRSY shows both layers of the stack working at once. M0 now accepts JTRSY, tokenized by Centrifuge, as eligible collateral for stablecoins built on M0, and any issuer can include it in its collateral composition. The fund is managed by Janus Henderson, holds short-duration U.S. Treasury bills, and offers instant liquidity of up to $500 million per day. At the asset layer, Chronicle Proof of Asset powers JTRSY's onchain verification. When an M0 issuer includes JTRSY in its collateral, the second layer engages. The same Proof of Asset that verifies the fund's reserves now confirms that collateral is in place before each mint and burn, this time in Chronicle's validator role on M0. One independent party, with direct access to the underlying data, covers the verification from the Treasury bills to the stablecoin. That is the full institutional playbook onchain: institutional-grade assets, verified end to end. The full stack running JTRSY on M0 is an example of what the full tokenization stack looks like when it's running in production: a tokenized treasury fund priced from its underlying asset value, used as collateral for stablecoins, with the same verification running end to end. No handoff between reporting layers, no gap between what the price says and what the underlying asset holds. That unified layer runs on Proof of Asset, powering the data pipeline. JTRSY on M0 is one instance of this pattern. The pattern itself is what tokenized collateral has been waiting for.

Disclaimer

Chronicle provides a data and verification technology platform. Chronicle Proof of Asset and related services are strictly limited to the provision of data and verification signals. Chronicle does not issue, offer, sponsor, market, manage, administer, custody, or otherwise operate any referenced products or services, or any related underlying assets. Chronicle is not acting as, and is not licensed or authorized as, any type of financial intermediary (such as an exchange, broker/dealer, investment adviser, or custodian) in connection with any referenced products or services. Any data (including data displayed on Chronicle dashboards) is provided “as is”, without representations or warranties of any kind, and subject to Chronicle’s applicable terms and conditions. This post is provided for general informational purposes only and does not constitute, and should not be relied upon as, investment, legal, tax, accounting, or other professional advice, nor an offer or solicitation to buy or sell any securities, tokens, or other financial instruments, or any recommendation to engage in any transaction with any such instruments.