Chain of custody receipt

Source #80917

Cryptographic attestation that the document below was captured in Goblin House's archive at the timestamp shown, with the hash listed. If the original URL goes dark or its content changes, this receipt remains as evidence of what the public record looked like at capture time.

TitleUSASpending.gov: MICROSOFT CORPORATION — Department of Defense contract N0003922F7903 ($104.44M)
Original URLhttps://www.usaspending.gov/award/CONT_AWD_N0003922F7903_9700_N6600119D0019_9700/
PublicationUSASpending.gov
Source typecontract
Date2022-09-26
EntityMicrosoft
Captured2026-10-03T13:49:05.525Z UTC
Hash computed at2026-10-03T13:49:05.525Z UTC
SHA-2564daa370c82b155c5fd143f105f82a61571a5fccd2f2e8488eef192b659257edf
Content length494 bytes
Content preview (first 800 chars) 
{
  "internal_id": 309531326,
  "Award ID": "N0003922F7903",
  "Recipient Name": "MICROSOFT CORPORATION",
  "Award Amount": 104437925.14,
  "Description": "MICROSOFT UNIFIED SUPPORT (MUS)",
  "Awarding Agency": "Department of Defense",
  "Awarding Sub Agency": "Department of the Navy",
  "Start Date": "2022-09-26",
  "End Date": "2024-05-31",
  "awarding_agency_id": 1173,
  "agency_slug": "department-of-defense",
  "generated_internal_id": "CONT_AWD_N0003922F7903_9700_N6600119D0019_9700"
}

Verifying this receipt

The hash above was computed as:

sha256( coalesce(url, '<no-url>') || '\n' || raw_content )

Anyone with a copy of the original document can verify the match:

  1. Take the URL field and the original document content.
  2. Concatenate url + '\n' + content and SHA-256 it.
  3. Compare to the SHA-256 row above.

Or POST the candidate content to /source/80917/verify and our server will compare for you:

curl -X POST https://www.goblinhouse.net/source/80917/verify \
  -H "Content-Type: text/plain" \
  --data-binary @document.txt

Companion machine-readable receipt: /source/80917/receipt.json