Chain of custody receipt

Source #80919

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 N0001918C1021 ($8.69B)
Original URLhttps://www.usaspending.gov/award/CONT_AWD_N0001918C1021_9700_-NONE-_-NONE-/
PublicationUSASpending.gov
Source typecontract
Date2018-03-23
EntityX Corp
Captured2026-10-03T13:49:08.701Z UTC
Hash computed at2026-10-03T13:49:08.701Z UTC
SHA-256c580b3ff735cecdec57ea0a2dc5c0f3ac00540f3c004184402586583be7284c7
Content length496 bytes
Content preview (first 800 chars) 
{
  "internal_id": 309495105,
  "Award ID": "N0001918C1021",
  "Recipient Name": "RTX CORPORATION",
  "Award Amount": 8688654906.89,
  "Description": "LOT 12 AAC LONG LEAD FOR PROPULSION SYSTEMS",
  "Awarding Agency": "Department of Defense",
  "Awarding Sub Agency": "Department of the Navy",
  "Start Date": "2018-03-23",
  "End Date": "2024-12-30",
  "awarding_agency_id": 1173,
  "agency_slug": "department-of-defense",
  "generated_internal_id": "CONT_AWD_N0001918C1021_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/80919/verify and our server will compare for you:

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

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