Chain of custody receipt

Source #80879

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: TENNESSEE VALLEY AUTHORITY — Department of Defense contract 0041 ($6.58M)
Original URLhttps://www.usaspending.gov/award/CONT_AWD_0041_9700_F4065002D0022_9700/
PublicationUSASpending.gov
Source typecontract
Date2009-03-31
EntityTennessee Valley Authority
Captured2026-10-03T13:48:11.484Z UTC
Hash computed at2026-10-03T13:48:11.484Z UTC
SHA-256ac793061546606a84166cdbf095e2ab343a901dff69b959c41ac52670e67c503
Content length490 bytes
Content preview (first 800 chars) 
{
  "internal_id": 273746591,
  "Award ID": "0041",
  "Recipient Name": "TENNESSEE VALLEY AUTHORITY",
  "Award Amount": 6584163.57,
  "Description": "ELECTRIC UTILITY FOR FY09 2ND QUARTER",
  "Awarding Agency": "Department of Defense",
  "Awarding Sub Agency": "Department of the Air Force",
  "Start Date": "2009-03-31",
  "End Date": "2009-03-31",
  "awarding_agency_id": 1173,
  "agency_slug": "department-of-defense",
  "generated_internal_id": "CONT_AWD_0041_9700_F4065002D0022_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/80879/verify and our server will compare for you:

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

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