Chain of custody receipt

Source #65884

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: 10-K — Snap Inc (2019-02-06)
Original URLhttps://www.sec.gov/Archives/edgar/data/1564408/000156459019002053/0001564590-19-002053-index.htm
PublicationSEC EDGAR
Source typesec_filing
Date2019-02-06
EntitySnap Inc.
Captured1970-01-01T00:00:00.000Z UTC
Hash computed at2026-05-31T05:33:03.753Z UTC
SHA-25657992d5b8de6ae2733a6c820a6cc76d3456de2a78acd7e0c0db42514bcb01d7b
Content length571 bytes
Content preview (first 800 chars) 
{
  "ciks": [
    "0001564408"
  ],
  "period_ending": "2018-12-31",
  "file_num": [
    "001-38017"
  ],
  "display_names": [
    "Snap Inc  (SNAP)  (CIK 0001564408)"
  ],
  "xsl": null,
  "sequence": 8,
  "root_forms": [
    "10-K"
  ],
  "file_date": "2019-02-06",
  "biz_states": [
    "CA"
  ],
  "sics": [
    "7370"
  ],
  "form": "10-K",
  "adsh": "0001564590-19-002053",
  "film_num": [
    "19569705"
  ],
  "biz_locations": [
    "Santa Monica, CA"
  ],
  "file_type": "EX-23.1",
  "file_description": "EX-23.1",
  "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/65884/verify and our server will compare for you:

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

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