Chain of custody receipt

Source #80765

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: INVARIANT CORPORATION — Department of Defense contract M6785425F0232 ($1.38M)
Original URLhttps://www.usaspending.gov/award/CONT_AWD_M6785425F0232_9700_M6785425D0056_9700/
PublicationUSASpending.gov
Source typecontract
Date2025-09-25
EntityInvariant
Captured2026-10-03T13:46:59.675Z UTC
Hash computed at2026-10-03T13:46:59.675Z UTC
SHA-256a4a384831874e1c4328a2215267db2ea13f0b650f6dbf08b45c89fbb15299291
Content length480 bytes
Content preview (first 800 chars) 
{
  "internal_id": 353698735,
  "Award ID": "M6785425F0232",
  "Recipient Name": "INVARIANT CORPORATION",
  "Award Amount": 1375736.42,
  "Description": "SPARE PARTS PACKAGE",
  "Awarding Agency": "Department of Defense",
  "Awarding Sub Agency": "Department of the Navy",
  "Start Date": "2025-09-25",
  "End Date": "2026-05-22",
  "awarding_agency_id": 1173,
  "agency_slug": "department-of-defense",
  "generated_internal_id": "CONT_AWD_M6785425F0232_9700_M6785425D0056_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/80765/verify and our server will compare for you:

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

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