TRV-2026-2350Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-2350 version: 1 kind: certified reason: Certified into the record timestamp: 2026-11-03T12:01:35.516758Z status: published lens: p_space sector: climate headline: UK’s most polluting power plant could power country’s largest AI datacentre dek: Britain’s most polluting power plant could soon power the country’s largest datacentre under a £20bn deal to build AI infrastructure on the site of the Drax power plant in North Yorkshire. The power plant’s FTSE 250 owner has struck a deal with the infrastructure investor Brookfield and and the AI infrastructure platform Radiant to develop a datacentre with an eventual capacity of more than 1 gigawatt that could begin operations by early 2028. In the initial phase of the project Drax will provide the datacentre… gain_title: (none) problem_title: A rush of datacentre building on a congested UK grid with binding climate targets raises questions about relying on expensive, polluting off-grid gas generation. trace_subject: (none) gain_reading: (none) gain_evidence: (none) problem_reading: A rush of datacentre building on a congested UK grid with binding climate targets raises questions about relying on expensive, polluting off-grid gas generation. problem_evidence: congested grid infrastructure and ambitious legally binding climate targets have raised questions | relying heavily on expensive and polluting off-grid gas generation quick_read: Drax, the owner of Britain's largest power station in North Yorkshire, has struck a deal with Brookfield and Radiant to develop a datacentre of more than 1 gigawatt on its site. A first phase of up to 100MW of compute capacity could be running by early 2028, using land and existing grid connections. The plan matters because Drax faces reduced government subsidies and a more limited future role, so the project is pitched as securing its revenues and jobs. Whether the site can be powered directly, and how a wave of datacentres can be supplied without polluting gas generation, remains unresolved. limitation: Direct power supply to the datacentre depends on regulatory approvals not yet secured, and the article says questions remain over how datacentres could be powered without polluting gas generation. tag: Evidence-backed problem key_points: The deal with Brookfield and Radiant could bring more than £20bn of investment and a datacentre above 1 gigawatt. | Phase one would offer up to 100MW of compute capacity from the first quarter of 2028. | Drax hopes to power the datacentre directly by the early 2030s, pending regulatory approvals before 2031. | Drax's subsidies are set to halve from 2027 to 2031 after concerns about its sustainability claims. | Drax's market value rose almost 9% to nearly £3bn on the news. rundown: Drax produces almost 5% of UK electricity by burning woody biomass pellets and is described by analysts as the single largest emitter of carbon dioxide. Its emissions are not counted by the government because Drax says growing trees absorb the equivalent carbon. Ministers promised that Drax would play a much more limited role in future, and it will receive only half of its current £2m a day subsidies from 2027 to 2031. Chief executive Will Gardiner framed the project as supporting the north's reindustrialisation and sovereign AI capability. The deal came a week after the government published a draft national policy statement calling datacentres as fundamental to the economy as railways and electricity networks. sources: - journalism | The Guardian | https://www.theguardian.com/business/2026/nov/03/uk-drax-power-station-ai-datacentre | 2026-11-03 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- d007379d5fa41f6cf3334665f90226fe6dc6039db2604ae3b51b8c709eaa0830
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-2350 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.
ace