Chain of custody receipt

Source #80884

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: LINKEDIN CORPORATION — Department of Defense contract M0026417P0201 ($90.0K)
Original URLhttps://www.usaspending.gov/award/CONT_AWD_M0026417P0201_9700_-NONE-_-NONE-/
PublicationUSASpending.gov
Source typecontract
Date2017-09-27
EntityLinkedIn
Captured2026-10-03T13:48:20.192Z UTC
Hash computed at2026-10-03T13:48:20.192Z UTC
SHA-2566b14d039079df50e09ef95eb7c0f9ac049cc020ffc4bf19691bfa4f7fe3b0b16
Content length490 bytes
Content preview (first 800 chars) 
{
  "internal_id": 309178781,
  "Award ID": "M0026417P0201",
  "Recipient Name": "LINKEDIN CORPORATION",
  "Award Amount": 90000,
  "Description": "LYNDA.COM ONLINE TRAINING WEBSITE ACCESS",
  "Awarding Agency": "Department of Defense",
  "Awarding Sub Agency": "Department of the Navy",
  "Start Date": "2017-09-27",
  "End Date": "2017-09-28",
  "awarding_agency_id": 1173,
  "agency_slug": "department-of-defense",
  "generated_internal_id": "CONT_AWD_M0026417P0201_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/80884/verify and our server will compare for you:

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

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