TruaceTracing the truth around AIThursday, August 27, 2026
TRV-2026-0067Retracted — remains on the recordJournalism

No console-flation: how the thirst for AI chips is sending games console prices soaring

It was once a truth universally acknowledged that an ageing console in possession of good revenue must be in line for a price reduction. Those days may be over. In March, Sony announced a price increase of £90 for the PS5, while last month Microsoft informed gamers that it would be charging at least £75 more for the Xbox Series S and X consoles from August. All three were first released back in 2020. The Switch 2 will also be more expensive globally from September. The main culprit, of course, is AI, or more specif

Media & Arts · G Space — documented gain · certified 2026-07-12 · v2 · article view · machine-readable

This record was retracted on 2026-07-12Retracted from the live record. It remains permanently retrievable here, as does every prior version below.
Current reading — gain

No console-flation: how the thirst for AI chips is sending games console prices soaring: For years, Sony and Microsoft absorbed a loss on each console to keep prices down, and Nintendo used cheaper components to reduce costs.

What this doesn’t fix

Machine-ingested summary: the claims above reflect a single primary source and have not been weighed against contradicting evidence by a Truvace editor yet.

Evidence

Cite this record

Truvace Impact Record TRV-2026-0067, v2: “No console-flation: how the thirst for AI chips is sending games console prices soaring.” Truvace, 2026-07-12. /record/TRV-2026-0067 (accessed at citation time). sha256 2e0b2ce6a4490627

Calibration history

Every change to this record since certification, in the open.

  1. Retractedv22e0b2ce6a449

    Retracted from the live record

  2. Certifiedv12bc36cbd7432

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0067 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.