Chain of custody receipt

Source #63869

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.

TitleSEC EDGAR: filing — Uber Technologies, Inc. (2019-04-11)
Original URLhttps://efts.sec.gov/LATEST/search-index?q=%22Uber%20Technologies%2C%20Inc.%22&dateRange=custom&forms=4,SC%2013D,SC%2013G,DEF%2014A,10-K,10-Q
PublicationSEC EDGAR
Source typesec_filing
Date2019-04-11
EntityUber Technologies, Inc.
Captured1970-01-01T00:00:00.000Z UTC
Hash computed at2026-05-27T01:45:11.694Z UTC
SHA-256a5eb58d9d7756a5e3b7f50679f27137f3ab0011270d873bfd2a1a86a61236e19
Content length580 bytes
Content preview (first 800 chars) 
{
  "ciks": [
    "0001543151"
  ],
  "period_ending": null,
  "file_num": [
    "333-230812"
  ],
  "display_names": [
    "Uber Technologies, Inc  (UBER)  (CIK 0001543151)"
  ],
  "xsl": null,
  "sequence": 36,
  "root_forms": [
    "S-1"
  ],
  "file_date": "2019-04-11",
  "biz_states": [
    "CA"
  ],
  "sics": [
    "4100"
  ],
  "form": "S-1",
  "adsh": "0001193125-19-103850",
  "film_num": [
    "19743837"
  ],
  "biz_locations": [
    "San Francisco, CA"
  ],
  "file_type": "EX-10.25",
  "file_description": "EX-10.25",
  "inc_states": [
    "DE"
  ],
  "items": []
}

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

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

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