DIA Oracles (@DIAdata_org): Why £100B in Fully-Backed Stablecoins Can't Function as DeFi Collateral

Why £100B in Fully-Backed Stablecoins Can't Function as DeFi Collateral The tGBP Case Study: Reserve-Backed Pricing for Institutional Assets @tokenGBP (tGBP) is a GBP-pegged stablecoin issued by BCP Technologies, an FCA-registered entity, and deployed across six blockchains. Like most institutional-grade stablecoins, tGBP is built for custody and settlement rather than speculative trading. Trading volume relative to total issuance remains modest, which is typical for assets prioritizing reserve transparency and institutional use over secondary market liquidity. This structure creates a pricing problem. Market-based oracles aggregate exchange data to determine value. That works for liquid assets with continuous trading. It fails when an asset rarely trades and derives value from verifiable reserves rather than market speculation. DIA deployed a Proof of Reserves oracle for tGBP to solve this. The feed computes value from reserve backing rather than secondary market activity. Pricing tGBP From Its Reserves tGBP's reserves consist of GBP cash, money market funds, and short-term UK gilts held at regulated custodians: Banking Circle, Clear Junction, Swissquote, and Interactive Brokers. DIA's Feeder network queries reserve balances from these custodians via authenticated APIs, normalizes to GBP, and aggregates. In parallel, Feeders query totalSupply() across all six chains where tGBP is deployed. The price calculation: GBP_Price = min(1.0, Total_Reserves / Total_Supply) When reserves equal or exceed supply, the feed publishes 1.00. When reserves fall short, it discounts immediately. No waiting for thin markets to discover the shortfall. The GBP price converts to USD using DIA's FX reference feed with consensus filtering across three institutional sources. 1.00 When Backed, Less When Reserves Fall Short When tGBP is fully backed, the feed reads 1.00. When over-collateralized, it still reads 1.00, because for a redeemable stablecoin, par is the maximum honest valuation. When reserves fall short of supply, the feed discounts immediately and proportionally in the next published update. The practical effect: the feed tracks the issuer's actual obligation. A vault consuming this feed underwrites reserve adequacy rather than the noise of thin prints on a single venue. Reserve Adequacy vs Market Liquidity A lending protocol accepting tGBP based on Coinbase order book depth underwrites market liquidity risk. The issuer's actual obligation is reserve adequacy. Different risks require different pricing methodologies. This distinction enables institutional collateral acceptance. Vault curators size positions based on reserve adequacy rather than thin secondary markets. The credit assessment shifts from "can I liquidate this on Coinbase" to "does the issuer hold sufficient reserves." When Reserve-Backed Pricing Applies The methodology applies to any asset where value derives from verifiable backing rather than trading. Tokenized treasuries price from portfolio NAV. Yield-bearing stablecoins price from contract exchange rates. Fund shares price from marked holdings. Market oracles remain appropriate for deep liquidity and continuous price discovery. Reserve oracles become necessary when markets are thin, fragmented, or nonexistent. The constraint is verification cadence. For issuers with custodian infrastructure and audited attestations, that's satisfied. The work is connecting reserve data to pricing infrastructure that computes from backing rather than trades. From Payment Rails to Institutional Collateral Over £100B in fully-backed stablecoins exist globally. Most can't function as institutional DeFi collateral because pricing infrastructure measures market liquidity instead of reserve adequacy. tGBP demonstrates the solution. Institutional capital priced not from thin secondary market trades but from verified reserves at banking partners. The oracle measures solvency. Protocols make credit decisions based on backing. This is the pricing layer institutional DeFi requires. Not better market aggregation. Different architecture for different assets. Learn more: https://diadata.org/blog/post/proof-of-reserves-for-tgbp/