Chain of custody receipt

Source #80916

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: MICROSOFT CORPORATION — Department of Agriculture contract 12314424F0350 ($107.31M)
Original URLhttps://www.usaspending.gov/award/CONT_AWD_12314424F0350_1205_12314424G0011_1205/
PublicationUSASpending.gov
Source typecontract
Date2024-07-17
EntityMicrosoft
Captured2026-10-03T13:49:05.508Z UTC
Hash computed at2026-10-03T13:49:05.508Z UTC
SHA-256af8c009a9dd696a9cc8ac65f74e084b1eb15377739ffbe9813ca236f84233337
Content length531 bytes
Content preview (first 800 chars) 
{
  "internal_id": 277319780,
  "Award ID": "12314424F0350",
  "Recipient Name": "MICROSOFT CORPORATION",
  "Award Amount": 107308915.76,
  "Description": "MICROSOFT AZURE STRATUS HSTXXX0000002144 93A34F",
  "Awarding Agency": "Department of Agriculture",
  "Awarding Sub Agency": "Office of the Chief Financial Officer",
  "Start Date": "2024-07-17",
  "End Date": "2029-07-16",
  "awarding_agency_id": 95,
  "agency_slug": "department-of-agriculture",
  "generated_internal_id": "CONT_AWD_12314424F0350_1205_12314424G0011_1205"
}

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

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

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