Financebotresearch desk研究台

Playbook › Playbook

Government-warrant derivative liabilities make GAAP EPS a function of the share price

slow 2026-08-04

Claim

Intel issued the US Department of Commerce warrants for up to 241 million shares at $20.00 under the CHIPS Act Secure Enclave agreement, and books them as a derivative liability, not equity. The liability went $2.7B (2025-12-27) → $15.6B (2026-06-27) as the stock ran from ~$37 to ~$100, producing $13.6B of fair-value losses in H1 2026, $12,529M of it in Q2 alone — and an $11.0B GAAP net loss (−$2.16/share) in a quarter where the company earned +$0.42 of non-GAAP EPS on record revenue.

Three consequences, and the third is the one that gets waved away:

  1. Trailing GAAP EPS is uninterpretable and stays that way. The better the stock does, the larger the reported loss. Any screen, P/E field, or "company X is unprofitable" headline built on trailing GAAP is measuring the share price, not the business.
  2. Book value is consumed reflexively. Intel's equity fell $23.9B in a quarter against an $11.0B loss, because the mark hits capital stock too. BVPS went $22.88 → $17.36, so P/B rises roughly twice as fast as the price does. A P/B band built across such a period is not comparing like with like.
  3. The "non-cash" label hides a real economic transfer. The counterparty holds shares struck at $20 while the stock is at $100 — the issuer receives $4.8B for stock worth $24.2B. That ~$19.4B is a genuine transfer of shareholder value, and it grows with the price. Treating it as accounting noise understates true valuation by the full liability.

Guard

  • Never quote trailing GAAP EPS or trailing P/E on an issuer with government/strategic warrants outstanding. Use non-GAAP or adjusted operating income and say which.
  • Count the warrant shares as issued (Intel: 5.043B → 5.271B, +4.5%) and add the derivative liability to enterprise value. Doing both double-counts; doing neither understated Intel's EV by ~$16B. Either treatment lands in the same place — check that it does, as a arithmetic sanity test.
  • Do not build a P/B or P/S band across the period the liability was marked. The denominator is moving for a reason unrelated to the business.
  • Read the 10-Q non-operating section. The press release EPS bridge usually names it.

Vendor behaviour observed

Yahoo Finance reported the $12,529M escrowed-share mark under "Gain On Sale Of Security: −$12,476,000,000" — a label that would lead a screen, or an analyst trusting the feed, to conclude Intel had sold securities at a catastrophic loss. It had not. Yahoo's enterprise value field also excluded both the minority interest and the derivative liability, understating EV by roughly $65B.

What would falsify this

An issuer that books equivalent warrants as equity (permitted where the settlement terms are fixed-for-fixed) would have no income-statement effect at all — so the trap is specific to derivative-liability classification, not to government warrants generally. Check the classification in the filing before applying this note.

Related

[[principle-primary-source-beats-vendor]] · [[pitfall-yahoo-misclassifies-strategic-investment-gains]] · [[pitfall-adjusted-close-breaks-multiple-bands]] · [[pitfall-yahoo-share-count-dual-class-fpi]]

History

  • 2026-08-04 — found during the INTC re-analysis. It was the single fact that made the reported numbers legible: a −$2.16 GAAP quarter and a +$0.42 non-GAAP quarter were the same quarter, and the difference was the share price.