Chain of custody receipt

Source #80918

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 HC102818F0719 ($101.53M)
Original URLhttps://www.usaspending.gov/award/CONT_AWD_HC102818F0719_9700_HC102817D0001_9700/
PublicationUSASpending.gov
Source typecontract
Date2018-06-07
EntityMicrosoft
Captured2026-10-03T13:49:05.543Z UTC
Hash computed at2026-10-03T13:49:05.543Z UTC
SHA-256e03b2e5503e462d850d129de12fdbfed857e10d52df0354ea013c5bb56cfc3c1
Content length494 bytes
Content preview (first 800 chars) 
{
  "internal_id": 306483457,
  "Award ID": "HC102818F0719",
  "Recipient Name": "MICROSOFT CORPORATION",
  "Award Amount": 101532072.99,
  "Description": "SE31&SE34 MCS LABOR",
  "Awarding Agency": "Department of Defense",
  "Awarding Sub Agency": "Defense Information Systems Agency",
  "Start Date": "2018-06-07",
  "End Date": "2023-06-14",
  "awarding_agency_id": 1173,
  "agency_slug": "department-of-defense",
  "generated_internal_id": "CONT_AWD_HC102818F0719_9700_HC102817D0001_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/80918/verify and our server will compare for you:

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

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