Chain of custody receipt

Source #46216

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 — WhatsApp (2026-02-10)
Original URLhttps://efts.sec.gov/LATEST/search-index?q=%22WhatsApp%22&dateRange=custom&forms=4,SC%2013D,SC%2013G,DEF%2014A,10-K,10-Q
PublicationSEC EDGAR
Source typesec_filing
Date2026-02-10
EntityWhatsApp
Captured1970-01-01T00:00:00.000Z UTC
Hash computed at2026-05-13T04:45:55.076Z UTC
SHA-25632109bd24e178d775467f0a40c53d6655ba153528c10d627ddbebfa46ba60b3d
Content length564 bytes
Content preview (first 800 chars) 
{
  "ciks": [
    "0001835830"
  ],
  "period_ending": "2025-12-31",
  "file_num": [
    "001-41806"
  ],
  "display_names": [
    "Klaviyo, Inc.  (KVYO)  (CIK 0001835830)"
  ],
  "xsl": null,
  "sequence": 1,
  "root_forms": [
    "10-K"
  ],
  "file_date": "2026-02-10",
  "biz_states": [
    "MA"
  ],
  "sics": [
    "7372"
  ],
  "form": "10-K",
  "adsh": "0001835830-26-000007",
  "film_num": [
    "26616003"
  ],
  "biz_locations": [
    "Boston, MA"
  ],
  "file_type": "10-K",
  "file_description": "10-K",
  "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/46216/verify and our server will compare for you:

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

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