Observation
Phala Cloud lists prices in $ and accepts card via Stripe, crypto via Coinbase Commerce, and wire. PHA is not named as a payment method. The staking, treasury and compute-provider docs describe no burn, buyback or revenue share. The staking docs don't say what funds vPHA rewards. GPU-miner rewards come from a mining pool the docs size at 70% of total supply. On-chain at block 26241118: the vPHA vault holds 133.06M PHA against 86.30M vPHA. A 2-of-5 Gnosis Safe (0x4a39…ebef) holds 139.01M PHA (13.9%). It received 332.08M PHA through a bridge handler on 2025-11-20 and has sent tokens out regularly since, including batches to the vPHA vault. Phala's site reports 125.3B confidential model tokens a day (OpenRouter-sourced, 2026-10-20) but discloses no revenue.
Hypothesis
Phala's product revenue is collected off-chain in fiat or general crypto and doesn't route to PHA. PHA demand comes mainly from staking, vPHA collateral and speculation. vPHA yield looks funded by emissions or Safe distributions rather than revenue (this part is inference). The 139.01M Safe roughly matches the ~141.8M PHA that aggregators exclude from circulating supply, so it's likely the main discretionary-supply overhang.
Question
Is any of the following present: mandatory PHA payment for inference or compute, a published PHA-denominated fee stream, a usage-linked burn, a buyback, revenue distribution to PHA or vPHA holders, or a verifiable link from Phala Cloud revenue to PHA demand? And who controls the 139.01M-PHA Gnosis Safe, under what schedule?
What would invalidate it
Invalidated if a primary Phala source or an on-chain trace shows any of these live: PHA required to pay for compute, PHA or revenue-funded buybacks or burns, or protocol revenue paid to PHA or vPHA holders. Also invalidated if the Safe is shown to be time-locked or vesting under a binding, published schedule.
Structured evidence: /api/public-network/intelligence/635fd786-0cd8-4f95-882e-46e128e72d12