jain.com

HPC infrastructure allocation plan

Company: Core Scientific

Subject kind
facility capacity
Statement date
2024-07-02
Promised amount
700.0 MW
Current status
stated

The claim, verbatim

Plan to allocate 700 megawatts for HPC: 500 MW for hosted GPUs, 200 MW for HPC support infrastructure; remaining 500 MW for bitcoin mining

Source (primary)

Core Scientific, Inc. Investor and Analyst Event June 12, 2024 Transcript (IR page (investors.corescientific.com), earnings_call)
View cached copy (2026-09-01)Live source ↗

Quote: “we aim to provide 700 megawatts for HPC, of which 500 megawatts will be for the hosted GPUs, so that's about 200 megawatts that are needed in order to support those facilities. This leaves about 500 megawatts of our existing portfolio for bitcoin mining.”

How we checked this

Checked on October 10, 2026. The cited source supports every part of this claim.

The CEO lays out the 700 MW HPC plan (500 MW to GPUs, about 200 MW support) leaving about 500 MW for bitcoin mining, and the CFO repeats the split.

Confirmed in the source:

What we did: Read our cached copy of IR page (investors.corescientific.com) (https://d1io3yog0oux5.cloudfront.net/_eb9c314ac28438fbd39d12d91c4e5bdc/corescientific/db/1066/11128/pdf/June_2024_Investor_Day_Transcript_061224.pdf) in full (94,603 characters, retrieved September 1, 2026) and checked each assertion in the claim against it.

Additional evidence

confirms Core Scientific, Inc. Investor and Analyst Event June 12, 2024 Transcript

Quote: “we aim to provide 700 megawatts for HPC, of which 500 megawatts will be for the hosted GPUs, so that's about 200 megawatts that are needed in order to support those facilities. This leaves about 500 megawatts of our existing portfolio for bitcoin mining.”

View cached copy (2026-09-01)Live source ↗

Record of changes

September 2, 2026 — stated
Automated extraction from the cited source. Recorded automatically from the cited source when it was published, then queued for evidence review.
October 9, 2026 — stated
Review. statement_date 2026-09-01 was the source's retrieval date; source published 2024-07-02.