Chain of custody receipt

Source #80925

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: RTX CORPORATION — Department of Defense contract N0001917C0020 ($2.68B)
Original URLhttps://www.usaspending.gov/award/CONT_AWD_N0001917C0020_9700_-NONE-_-NONE-/
PublicationUSASpending.gov
Source typecontract
Date2016-11-08
EntityX Corp
Captured2026-10-03T13:49:08.805Z UTC
Hash computed at2026-10-03T13:49:08.805Z UTC
SHA-2566b0473a8c6d95559d45d30a7d4b6c915501fb3024993c600f395446af43446e5
Content length509 bytes
Content preview (first 800 chars) 
{
  "internal_id": 309494517,
  "Award ID": "N0001917C0020",
  "Recipient Name": "RTX CORPORATION",
  "Award Amount": 2682738779.93,
  "Description": "LRIP 11 AAC - FMS AND INTERNATIONAL PARTNERS",
  "Awarding Agency": "Department of Defense",
  "Awarding Sub Agency": "Defense Contract Management Agency",
  "Start Date": "2016-11-08",
  "End Date": "2021-09-30",
  "awarding_agency_id": 1173,
  "agency_slug": "department-of-defense",
  "generated_internal_id": "CONT_AWD_N0001917C0020_9700_-NONE-_-NONE-"
}

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/80925/verify and our server will compare for you:

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

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