Community impact · CoreWeave / Digital Crossroads expansion · IN

Up to $4 million per year for 20 years

A verdict applies only to the wording shown.

Public statement checked

Answer

Verdict on the wording above: Outdated It referred to a date, trigger or plan that has since passed or lapsed; newer evidence not yet checked. Not a finding that it is now false. How verdicts work →

Who stated it
Said by the City of Hammond · government record · 9 June 2025 →
What the evidence establishes
Stated 9 June 2025; it referred to a plan, deadline or agreement that has since passed or lapsed. Authorized, then lapsed. The Common Council adopted Resolution 25R-16 approving the development agreement on 9 June 2025 by an 8–0 roll-call vote (one member absent); the 22 December 2025 minutes record an extension. It was accurate as of the date shown as far as the record goes; this is not a finding that it is now false.
Biggest limitation
The executed agreement and its payment-trigger clauses, the two extension resolutions, which milestones failed and any City payment ledger are not in the saved record; whether any payment was ever due or made is not established.
Checked
21 September 2026 · Next review: replacement proposal, new NIPSCO docket or new development agreement · History (3) →

Evidence

What the evidence supports

Authorized, then lapsed. The Common Council adopted Resolution 25R-16 approving the development agreement on 9 June 2025 by an 8–0 roll-call vote (one member absent); the 22 December 2025 minutes record an extension. The City announced on 1 July 2026 that the agreement for 301 Digital Crossroads had expired after two extensions because milestones were not satisfied by the 30 June 2026 deadline. No community impact payment is shown as due or received in the saved record, and the notice concerns the proposed 301 expansion, not the separate existing DX-1 facility; it does not freshly confirm current operation.

Still unknown

The executed agreement and its payment-trigger clauses, the two extension resolutions, which milestones failed and any City payment ledger are not in the saved record; whether any payment was ever due or made is not established.

Sources

  1. Hammond Common Council minutes, 9 June 2025 → Archived copy Gov. record

    Exact location pp. 3–11 (resolution 25R-16 introduced p. 3; lease, jobs, tax terms and community impact payment p. 4; NIPSCO contingency p. 6)

    What it supports Proposal, contemplated lease, jobs, tax terms, community payments and explicit power-agreement gating.

    Publication date unavailable · Accessed

  2. Hammond Common Council minutes, 22 December 2025 → Gov. record

    Exact location pp. 1–4 ($80 million community-payment total p. 1; $25 million announced p. 2; 'Right now it's not part of it' p. 4); extension resolution at p. 10

    What it supports Extension, utility negotiations and noncontractual $25 million discussion.

    Publication date unavailable · Accessed

  3. Hammond Announces Expiration of Data Center Development Agreement → Gov. record

    Exact location News post body, first paragraph (byline July 1, 2026): 'The City of Hammond announced today that the Development Agreement for the proposed data center project at 301 Digital Crossroads has expired following two previously approved extensions.'

    What it supports The development agreement among the City, the Redevelopment Commission, Decennial Group and CoreWeave expired after two extensions because milestones were not satisfied by the 30 June 2026 deadline. The notice does not say which milestones failed, does not show any payment or incentive as due or received, and concerns the proposed 301 expansion, not the separate existing DX-1 facility; it does not freshly confirm current operation.

    Publication date · Accessed

Corrections and history

Correction · 11 September 2026 · DataCenterData review

coreweave-hammond → Community impact payments

Field Community impact payments

From Previous locator

To pp. 1–4 ($80 million community-payment total p. 1; $25 million announced p. 2; 'Right now it's not part of it' p. 4); extension resolution at p. 10

Why 2026-09-11: previously 'pp. 1–2; extension resolution at p. 10'.

Evidence https://www.gohammond.com/document_library/meeting_minutes_and_agendas/city_council/2025/12-22-25_minutes.pdf →

Correction · 21 September 2026 · DataCenterData review

coreweave-hammond → Community impact payments

Field Community impact payments

From Not shown due or paid.

To Authorized, then lapsed. The Common Council adopted Resolution 25R-16 approving the development agreement on 9 June 2025 by an 8–0 roll-call vote (one member absent); the 22 December 2025 minutes record an extension. The City announced on 1 July 2026 that the agreement for 301 Digital Crossroads had expired after two extensions because milestones were not satisfied by the 30 June 2026 deadline. No community impact payment is shown as due or received in the saved record, and the notice does not concern the operating DX-1 facility, which is a separate record.

Why City of Hammond notice of 1 July 2026: the development agreement expired after two extensions because milestones were not satisfied by 30 June 2026. The authorized terms (Resolution 25R-16, 8–0, 9 June 2025) are now recorded as lapsed; no payment, incentive or NIPSCO agreement is shown in the saved record. Verdict unchanged.

Evidence https://www.gohammond.com/hammond-announces-expiration-of-data-center-development-agreement/ →

Review details

Scope

Unit
community impact payments
Geography
CoreWeave / Digital Crossroads expansion
Period
None recorded
Confidence
medium — city-council description
Kind
Public statement checked

Conflicting evidence

None recorded when this claim was checked. That records what we logged, not a finding that no conflicting record exists.

Outdated — the as-of date is not recorded. This is not a finding that it is now false.

Chronology

  1. Stated by City of Hammond
  2. Published — Hammond Announces Expiration of Data Center Development Agreement
  3. Source retrieved
  4. Changed source locator recorded
  5. Source retrieved
  6. Source retrieved
  7. Changed field recorded
  8. Checked by DataCenterData
  9. Date not established Next review: replacement proposal, new NIPSCO docket or new development agreement

Data

This claim as JSON →

Suggest a correction

Suggest a correction → Claim ID claim:coreweave-hammond:community-impact-payments and this page are prefilled. Accepted material corrections appear publicly on Changes.