CANUS

Research / 03 · GPU contracts and capital

Research as at

14 June 2026

GPU Delivery Is Not One Financial Milestone

Four filed agreements separate technical proof, customer acceptance and funding.

Abstract

GPU delivery evidence already performs a financial function. Our comparison of four filed agreements identifies distinct requirements for technical testing, customer acceptance, service payments and financing. The documents connect some of these requirements explicitly, but they do not reduce them to a single completion event. We derive an evidence-to-decision map and quantify the consequences in two transparent scenarios: seven days of service charges amount to US$430,080 for the assumed cluster, while seven days of carrying US$10 million at 8% costs US$15,342.47. A third analysis shows why earlier evidence changes funding timing only when the affected requirement is decisive. The commercial implication is specific: independent GPU evidence and coordinated requirements have a role where they resolve a named acceptance or financing task. CANUS should compete on completing that work, its cost and its reuse, rather than on another certificate alone.

  1. 01Required facts
  2. 02Recipient decisions
  3. 03Financial consequences

Provenance & verification

Provenance and verification.

Each file is published with a fixed fingerprint and independent timestamps. The commands below reproduce the checks.

SHA-256 fingerprint
461f0d47fb942f247d3831f1aa6e4de3a001e4b36ecdb01ee76abef82fabcc34
Independently notarised
RFC-3161 · FreeTSA · verifiedTime recorded in the token below
OpenTimestamps
Bitcoin-anchoredPending confirmation

Integrity — SHA-256

shell
sha256sum -c CANUS_Research_03_Contracted_Compute.pdf.sha256

Confirms the download is byte-for-byte the published file.

Timestamp — RFC-3161

shell
openssl ts -verify -in CANUS_Research_03_Contracted_Compute.pdf.tsr -data CANUS_Research_03_Contracted_Compute.pdf \
  -CAfile freetsa-cacert.pem -untrusted freetsa-tsa.crt

An independent authority (FreeTSA) signed the file's hash. 'Verification: OK' means the exact file existed no later than the token's timestamp.

Timestamp — OpenTimestamps

shell
ots verify CANUS_Research_03_Contracted_Compute.pdf.ots

A Bitcoin-anchored record, once the calendar confirms it into a block.

Each file is published unaltered and independently notarised; the exact notarisation time is contained in the downloadable token. Dates are evidenced by the public records each paper cites, not by file metadata.

References & cited records

Dates below are the verified SEC filing dates of the cited exhibits, not their execution dates. All four were publicly filed by 14 June 2026. SEC EDGAR links may require a browser; the pages are public.

  1. 01

    Microsoft Partner Statement of Work, IE US Hardware 3 Inc., Exhibit 10.3. Accession 0001878848-26-000015.

    Filed 5 February 2026Open the record
  2. 02

    CoreWeave Compute Acquisition Co. VIII credit agreement, DDTL 4.0, Exhibit 10.1. Accession 0001769628-26-000129.

    Filed 31 March 2026Open the record
  3. 03

    Nebius / Microsoft Statement of Work, Exhibit 4.4. Accession 0001104659-26-052948.

    Filed 30 April 2026Open the record
  4. 04

    SAI AU No.2 / Spochub / ESDS Master Services Agreement and form of Service Order, Exhibit 10.17. Accession 0001493152-26-023769.

    Filed 15 May 2026Open the record