PHA value capture: does Phala Cloud usage create demand for PHA? (deep-research method test)

Published date. Secondary opinion: "Phala's revenue is mostly off-chain"; "Enterprises pay for confidential compute with credit cards through Stripe, and almost none of it routes to PHA holders". It also says no buyback or fee switch connects cloud revenue to the token. Not a primary source.

eth_call at block 26241118. getThreshold = 2. getOwners = 5: 0xff52c825…, 0x3f7a5f0c…, 0x503f3141…, 0x3d19777f…, 0xa399460c…. VERSION = 1.4.1. PHA balanceOf = 139,010,885.34. PHA totalSupply = 1,000,000,000 exactly. The owners weren't identified.

Approximate read time. Treasury funding is described as "transaction fees, slashing, Secure Worker mining rate (20%)", with spending by community-approved proposals. No address, controller, vesting schedule, burn or buyback is given. The wording may date from the legacy parachain design; whether it is current is unverified.

Approximate read time. GPU workers post vPHA collateral: H100 1,250, H200 1,875, B200 2,250 vPHA. Rewards come from a mining reward pool; the page says 70% of total supply is allocated to mining rewards, with GPU miners getting 40% of that pool, paid hourly in vPHA. The page doesn't say how customers pay or whether they pay in PHA.

Approximate read time. Shows 125.3B "confidential model tokens/day" dated 2026-10-20, "Crawled from Phala's OpenRouter provider chart", and 10 active models. No revenue figure. PHA payments, burns and buybacks aren't mentioned.

eth_call at block 26241118. The vault holds 133,064,459.31 PHA (13.31% of supply; ~15.5% of the 858.2M circulating Surf reports). vPHA totalSupply is 86,298,756.32, an implied ~1.542 PHA per vPHA. The vault receives periodic PHA transfers from the 0x4a39 Safe, which suggests rewards are funded by distribution rather than revenue (inference).

Approximate read time. Staking on Ethereum mainnet converts PHA to vPHA at a rising exchange rate, with a 21-day unstake. The page doesn't say whether rewards come from emissions, fees or revenue. No burn, buyback, revenue share or fee is described beyond gas.

Indexed transfer query, last 364 days. The Safe received 332,083,656.87 PHA from 0xc8325881…b830; that contract's bytecode includes a "sender must be bridge contract" check, so it looks like a bridge handler. Outflows on 2025-11-20: 87.68M to PhalaClaimer (0x8b6d…777f), 54.86M to another Safe (0x35e0…b103), 20M to the vPHA vault. Recurring transfers since: ~1.19M and ~0.60M PHA roughly monthly to 0x7700…0f62 and 0x35e0…b103, and batches to the vPHA vault, 0x622e…153d and Safe 0xf32f…ecb6 (e.g. 2026-08-27, 2026-09-25). Purpose of the transfers isn't verified.

Published date; no time shown. Attack window Oct 8–12, detected Oct 12 19:28 UTC. A guest-agent log-endpoint flaw (dstack OS v0.3.1–v0.6.0) combined with a host network-isolation gap. Environment variables of a small set of customer apps were exposed, and a shared gateway admin token was stolen. The post says TEE, KMS and sealing keys and customer disks were not accessed, and doesn't mention funds. Fixed in v0.6.1 and v0.5.12 by Oct 13. Customers must upgrade by Nov 19, 2026.

Approximate read time. The page says "Credit card through Stripe, crypto through Coinbase Commerce, and wire transfer for enterprise accounts." Prices are shown with $ (e.g. GPU TEE $4.40/hour). PHA isn't mentioned; there's no PHA payment option or discount. Coinbase Commerce's accepted assets weren't checked.