Chain of custody receipt

Source #80883

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 — Consumer Financial Protection Bureau contract 9531CB22P0002 ($118.4K)
Original URLhttps://www.usaspending.gov/award/CONT_AWD_9531CB22P0002_955F_-NONE-_-NONE-/
PublicationUSASpending.gov
Source typecontract
Date2021-11-03
EntityLinkedIn
Captured2026-10-03T13:48:20.166Z UTC
Hash computed at2026-10-03T13:48:20.166Z UTC
SHA-256a99c20ef13c98f65435fa92fda87dd6d9a90782a29cd9d80a82699a74840ca99
Content length524 bytes
Content preview (first 800 chars) 
{
  "internal_id": 292215008,
  "Award ID": "9531CB22P0002",
  "Recipient Name": "LINKEDIN CORPORATION",
  "Award Amount": 118385,
  "Description": "LINKEDIN SUBSCRIPTION SERVICE",
  "Awarding Agency": "Consumer Financial Protection Bureau",
  "Awarding Sub Agency": "Consumer Financial Protection Bureau",
  "Start Date": "2021-11-03",
  "End Date": "2022-11-02",
  "awarding_agency_id": 1158,
  "agency_slug": "consumer-financial-protection-bureau",
  "generated_internal_id": "CONT_AWD_9531CB22P0002_955F_-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/80883/verify and our server will compare for you:

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

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