Chain of custody receipt

Source #80888

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: GLUEFOLDER, LLC — Department of Defense contract SP700016M0027 ($74.2K)
Original URLhttps://www.usaspending.gov/award/CONT_AWD_SP700016M0027_9700_-NONE-_-NONE-/
PublicationUSASpending.gov
Source typecontract
Date2015-10-27
EntityGlue
Captured2026-10-03T13:48:22.899Z UTC
Hash computed at2026-10-03T13:48:22.899Z UTC
SHA-2560c30db21e4f0b3edf621e619641380311b900bb387fde577f49054d9d21520ec
Content length464 bytes
Content preview (first 800 chars) 
{
  "internal_id": 313235177,
  "Award ID": "SP700016M0027",
  "Recipient Name": "GLUEFOLDER, LLC",
  "Award Amount": 74160,
  "Description": "GLUEFOLD MACHINES",
  "Awarding Agency": "Department of Defense",
  "Awarding Sub Agency": "Defense Logistics Agency",
  "Start Date": "2015-10-27",
  "End Date": "2015-11-15",
  "awarding_agency_id": 1173,
  "agency_slug": "department-of-defense",
  "generated_internal_id": "CONT_AWD_SP700016M0027_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/80888/verify and our server will compare for you:

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

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