Chain of custody receipt

Source #3181

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 — L3Harris Technologies (2021-03-01)
Original URL(none — typed-API result with no web URL)
PublicationSEC EDGAR
Source typesec_filing
Date2021-03-01
EntityL3Harris Technologies
Captured2026-04-08T20:09:00.361Z UTC
Hash computed at2026-04-08T20:09:00.361Z UTC
SHA-2563d3ea476129a1fe471d01ded2f8ad5a3cd63cc26b3ffac68808aae9159545f18
Content length587 bytes
Content preview (first 800 chars) 
{
  "ciks": [
    "0000202058"
  ],
  "period_ending": "2021-01-01",
  "file_num": [
    "001-03863"
  ],
  "display_names": [
    "L3HARRIS TECHNOLOGIES, INC. /DE/  (LHX)  (CIK 0000202058)"
  ],
  "xsl": null,
  "sequence": 7,
  "root_forms": [
    "10-K"
  ],
  "file_date": "2021-03-01",
  "biz_states": [
    "FL"
  ],
  "sics": [
    "3812"
  ],
  "form": "10-K",
  "adsh": "0000202058-21-000008",
  "film_num": [
    "21698938"
  ],
  "biz_locations": [
    "Melbourne, FL"
  ],
  "file_type": "EX-21",
  "file_description": "EX-21",
  "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/3181/verify and our server will compare for you:

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

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